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.
Explore Gratona Network
A local program update becomes a network decision
Gratona Network
Interactive example · sample recordsStep 1 of 4
Define the organization
Connect headquarters, affiliates, programs and partner teams with clear ownership of their records.
- Record
- Regional program network
- Status
- Entities connected
- Owner
- Network administrator
Tali’s part in the work
Prepare a summary of responsibilities and entity context.
Try this step with the sample record. No real records or messages are changed.
A central team needs information that is not part of its current access.
Route the request to the appropriate owner and retain the access boundary.
Read the full walkthrough
Define the organization
Connect headquarters, affiliates, programs and partner teams with clear ownership of their records.
Give each team the right access
Use roles and delegated access for local work and shared responsibilities. Keep sensitive records within their intended scope.
See the network picture
Bring local reporting into a cross-entity view that leaders can use to understand progress and exceptions.
Coordinate the response
Assign action to the appropriate entity or team and retain the decision in its context.
Explore the steps with sample records, then see your team’s workflow in a live demo.
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 custom-scoped and 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.
Related Gratona capabilities
Membership organizations
Configure dues, renewals and benefits through Gratona’s forms and programs.
Conservation organizations
Manage local access, shared records and fundraising reports across chapters and partner teams.
Denominations
See the Network model for denominational headquarters and affiliates.
Mission networks
Review network-wide fundraising and country-office coordination.
Pricing
See what changes plan fit and what drives a custom Network scope.
Choose the right fit
Compare multi-entity organizational platforms around your work.
Coordinate entities, permissions, shared relationships and leadership reporting without losing local context.
Open the comparison guide- 01Entity hierarchy and data ownership
- 02Delegated access and SSO
- 03Shared relationships and reporting
- 04Local autonomy and central governance
Getting started
Start with one complete workflow.
Map entities, shared relationships and decision rights first. Configure permissions and reporting, then validate local and central experiences with representative roles.
What should we bring to a demo?
Bring the people who own this workflow, an example of how it runs today and the decision you need to make. Walk through define the organization, give each team the right access, see the network picture, coordinate the response with your team.
How does Tali fit into the work?
Prepare the handoff using context available to the team. Your team keeps responsibility for the review and the next action. Tali works with the context and permissions behind the workflow.
Can we connect this to the rest of Gratona?
Yes. Gratona Network connects to the shared relationships, information and work in Gratona. Start with the workflow your team needs and use the same platform as more teams participate.
Explore Gratona by fundraising goal