The /user list macro is on the list for removal in Confluence.
https://support.atlassian.com/confluence-cloud/docs/learn-which-macros-are-being-removed/
We use this a lot to manage groups, which can only be altered by site admins. However, space admins and project managers need to understand who is in which group in order to manage the permissions efficiently.
The proposed alternative on the removal communication is mentioning teams, but teams can't be used for permission management?
Is there an alternative approach that we are overlooking?
Hey Steven - Welcome to the Atlassian Community!
This move comes more inline with how Jira does it as well. Group management has to be done by someone with Site Admin permissions. Not saying that is good or bad, just that it looks like Confluence is moving to that same model.
Hi John,
Thanks for the remark.
We are a relatively large organisation with international locations, with many teams, many projects, ...
We need to be able to manage permissions based on groups (not possible based on teams). Site admins have too many rights to give to a lot of people, so we need to be able to communicate about group members. Communicating about group members seems impossible without the /user list macro.
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.