-
Suggestion
-
Resolution: Unresolved
-
None
-
64
-
Problem Definition
The site creation flow currently doesn't doesn't require any confirmation and minimal manual input from the end user.
Although convenient, this poses an issue for org. admins who manage existing company Cloud sites and may have either already invited the user to their Cloud site or have configured "Approved domains" based self sign-up flows.
The end user may not be aware of existing company managed Cloud sites and found the site creation flow via a search engine. If a user finds their way to https://www.atlassian.com/try/cloud/signup?bundle=jira-software&edition=free via a search engine, logs in or creates a new Atlassian account - they are able to create a new Cloud site with a couple of button clicks.
Suggested Solution
- Suggest available site names instead of pre-filling the "Your site" field, having to manually enter/select a new site name may prompt the end user to realize that they are creating a new Cloud site and exit the flow if their intention was not to create a new site
- Use of the word "new", e.g. "Your new site name" instead of "Your site" on the Cloud site creation flow. Other examples of current wording is "Create a site" or "Welcome back, [FirstName]":
- Introduce a confirmation prompt to make sure that the end user is aware that they are creating a new site instead of joining an existing site. The confirmation screen can state that the end user that they will become an org. and site admin of the newly created site - perhaps this is not what the end user was looking to do
- Offer ways the end user can exit the flow - an end user may realize the flow won't lead them to an existing site, but at that point, the only way is forwards("Continue"). Clicking "Continue" currently creates a new cloud site without any additional confirmation
- Make suggestions to join existing sites based on any "Approved domain" flows available to the end user: CLOUD-12189
- If a user is currently logged in to their Atlassian account, and they have access to an existing site - then suggest that the user log back into that site. This is the current experience on the www.atlassian.com page and https://www.atlassian.com/software/jira, but not on Cloud site creation flows:
Why this is important
- Sites are being created erroneously/accidentally and creating overhead for org. admins who then need to take control of the sites/orgs. and delete the sites/orgs.
- This experience causes friction with the end user if their intention was to join an existing site, but they found their way to the site creation flow via a search engine with no obvious way to exit the flow once started
- The behavior between Atlassian's products is not consistent and the inconsistency might be confusing to customers. An end user can search for "Trello" on their favorite search engine and find their way to company workspaces or boards shared with the end user via the search results. That is possible because Trello is a non-tenanted application. For Jira or Confluence it's not always possible for end users to "search" their way to their company's Cloud site
- Important to find the optimal balance between lowering friction relating to new site creations and managing increased friction from dealing with accidental site creations(deletions)
- It is widely understood that unless the: Manage your users requests for products feature has been configured(if available), end users are still able to create new Cloud sites. The intention of this Suggestion ticket is not to block new Cloud site creations, but to reduce the occurrences of accidental site creations
Workaround
N/A
- is related to
-
- Gathering Interest
-
- Gathering Interest
- relates to
-
ACE-6976 You do not have permission to view this issue
[CLOUD-12193] Reduce occurrences of accidental site creations
I just checked the sign-up flows for Confluence and Jira again, and it actually looks like some changes have already been made that will help with this ticket. For example, the following procedure:
- Go to https://www.atlassian.com/software/confluence
- Click "Get it free"
- Enter your work email address
- Sign in via your identity provider
This used to result in a page that prompted you to set up a new site with the site name pre-filled, but now it's showing a page with a big "Go to confluence" button that takes you to your existing site, with a small "start new site" link down the bottom. Same thing with Jira.
So hopefully fewer new sites being accidentally created now?
(Edit: replaced image with text)
Give me the ability to disable this customer hostile garbage for free. You should not be charging extra to turn it off.
Same here!
I also highly recommend anyone to send your opinion on this topic to the CEO of Atlassian:
Besides that, you can also comment/follow/vote all articles/issues/request that apply for you:
- https://jira.atlassian.com/browse/CLOUD-10325
- https://jira.atlassian.com/browse/CLOUD-11690
- https://jira.atlassian.com/browse/CLOUD-12089
- https://jira.atlassian.com/browse/CLOUD-12193
- https://jira.atlassian.com/browse/ACCESS-1135
- https://jira.atlassian.com/browse/ACCESS-1272
- https://jira.atlassian.com/browse/ACCESS-1468
- https://jira.atlassian.com/browse/ACCESS-1645
- https://jira.atlassian.com/browse/ACCESS-1651
- https://jira.atlassian.com/browse/ACCESS-1679
- https://jira.atlassian.com/browse/ID-7697
- https://community.atlassian.com/t5/Articles/What-s-the-word-I-m-looking-for/ba-p/2862486
- https://community.atlassian.com/t5/Confluence-questions/SECURITY-ISSUE-during-login-procedure-of-managed-users/qaq-p/2841895
- https://community.atlassian.com/t5/Atlassian-Account-questions/How-to-Prevent-Atlassian-Products-being-added-by-users-w-company/qaq-p/2401874
- https://community.atlassian.com/t5/Questions/Why-is-Atlassian-promoting-Shadow-IT-Or-Accidental-IT/qaq-p/2731538
- https://community.atlassian.com/t5/Enterprise-articles/An-update-on-product-requests-bringing-shadow-IT-controls-to/ba-p/2840760
- https://community.atlassian.com/t5/Articles/Proposal-to-prevent-Accidental-Site-Creations-accidentalit/ba-p/2867193#M558
"Atlassian support's vision of solving this problem is completely disconnected from reality."
I love this statement. 100% on target. Atlassian doesn't feel like it's on the "same team" as its org admins any more. The product has been intentionally evolved/mutated to work against the administrators trying to maintain it.
We are also evaluating other options as my confidence and satisfaction with Atlassian products erodes away.
Hello,
We faced a similar reply as 408621841d67 . We are an organization with nearly 30,000 users in the information system, and Atlassian support's vision of solving this problem is completely disconnected from reality.
I do not understand why the ability to configure this setting is restricted to Enterprise versions of the products. This configuration makes no sense. As the organization administrator, I should have the ability to make these adjustments, not the product tied to a specific license.
For this and several other reasons, we have gradually started moving away from Atlassian services and products because they simply don’t focus on what actually needs to be resolved. The funniest part is that when someone complains, they are referred to the implementation policy or the bug and update policy. But none of the managers seem to care that there are publicly available tickets that haven’t been touched for as long as 12 years. This is despite the claim that the more votes a ticket has, the higher its priority should be.
For me, Atlassian's attitude and approach are a big disappointment. Years ago, I thought everything was great, but now...
Hello, I have guard and the same concern. users at the first connection, connects with the wrong url and it creates a site, then we must unsubscribe and wait to delete the site. The support gave me this solution:
- to communicate the url of my site but this won't be done for new users and I'll have the same problem with each new user.
- One way to tackle this is by introducing a firewall rule in your corporate network/VPN. This will restrict access to certain addresses, like:
• https://admin.atlassian.com/o/create
• https://www.atlassian.com/try
• https://www.atlassian.com/try/*
By doing this, your managed users won’t be able to create Atlassian organizations themselves. This means no accidental product creation and a more secure environment for everyone!
Note: This rule won’t block you from adding products to your current organization, but it will prevent the creation of separate cloud sites.
but for me, it's a bug that you needs to fix
8f4050917dd7 we do use Guard. I've done that a few times before (take over admin), but there are some I cannot, plus there are so many steps to do in order to delete...I cannot do that for almost 50 sites.
I have to go kill about 3 sites a month, and for each of those, I have to wait 3 months for data deletion. Reducing the occurrence is most welcome.