Context
The platform is migrating from a legacy role-based system to a new fine-grained permissions model. In the current production setup, users who currently hold admin role can view admin team members but cannot create, update, pause or delete them. In the new permissions model, all team member operations — view, create, update, and delete — are grouped under a single on/off switch, making partial access (e.g. view-only) impossible to represent. This means the admin role's current state cannot be preserved as-is in the new system, and a decision is needed before migration to determine which direction to go.
How should the admin role's team member permissions be set when migrating to the new permissions model?
You answered on Apr 17, 2026 at 1:39 PM
only Super Admin can see other Admins and create other Admins
Your answer
Revoke all access — the switch is turned off; admins lose the ability to view team members entirely
Grant full management — the switch is turned on; admins gain view, create, update, and delete permissions for team members
None of the above — I'd like to talk through the tradeoffs first.