Organization Administrator as an assignable role [Preview]

[glider-bot]

Value Prop

Today, organization administrator is a special "membership type", that isn't assignable using the standard roles and permissions system. The biggest implication of this is that teams cannot be assigned the "organization administrator" role, and requires users to manually be given the role.

When the organization administrator role is supported, administrators will be able to:

1. Assign the role to a team, which has the side effect of making it possible to @mention all the admins (if you like).
2. Link that team to an IDP group
3. Use your IDP to then manage who an administrator of that organization is.

JIT permission management systems, such as PIM, can also use this to elevate users to the "admin group" on demand, to let them take actions that aren't supported by the custom role platform yet, and then automatically drop back to standard permissions.

Expected Outcome

Organization administrator will be a role that can be assigned to a team, like any other role at the organization level. Users in that team (or a child team) will be full administrators of the organization it's assigned in.

In the future, organization administrator will also be available from the enterprise level, so that users and enterprise teams can be assigned that role against multiple organizations at once.