Scoped roles and permissions

[ackernaut]

Background

I’m starting this to gather thoughts on how to move forward regarding roles and permissions in our app. This is 1 of many concerns found in #5661 and other discussion and issues. I’m trying to break down those concerns into more manageable conversations so that we may identify next steps and slowly break down the work.

For reference:

• Administrative IA feedback, concerns, and open questions #5661

Are there different permission roles (billing leader vs. super admin vs. team lead vs regular user) and how do they interact with the design?

• These comments on Administrative IA feedback, concerns, and open questions #5661
  • Administrative IA feedback, concerns, and open questions #5661 (comment)
  • Administrative IA feedback, concerns, and open questions #5661 (comment)
• These issues
  • Design Meeting Permissions UI #4540
  • Participation/permissions/sharing UX, user job stories defined #4950

Open questions

• What are the main user job stories of roles? Who wants to see team health and insights without being on the team? Who wants to see overall team usage and user membership to manage the account?
• What’s the best framework for building this into our app? Who can see what? Who can control what?
• How can customers better manage their roles and permissions? How can we help folks get unblocked on roles when folks leave, etc? E.g. a team lead leaves the team, and nobody on the team can manage the team
• How might we map roles from SSO/SCIM?