-
Suggestion
-
Resolution: Fixed
-
None
-
103
-
-
Jira Software
Update Oct 15 2024:
Hi, we are happy to share some new updates to this ticket in regards to the following issues listed:
- Ability to create new sites for Jira and Confluence
- Ability to create new Bitbucket or Trello accounts
- Ability to join sites or products external to the organization
- Ability to remove managed users from external sites
- Ability to remove access to specific products
We have solved these issues through both proactive and reactive controls for user-created instances (also referred to as sites), and an organization admin’s ability to control them.
With our Atlassian Guard (formerly Atlassian Access) feature automatic product discovery, admins are able to see what user-created instances exist within their cloud footprint and join these instances to take over control. By doing so, they can remove certain users, products, etc. - and determine the best next steps.
With the Enterprise plan feature product requests, admins can set a policy and then either deny or approve requests for a new user-created instance. This feature is available to customers who have a Jira, Confluence, or Jira Service Management Enterprise plan - and coverage now expands to Trello and Bitbucket (Premium plan, in beta).
For further information, please refer to our latest community post: An update on product requests: bringing shadow IT controls to Trello and Bitbucket
- supersedes
-
- Closed
[CLOUD-11690] The ability to remove managed users from external sites
Can this finally be implemented, please - as the initial request (comp. https://jira.atlassian.com/browse/ACCESS-1468) is already from 30/Jan/2020 ???
This is genuinely asinine since this request https://jira.atlassian.com/browse/ACCESS-1468 is being split into multiple issues.
When people talk about rigging the vote, diluting the constituency, invalidating the polls, or just generally intentionally missing the point, this is EXACTLY what they mean, this ticket and its siblings, right here.
Yes, we're mad about this. This is infuriating.
See also: Gerrymandering - Wikipedia
nothing like a company trying to hide feature requests by moving it to new tickets and delaying development.
Even if the user never logged in on the external site, it cost an Atlassian Access slot
Product access for external sites is not manageable.
So the visibility I more or less have, but the abillity to decrease the bill by removing the user is not directly in my hands. Unless a lot of manual effort to fix this.
an essential feature of atlassian access. But what's the point of paying so much for it?
This is a critical need for our business. Users at my company signed up for products prior to our corporate licensing of Atlassian. This results in fractured products that requires a lot of manual effort to fix.
As Org admins we should be able to control what we allow users to do on out tenant. please enabled these features asap