You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I'm testing OpsGenie for use with a large enterprise that utilizes SSO. I've been unable to find any kind of documentation that describes what happens when I remove a user from my third-party SSO provider instead of within OpsGenie. Does the user get automatically removed from on-call schedules and teams? Or do they go inactive and need to be manually cleaned up?
Any kind of clarity into this would be much appreciated!
Hi @Josiah Tillett ,
I believe the user would need to be removed from within Opsgenie even if they were removed from your SSO. And I believe they would remain active as well even if removed from SSO.
A user cannot be removed / deleted from Opsgenie until they are removed from any schedules and/or escalations they are configured in: https://support.atlassian.com/opsgenie/docs/add-invite-update-and-delete-users/#Deleting-users
Removing them from schedules and escalations needs to be done manually, and by design so no workflows are interrupted or affected.
Is there any way to identify if a user has been removed from SSO without waiting the 90 days for their account to go inactive?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.