-
Suggestion
-
Resolution: Unresolved
-
None
-
43
-
1
-
User Story
As a Confluence administrator I need to be able to grant permissions to user-created "team" objects in addition to individual users and groups because these are the only multi-user objects editable by non-admins and I do not have time to manage everyone's groups.
Context
Group management in Atlassian tools has been a tremendous pain point since...ever.
- The typical Confluence administrator pool is very small
- In even a medium-sized organization, the number of create\add\remove\delete actions on organizational units can be high.
- As of now, it's still not possible to sync groups from third-party IdP's, so any group management you want is going to be manual.
- In addition to their official OU's most organizations have a secondary set of informal groups beyond the "official" ones, whose memberships are both fluid and not recorded.
"Teams" seems like a great compromise - it's like a group, but users can maintain them - however as of now you can't actually do anything with a 'team'. It just exists in the system like a bicycle designed for fish, taunting us with it's unrealized potential.
More context from a related ticket:
(For Jira and Confluence / Atlassian Cloud)
Please add more functionality to "People and Teams."
More specifically: Be able to use Teams in Space Permissions and Page Permissions like regular managed Groups in Atlassian Cloud. Currently, users can only use Teams by @mentioning them in Jira tickets or Confluence pages. User want to be able to create their own groups and manage the members.
- is duplicated by
-
- Closed
[CONFCLOUD-75232] Allow Granting of Permissions to "Team" objects
Please add this feature - we want to store our "Retrospectives" on Confluence, based on the provided template. However, access should be restricted to the team, hence permissions should be managed on the team (not individual) level.
That would be an absolute game changer for us.
If the users are able to create teams and use them in Jira and confluence to set permissions we would have a huge benefit.
While we wait for this one, ScriptRunner has a workaround that might help. You can combine the functionality of Jira Groups with the Team field while keeping members in sync. We’ve written up a tutorial with example scripts here.
In my organization there are many projects followed from many teams. The teams can also change their members on the road.
It should very great to have the faculty to enable or not for a team the permissions to edit a space or a group of articles.
Yes, please, we would like to be able to add and remove members to and from our working group team to give permission to edit team pages, without having to pester an administrator each time.
+1 on this
Having to manage multiple groups as admin is a pain when people come and go all the team. Giving the end user the ability to go and add members to a team and then for that team to have edit/view permission capabilities on a space or page is something that should have been implemented a long time ago.
8fc8181ac0d1 you're correct; I don't quite remember when but this is possible now. You can even provision licences on those groups!
So as long as your IT\Authentication team doesn't mind owning group management... 😂
I agree. The ability to create a team and assign it to pages would be great. This would allow a user to simply maintain the team and have the access permissions transfer down to all the pages/spaces without having to manually add and remove individual users across several pages/spaces.
I believe this one point is not quite right, IF you have configured Atlassian Access (soon to be Guard Standard) and setup user and group provisioning:
- As of now, it's still not possible to sync groups from third-party IdP's, so any group management you want is going to be manual.
https://support.atlassian.com/provisioning-users/docs/understand-user-provisioning/
Our Confluence site admins don't have time to set up groups for the entire organisation and manage them every time someone joins or leaves. This is another really basic concept that seems to be difficult to manage on Confluence for some reason.
I wish I could go back to the old version of Confluence of about 10 years ago where functionality was simple and intuitive. There are too many features now that we'll never use and not enough effort being spent on simple, useful things, like this.
Let me manage my own groups (teams) within my own space! I shouldn't have to raise a Jira ticket, then wait for ICT (our site admins) to do this, I should be able to do this myself!