Changing a board/project ownership

Whisley Santos_ihi4k8

Hi guys,

 

First things first, we use Google authentication to log in. I will get back to this later...

In order to don't lock the teams out when a key user leaves the company, I :

• Change the user Google password
• Change Confluence/Jira permission groups to the basic one

But this is far to be a solution. I have checked old posts here but they were mixed so:

• How can I safely change the Confluence Board owner without blocking access/losing anything?
• How can I safely change the Jira Project owner without blocking access/losing anything?

 

My main fear is that a wrong move and adios, nobody can change anything. We don't have the top subscription that gives you that "admin key" which I believe makes you a God there so there is nothing to fear.

Getting back to Google authentication, that forces me to keep the user account active, so paying for something that you are not using, without mentioning the security risks that could be possibly involved.

 

Thank you for any info.

 

Ste Wright

Hi @Whisley Santos 

It's important to setup Jira and Confluence so Administrators can assist when problems occur - however there are lots of good administration tools to help where needed.

I just want to clarify:

• Confluence Board Owner - this would be Space Admin?
• Jira Project Owner - this would be Project Lead?

I would ensure:

• Space Admin: Either the group "administrators" or "site-admins" has Administration access on each Space. This ensures you have access to help with access when needed. You can set the standard permissions for a new space via Confluence Settings > Space Permissions.
• Project Lead: This is less of an issue as project access is based on Project Permissions - like with Confluence, I would ensure the "Administer Projects" permission is assigned to "administrators" or "site-admins"

And if you get stuck:

• Jira: If a user leaving causes a project to become invisible - Admins have access to permission schemes. So an Admin could modify the permission scheme to provide wider access, thus unhiding the project.
• Confluence - Spaces: If a user leaves and it causes a Confluence space to become hidden - or no-one has access to the Space Admin - you can recover the permissions. Go to Confluence Settings > Space Permissions. From here you can "Recover Permissions" for any Space, which provides you all permissions within a space
• Confluence - Restricted Pages: A Space Admin can un-restrict pages. Go to Space Settings > Permissions > Restricted Pages - then press a padlock to remove edit/view permissions from a restricted page. To unhide a page, you'd have to remove all "view" restrictions from users, for example.
• Confluence - Personal Spaces: Confluence Admins can see all Personal Spaces. You can use the recovery of permissions / restricted pages to access pages in these spaces for users who have left the business.

------------------

For Google Auth - we utilise G-Suite to manage account access.

We can still remove the user's product access though, via Jira Settings > User Management. Just having site access (without product access) doesn't utilise a licence.

Ste