-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
4
-
11
-
In reference to this feature:
[Create and manage an Atlassian team | Atlassian Support|https://support.atlassian.com/atlassian-account/docs/start-an-atlassian-team/]
I recently created an Atlassian "team". Afterwards, I noticed that the team is "open" by default and there is no way to change this setting. This seems to be a significant oversight. Teams should be able to be made private and controllable by the team owner so that the team can only be joined by invitation or by the owner adding a new member. There are plenty of scenarios where you wouldn't want anyone in the org to be able to join a specific team.
I also see that there is no way as an org admin to see these teams. This is also a significant oversight. As an org admin, I should be able to see, edit, assign owners and members, and even delete teams in our org. There should also be an org level setting to control if the org wants to allow users to be able to create teams. Without this kind of oversight users can and will eventually create a large number of teams which will eventually be ignored or left orphaned which will add significant clutter in the long run.
Please update Atlassian teams to be able to address the concerns listed above.
There have been a number of questions and comments on this asking for this functionality:
How do i make teams private? (atlassian.com)
Solved: How do I make a team private/closed? (atlassian.com)
How do I change a team to NOT be open (atlassian.com)
More context from similar requests:
#########################################
Summary
Only a current team member can remove a member.
How to reproduce
- Access "People" >> "Search people and teams".
- Find a group that you won't be a member of.
- Even a site-admin won't be able to remove a team member.
Improvement suggested
Site-admin should be able to remove a team member, or at least we should grant permission to a group to edit groups.
#########################################
- is duplicated by
-
- Closed
-
- Closed
- relates to
-
- Closed
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
[CLOUD-11945] Need admin controls for Atlassian teams
Hey 7627d68c7dfd
Thank you for the comment, we currently have a separate ticket tracking just the bit you mentioned. Please follow it here https://jira.atlassian.com/browse/JRACLOUD-75734
Adding my voice to everyone in here. Teams seems like a very open and uncontrolled concept. We need Adminstration controls in order for them to be useful.
@Yerbol, regarding the changes and comments you made.
The issue is that anyone can join a team and then kick anyone else out. There are no ownership permissions for a team. They are all completely open and uncontrolled. The ability to even let users make a team should be something that is configurable by admins. If an org doesn't want users to be able to make teams, they should be able to block that ability.
I'll add my voice to Phil above, users who join teams have full control to do anything with that team. There does not appear to be any way to secure or otherwise restrict access to these teams beyond an immense amount of work with security policies and permissions. Please add what should have been standard functionality to the "Team" aspect of Atlassian.
I have also just discovered that after joining any team, I now have the ability to delete that team. This is also a significant problem. A rogue user could join and then delete any team in our org. This needs to be addressed with urgency.
Now that it appears Teams is also connected to the newly migrated Opsgenie, we have no ability to manage/update/edit the Teams. Too much rogue functionality creating a wild west scenario. It is getting near impossible to mange or Admin Jira with this type of functionality. This is my number one hated field in Jira. I removed it from most of the projects were I could.
Then, again, I just came across a use case that kinda made me a bit surprised, I kinda liked telling them if they want it to work the way they expect, they need to manage the team membership accordingly. Kinda felt good.
But I still don't like not being able to access it in case a Jira Admin is needed.