Gratona Network
Shared fundraising infrastructure with local control.
Give a denomination, federation, foundation, membership organization, or partner network a common relationship and reporting model while preserving entity boundaries, permissions, ownership, and local workflows.
Network is custom-scoped. Price and implementation depend on entity structure, external accounts, integrations, security, reporting, AI usage, and service requirements.
Entity-aware records
Define which records belong to a local entity, which can be shared, and which roll up for central reporting or coordinated work.
Delegated access
Use roles, SSO, partner workspaces, and external accounts to give each person the access needed for their part of the network.
A branded member experience
Scope an organization-branded mobile app for donors, members, and staff, with role-aware views for the work and relationships each person can access.
Scope the operating model before configuration
Network implementation starts with the organization chart, data ownership, permissions, reporting, integrations, and decision rights.
Step 1
Map entities and relationships
Document headquarters, affiliates, programs, partners, local teams, shared constituents, and the records each part of the network owns.
Step 2
Set access and governance
Define roles, delegated administration, SSO, external accounts, approval requirements, audit expectations, and security review.
Step 3
Design rollups and integrations
Specify local and central reporting, accounting paths, data exchange, APIs, partner workspaces, and the source of truth for each workflow.
Step 4
Roll out and validate
Plan migration, training, entity onboarding, acceptance tests, support, infrastructure, and service levels for the operating model.
Scope evidence
Test the same record from local and central roles.
A Network design is credible only when record ownership, access, rollups, and exceptions can be demonstrated against the agreed operating model.
- Entity boundary
Owning entity, shared scope, and local-versus-central visibility
The implementation defines where a record belongs and which roles can view or act on it across the network.
- Delegated work
Role, permission, partner workspace, and approval path
Local staff, headquarters, and external participants receive the access and review path written into the scope.
- Rollup
Local detail, central total, exclusions, and source records
Network reporting should preserve the local records behind a central result rather than expose an unexplained aggregate.
Require an acceptance test that opens the same scenario as a local user and a central user, then reconciles the approved cross-entity rollup.
What belongs in a Network scope
- Multi-entity hierarchy, cross-entity rollups, delegated access, SSO, partner workspaces, and external accounts.
- An organization-branded mobile app for donor, member, and staff access.
- Advanced grantmaking workflows are in private beta; access and current scope are confirmed separately. Custom integrations, dedicated infrastructure, security review, governance, and service levels are written into the Network scope.
- High-volume external accounts, member applications, two-way accounting, and other organization-specific workflows should be written into the final scope.
Explore Gratona by fundraising goal