Working with one chapter
A direct membership assigns a role in that organization. It does not automatically open its parent or sibling workspaces.
Local teams. A network that works together.
Give each organization a home for its people, events, forms and talent work. Invite colleagues into the right workspace, whether they support one local team or a whole branch.
Give each colleague the right responsibility.
Choose a role for the work a colleague needs to do. Event operations, sensitive records and team administration carry different responsibilities. An attendee account or CRM relationship does not grant workspace access.
| Role | Event work | Manage team |
|---|---|---|
| Owner | Create and edit | All roles |
| Admin | Create and edit | Non-owner roles |
| Member | Create and edit | No |
| Viewer | Read only | No |
Event work includes preparing events, issuing tickets, and recording check-ins. Only authorized roles can manage contracts, review finances, read internal notes or export records. Owners can create child organizations; administrators cannot grant wider access than they hold.
Connect organizations without opening every workspace.
A parent relationship does not grant access by itself. Choose direct membership for a local assignment, or explicitly extend a role across a branch.
Supporting a whole branch
An explicit descendant grant extends a role from an organization into its child organizations. A coordinator can support the local teams in that branch.
For access to one child instead of the whole branch, add a direct membership there. Every organization keeps at least one directly assigned owner.
Keep access aligned with the people doing the work.
Invite a colleague by email, with a clear role and organization scope. They accept through their own verified account. Authorized owners and administrators can change the role, adjust descendant access or remove the membership as responsibilities change.
Start with the local team, then decide who needs to support several organizations. A regional event coordinator and an agent working with a child organization’s talent roster can each receive the access their assignment requires.
Explore connected team setupsA secure start for every teammate.
People sign in directly to Turnstile. The same account can hold their own tickets and accepted team invitations, with workspace access granted separately.
- Choose a familiar way to sign in
- Use email and password, a saved passkey on a compatible device, or a magic link. Every account verifies its email before accessing protected work.
- Keep two-step verification on
- MFA with an authenticator app is required for all accounts, including attendees. A passkey or email link does not skip the second-factor requirement.
- Keep personal and team records distinct
- Someone’s private profile belongs to them. Organization CRM records stay in their workspace; a household, employment or representation relationship does not confer access.
Questions about roles and organization access.
Do parent administrators automatically see child organizations?
No. Being an administrator in a parent organization does not automatically open child workspaces. A person needs a direct membership in the child or an explicitly granted descendant scope from an ancestor.
Can we create custom or check-in-only roles?
The current workspace roles are Owner, Administrator, Member, and Viewer. They apply across an organization. A custom-role builder, per-event role assignments, and a separate check-in-only role are not currently provided.
How do we add colleagues?
An authorized owner or administrator invites a colleague by email and chooses their role and scope of access. The colleague verifies their email, completes account security setup and accepts the invitation. Access to child organizations requires an explicit grant.
Does a Viewer see every record in an organization?
No. Read access is permission-specific. A Viewer can see the records included in that role, but does not receive internal CRM notes, contract access or financial review simply by joining the workspace. Choose roles around the actual responsibilities your team needs.
Talk through your team structure.
Tell us how your organizations are connected and who needs to work across them.