Admins & Inherited Access
Admin access can be granted on one team, or it can flow down from a level above. This guide explains who can administer what, and why some admins appear without you adding them.
Who can administer
An admin can run a team — build schedules, manage people, change settings. You give someone admin rights by setting their role to admin on a team.
Scope it to where it’s needed
How access flows down
Access flows downhill. If you’re an admin of a Group, you’re automatically an admin of every Sub-Group inside it — no need to be added to each one.
Inherited admins show up automatically
Dashboards above the team
Being admin of a higher level doesn’t just grant access to the teams below — that level gets a home of its own. From the hub, open a Group, Organization, Institution, or Corporation and you’ll find its own dashboard: the entities inside it, the users across all of them, activity logs, statistics, and billing for that whole branch.
Oversee up high, schedule down low
Admins & Access FAQ
What does “inherited” access mean?
If you’re an admin of a higher level — say a Group — you automatically have admin rights over the teams inside it. You don’t need to be added to each one separately. That’s inheritance.
Why do I see admins I didn’t add?
Those are inherited admins — people who manage a level above this team. They show up so you know who else has access, even though they were added higher up.
How do I give someone admin of just one team?
Add them to that Sub-Group and set their role to admin. Their access stays scoped to that team only.