Proposal to prevent Accidental Site Creations #accidentalit

[#1]

As I've documented, "managed" users in claimed domains continue to accidentally create Jira and Confluence sites because the public landing pages for those products kind of "trick" them into going down the wrong path.

I was thinking that other SaaS products must have similar issues. Here's why they don't.

If you go to http://asana.com, here is an non-user sees vs a user who is currently/has previously logged in:

Similarly, https://www.airtable.com also somehow "knows" who you are and doesn't try to trick you into signing up for a new service.

Alas, when a logged-in user ends up on https://www.atlassian.com/, instead of showing them a list of existing sites the user has access to, it prompts the user to sign up for a new site.

You can see it "knows" me, because there's my name and profile photo in the top-right corner. (Which actually adds to the confusion later when it Welcomes you to your new site by name, and auto-suggests a new site name that includes your Org name.)

What's FRUSTRATING is that it SEEMS like Atlassian is working on this. If your cookies/sessions are "just so", you will sometimes get this page when going to  https://www.atlassian.com/software/jira

But for https://www.atlassian.com/software/confluence users will see this:

Probably the saddest thing is that there are teams at Atlassian who have spent time putting together a "portal" site at https://team.atlassian.com/ (or is it https://home.atlassian.com/ ?) that would be a perfect place to redirect already logged in users to:

But nothing automatically takes you there. "Atlassian Home/Start" is hidden/buried in the little Grid button next to your avatar/profile pic.

I'm sure some of you use other SaaS tools that deal with this better than Atlassian. I welcome your screenshots and examples. Thanks!

[Dave Liao]

Thanks for putting this together! I now want to test what happens in various SaaS tools in this particular scenario…

[Joe Johnson]

Props to @Darryl Lee for basically doing Atlassian's work for them! Sending in logged-in users direct to Atlassian Home/Start is clearly the right choice for this.