Deactivating the @admin user in Jira/Confluence Cloud

[Mathew Cooke]

I'm the original user of our organisation's Jira/Confluence cloud instance, so have been granted the @admin username.

In the organisation I work at, there are now other people with full Jira/Confluence admin permissions and billing is now managed outside of my account.

So, when it comes to me leaving the organisation and my @admin account being deactivated, is there any pitfalls to this? Is there anything else we should be doing to prepare for the eventual deactivation of the @Admin account?

[CARLISLE]

More than likely on the authentication side of the aisle, you will not be able to take the credentials outside of the walls of your network. This stuff will be different at each Atlassian site in various countries and places.

Someone from within your organization will have to do a clean sweep so to speak on your credentials and reset everything for your internal team to take over after you leave.

Generally speaking the on-boarding and the exiting process will be managed by your internal networking/DEVOPS team for litigation, liability, and risk reasons.

[Mathew Cooke]

Cool.. I guess my question is really getting at, is there anything special about the first account to have been created on the cloud instance of Jira/Confluence (hence the automatic allocation of the @admin username)?

If it's just another admin account, then I'd expect everything to work fairly normally once my account is deactivated, (based off the various important roles I see having already been shared with other people in the organisation).

[CARLISLE]

Good question - I would think it was like a Building Manager that has all the keys. Anyone could take that role at any point in time and all locks do not have to be changed?

I would check with Atlassian directly on that point.