A home for each chapter
Keep each team’s people, forms, events and tickets in its own organization. Staff working only with one chapter receive direct membership there.
Local teams know their people. Give each chapter a workspace for its own events and records, then grant regional colleagues access only where their work calls for it.
A parent organization can connect the network without making every parent administrator an administrator of every chapter. Access to a child organization takes an explicit grant.
Keep each team’s people, forms, events and tickets in its own organization. Staff working only with one chapter receive direct membership there.
Grant descendant access to a regional teammate when they need to help across a branch. That grant travels down only; it does not open unrelated chapters or the parent’s private records.
A person helping at the door needs check-in permission for the relevant event. They do not need every setting, people record or financial action in the network.
A chapter can publish its own gathering, decide how guests register and prepare the entrance team. A regional colleague with the right grant can step in when needed, using their own account and current permissions.
Set up memberships before sharing event work. If someone moves teams, change their access rather than passing around a shared login.
Explore organization and team accessNo. Being an administrator of a parent does not itself grant access to a child organization. The person needs direct membership or an explicit descendant grant for the relevant branch.
Yes, when the relevant organizations grant access. Use direct memberships for a few separate chapters or a deliberately scoped descendant grant for a branch. Permissions are checked against the organization and action each time.
No. Attendee tickets and people records do not create organization membership. Workspace access is assigned separately.
Tell us how local teams operate, where they need regional help and who owns each event.