Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage
Highlighted

Opsgenie Best Practices "Wednesdays"- Don't have too many cooks (read Admins) in the kitchen.

Kate Clavet Atlassian Team Mar 21, 2019

It may seem intuitive to some, but a common mistake that folks make is giving too many users in their account Owner or Admin roles. These roles have the power to change many configurations in the account, delete alerts, etc. Some customers have given Admin permissions to too many users who inadvertently close alerts when they shouldn’t, change configurations, or disconnect/break integrations.

Even with the best intentions having too many folks holding the controls can wreak havoc, similar to adding too many ingredients to a soup. A good rule of thumb is to give only the permissions truly necessary for a user to complete their job duties. Opsgenie has four main role categories:

  • Owners can manage any setting (global or team-based) for the entire account including subscription and billing details.
  • Admins can manage any setting (global or team-based) for the entire account excluding subscription and billing details.
  • Users (Default settings) are able to access alerts and incidents that affect them and manage their own settings but don’t have visibility into the global account as a whole or the ability to delete etc. There is the ability to customize user roles, see more here.
  • Stakeholders can manage their own profile settings and contacts and review the status of the services they are listed as a stakeholder on. But they can’t receive alert notifications, be part of a team, escalation or a schedule. The purpose of the stakeholder role is to keep the user informed.

For full explanation of each role, see our docs. What are some Best Practices you follow? Feel free to contribute your thoughts! 

0 comments

Comment

Log in or Sign up to comment
TAGS
Community showcase
Published in Opsgenie

New! Investigate and re-deploy stable deployments from the Incident Investigation view in Opsgenie

We’re excited to announce the latest enhancement to Opsgenie’s Incident Investigation view. Now when an incident occurs users can select the previous stable deployment, and begin the redeployment pro...

314 views 0 3
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you