How to grant global space admin privs

[Eric Koepfle]

We run confluence in a very large financial institution. I was trying to create a "moderator" role that will allow some users to help maintain all the spaces.

I am perplexed that this cannot be done with the Confluence permissioning?

If I put them in confluence-administrators, they can space-admin every space, but they can also do ANY other admin activity.

If I grant them the "Confluence Administrator" Role, they get limited admin of Confluence, but they don't get global space admin rights.

Is the only alternative to declare them as a Space Admin on every space? And expose them to being shut out by the local space Admin? I see space creators can get local space admin, but that won't apply to a group.

Seems like a giant group role is missing: moderation. i.e. full control over content but not application.

And yes, I read all of the documentation and how a Confluence Administrator isn't a confluence-administrator (Really good naming conventions btw).

[Eric Koepfle]

I got the sense that that onlyh applied to new spaces? We have about 1000 existing spaces and I would like something the local space admins cannot remove. I will play around with it.

However I think I may have found another hack. I granted my group 'SETSPACEPERMISSIONS' permtype in the spacepermissions table where spaceid is null (global space). I didn't see a way to do this in the UI, I used sql. It seems that it is taken into account in the permissions algorithm too.

[MJ]

You could create a new group, add all users you want to have the moderation rights, and grant this group space admin permission through the default space permissions. This will grant them all the admin permissions within a space, whilts preventing them from perfoming non space related administrative tasks. The space permission settings of an individual space will override the default settings, so you can still shield off certain spaces from this group if needed. This page will provide you with more details on the difference between the default and the individual space settings, and how to configure them.

[Eric Koepfle]

Thanks, I got the sense that that only applied to new spaces? We have about 1000 existing spaces and I would like something the local space admins cannot remove. I will play around with it.

I think I may have found another hack. I granted my group 'SETSPACEPERMISSIONS' permtype in the spacepermissions table where spaceid is null (global space). I didn't see a way to do this in the UI, I used sql. It seems that it is taken into account in the permissions algorithm too.

[Eric Koepfle]

Thanks, I got the sense that those were only applied to new spaces, but I will play around with it.

[Sergey Svishchev]

Mick, is it definitely true that default space permissions are in effect for all spaces?

[Peter Van de Voorde]

No there are only applied on new spaces or spaces that don't use their own settings not on all spaces.

[Sergey Svishchev]

Thought so. Perhaps a feature request is in order -- to force certain permissions in certain conditions on and off (https://answers.atlassian.com/questions/284443/approve-or-restrict-a-space-permission-how)

[Hans-Peter Geier]

Mick's suggestion may be an administrative nightmare for large sites (it would require to edit permissions of many spaces) if you do this manually.

You may consider scripting this, e.g. through Bob Swift's CLI package.