We’ve broken up permissions into organization and team levels in order to allow orgs to define Team level permission per member, per team.
The benefit of this change is that you can have more granular control of permissions for each user. An engineer can have unfettered permissions for a team and all the projects in it, while at the same time, they can just have limited permissions to other teams/projects that they are tangentially involved in.
Say you are the mobile engineering manager, as a Mobile Team Admin you can do things like remove team membership, create alerts, and add new repositories to the team but the folks on your team, as a team member, will be limited to triaging issues for the projects associated with your team.
|Current Role||New Role|
|Owner||→||Organization Owner, Team Admin|
|Manager||→||Organization Manager, Team Admin|
|Admin||→||Organization Member, Team Admin|
|Member||→||Organization Member, Team Contributor|
|Billing Member||→||Billing Member|
Because the new roles mapping will be handled by Sentry, there should be no operational impact to your teams.
Yes, only at the team level. Each member will have one role at the organization level but can belong to multiple teams as either a Team Admin or Team Contributor.
Owners and Managers will automatically be made Team Admins for teams they are members of.
Yes. Existing Admins will be made Organization Members and Team Admins for all teams they currently are members of.
No. Organization Owners and Managers have the highest level of permissions.
Projects can belong to multiple teams. If projects belong to multiple teams, members will have the highest role for shared projects.
No, the role will have to be set manually.