Atlassian Cloud collaboration basics

Atlassian Cloud currently includes the cloud version of these products: JIRA Software, JIRA Core, JIRA Service Desk, and Confluence. You manage your users for your JIRA applications and Confluence from one central place, the Site administration.

In the future, Atlassian Cloud will also include Bitbucket, HipChat, and StatusPage. Refer to (link here) for details of our future vision for Atlassian Cloud.

This page

Atlassian Cloud sites

An Atlassian Cloud site is a set of cloud products that includes one central place where you administer the site. Your site may include any combination of cloud products. At the center is the Site administration where you manage your users, their access, and policies that apply across products.

In this example of what your sites could include, you'd have JIRA Software, JIRA Core, JIRA Service Desk, and Confluence as part of your site.

Cloud site administrators

As an administrator, you can manage one or multiple sites. For each site, you'll grant other users access to your organization's products and content. Each site is independent, so you can maintain two sites with different sets of users, or overlapping users. Refer to our user site access description for more information about these types of users.

The rest of this section details how you manage an Atlassian Cloud site.

You administer one cloud site and grant access to personal Atlassian accounts

One cloud site encompasses all the cloud products and the Site administration where you grant access to users and manage groups. As an administrator, you give users access to one or more products. These accounts exist outside your site, that way they can gain access other cloud sites. Their Atlassian accounts are personal, which means you can't manage them as an administrator.

Teams in Space is a startup with 10 employees. Will is an admin for their Atlassian cloud site. The company is still small enough that they don't have to worry about security. All Teams in Space employees have personal (individually managed) Atlassian accounts set up with their work email address. With a personal account, users can make changes to their email address, their full name, and other profile details without getting Will involved. Will does manage access to JIRA and Confluence for their accounts.

You administer one cloud site and grant access to managed Atlassian accounts

When you administer a cloud site, you can verify your email domain to manage the Atlassian accounts of all users with that email domain. Once you do that, you can now enforce an authentication policy on your managed accounts. Any users without your organization's domain remain personal, but you can still grant or revoke their access to your site.

Teams in Space now has 100 employees, so Will starts to get serious about security. He wants to make sure everyone logs in securely by enforcing a password policy. He verifies the Teams in Space domain: teamsinspace.com. After he completes the domain verification, all Atlassian accounts with the teamsinspace.com domain switch to managed accounts. Alana receives an email letting her know that her company now manages her account.

Will can now directly change email addresses and full names of employees with managed accounts and require a strong password. The two external users still have access to the site but the password policy doesn't apply to them.

You administer one cloud site and grant access to portal only customers

If your cloud site includes JIRA Service Desk, you may want to give customers access so that they can create requests and get support. JIRA Service Desk has two different types of users, your cloud site's users that have an Atlassian account and your customers that can log in with their portal only customer account, which isn't an Atlassian account. You have more control over these portal only customer accounts and can update their email addresses, full names, and passwords as needed.

You can upgrade a portal only customer account to an Atlassian account to grant it product access. Once upgraded, it's not possible to downgrade. You'll have to create a new portal only customer account instead.

As Teams in Space grows to 1,000 employees, it starts to provide customer support for the company's major product with JIRA Service Desk. Mia is a customer of Teams in Space. She visits teamsinspace.com seeking support and gets directed to a registration page for JIRA Service Desk. She registers for a customer account and can now get support. She doesn't have an Atlassian account, only a customer account, which means that Will can update her email address, full name or password if she forgets any of it or her information changes.

You administer multiple cloud sites and your users have been invited to access vendor cloud sites

When you have a large organization, you might administer two or more cloud sites. Because your users exist outside your sites, they don't need separate Atlassian accounts to access both. Some of your users might also have access to other sites that a vendor owns.

Teams in Space now has 10,000 employees and not all of them use the original site. Alana is one of those employees at Teams in Space with a managed account.

Alana decides she wants to start using Atlassian products with her team, so she sets up her own cloud site and starts inviting users, which gives them access to the products associated with her site. Because Will manages those accounts at the original Cloud site, Will's password policy applies across both sites that users can now access.

Around the same time, Teams in Space starts working closely with a vendor called Deep Space Suppliers, which has their own Atlassian Cloud site. Harvey administers DSS's site and invites a small list of Teams in Space employees to his site. Because these employees are still managed by Teams in Space, the original password policy still applies to them here too as they access the DSS site.

Atlassian Cloud's future vision

We want to make Atlassian products simple and secure for admins and end users alike. Introducing Atlassian account for end users across our cloud products is an important step in making things simple and secure. We hope it will foster better collaboration within and across teams, and even across organizations. Making products simple and secure for administrators involves centralising the user management across products and ensuring you can apply security policies effectively.

As previously described, Atlassian Cloud currently includes the cloud version of these products: JIRA Software, JIRA Core, JIRA Service Desk, and Confluence. That means that you manage your users for your JIRA applications and Confluence from the Site administration. If your organization also uses Bitbucket and HipChat, you grant those users access separately within these products.

Your users exist outside of your products, so you can access them from any of them. You manage and grant them access from the Site administration and from Bitbucket and HipChat.

Next, we'll build the access and security management for all users into a single location, simplifying the experience for administrators. When that change happens, HipChat and Bitbucket will become part of your Atlassian Cloud site and you'll manage users for both these products from within the Site administration.

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport