Would love some help understanding Permissions with Opsgenie After Migration

[Calvin]

Hi all, would love some help understanding permissions, what I think I understand right now is

Org Admin - Configures Site Access - allows changes to a particular site, like domain name etc. And Teams Changes.

Product Admin - Configures access to the product itself, assuming Jira Service Management, you then can provide

• Product Access - Access to JSM itself, which might not necessarily be the project. They will also be known as an agent?
  • Each project also has its own permissions for customer/Project Admin
• Admin Access - Access to JSM Itself but also admin features such as editing Systems, Products and Projects
  • They can also update users/add users to groups?

For Opsgenie they used to have their own user/admin access.

After the migration, if they exist with "Product Access" then they will come straight across. If they don't, you have to provide the user "Product Access" which then adds them as an Agent of the product aka agent access to the Jira Service Management instance (and a license). Which then lets them use JSM and Opsgenie/Operations.

Is this right, or am I very very wrong? Cheers!

[Fabian Lim · Accepted solution]

Hi @Calvin

You are correct. Also you need to assign members as team administrators so that they can add members, configure schedules and integrations. 

Regards,

Fabian

[Calvin]

Thanks heaps Fabian! Do you also know is Org Admins the only one that can assign team admins? I tried in our environment as a product admin and it seems it doesn't let me.

As our Org Admin is currently out of office, thats a super worry because if an opsgenie team admin doesn't come across with product access. No one can add or touch that team :(.

[Fabian Lim]

Yes, I did notice that. Always good to have a few org admins available.