Multiple Admin Levels
Four people, four different views of the same group.
Layered management roles with permissions you define, so an owner, a coach, a group leader, and a team captain each get exactly the access their job requires.
The group fulfillment chain
Sell
>
Enroll
>
Delegate
>
Report
One admin role is always the wrong shape
Available now as custom build.
A typical hierarchy
Everything available to you.
These are defaults. Every level and permission is yours to define.
Everything
Owner
- Full platform access
- Creates roles and defines their permissions
- Sees every group, every report, every member
A whole client
Organization admin
- All groups under one organization
- Buys and allocates seats
- Cross-group reporting
- Appoints group leaders below them
One group
Group leader or manager
- Their own team or cohort only
- Add, remove, and reassign members
- Full progress and engagement reporting
- Message their group
People, not settings
Coach
- Their assigned roster
- Progress, quiz results, and where people are stuck
- Message and nudge, sign off on steps
- No ability to change membership or content
A peer with a badge
Team captain
- Visibility of team standing and shared goals
- Team messaging and coordination
- No administrative permissions at all
Worked example
One franchise, four roles, no overlap
Twelve locations. Nobody sees more than they should.
Permission hierarchy
12 locations, roughly 90 people
Sell
Regional director buys 90 seats as organization admin
She sees all twelve locations rolled up.
Delegate
Each location manager is a group leader
They see their own staff and nobody else’s.
Delegate
Two coaches assigned across locations
Progress and messaging only. They cannot move anybody between groups.
Enroll
Each location appoints a captain
Team standing and coordination, zero admin rights.
Report
Four reporting views, one data set
Each one answers the question that role actually has.
Recipes
Three you could build this afternoon.
Start narrow
When
Only if
Then
Separate seeing from changing
When
Only if
Then
Roll up, do not flatten
When
Only if
Then
Before you build
Three things worth knowing.
Note
Draw the line between people permissions and settings permissions. Most role confusion comes from mixing them.
Note
A captain is a social role, not an administrative one. Giving captains admin rights is a common and regrettable shortcut.
Note
Document who can do what before you have twenty managers. Reconstructing it afterwards is genuinely difficult.
The rest of TEAMS
Multiple Admin Levels is one of 7 parts.
Team & Cohort Management
Credit, Seat & Token System
Bulk Enroll
Admin Management
Multiple Admin Levels
Course & Content Access Control
Team Reporting
Put Multiple Admin Levels to work.
Tell us what you are trying to get members to do, and we will show you the Flow that does it.