Atlassian Cloud collaboration basics

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

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 products and Confluence from one central place, the Site administration.

In the future, Atlassian Cloud will also include Bitbucket, Hipchat, and Statuspage. Refer to Atlassian Cloud's future vision below for details of our future vision for Atlassian Cloud.

This page

Atlassian Cloud sites

An Atlassian Cloud site is a set of cloud products with 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 site could include, there is Jira Software, Jira Core, Jira Service Desk, and Confluence:

Cloud site administrators

As a site admin, you can manage one or multiple sites. For each site, you'll grant users access to your site's products and content. Each site is independent, so you can maintain two sites with different sets of users, or overlapping users.

This section describes scenarios for how you might manage an Atlassian Cloud site.

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

Your cloud site includes all the cloud products and the Site administration where you grant access to users and manage groups. As a site admin, you grant users access to one or more products. Atlassian accounts exist outside your site, and may access other cloud sites. Unmanaged Atlassian accounts are individually managed, and you can't manage them as an administrator.

As an example, consider the hypothetical Teams in Space startup with 10 employees. Will is an admin for their Atlassian cloud site. All Teams in Space employees have individually managed Atlassian accounts that are set up with their work email addresses. With an unmanaged account, users can make changes to their email address, their full name, and other profile details without getting Will involved. Will does manage their access to the Jira products and Confluence.

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

As a cloud site admin, you can verify your domain so as to obtain more control over the Atlassian accounts that have access your site. Once you do that, you can now enforce security policies on those managed accounts. Atlassian accounts not covered by your verified domain remain unmanaged, but you still have control over their access to your site.

Teams in Space now has 100 employees, so Will starts to get serious about managing all those account efficiently. 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 email addresses using the teamsinspace.com domain become managed accounts. Alana receives an email letting her know that her company now manages her account.

Will can now directly change the email addresses and full names of those managed accounts, and can 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 company, you might administer two or more cloud sites. Because Atlassian accounts exist outside your sites, your users don't need separate Atlassian accounts to access both. Some of your users might also have access to other sites, such as a vendor's site.

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, that 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 Teams in Space password policy applies to them here too as they access the DSS site.

Atlassian Cloud's future vision

We want Atlassian products to be simple and secure for admins and end users alike. For end users, Atlassian account simplifies access and security across all our cloud products, with features such as SAML single sign-on and two-step verification. We think Atlassian account provides a basis for better collaboration within and across teams, and even across the whole company. For admins, Atlassian accounts allow centralized user management and security policies across all your sites.

Atlassian Cloud currently includes the cloud versions of Jira Software, Jira Core, Jira Service Desk, and Confluence. You manage users of your Jira products and Confluence from the Site administration. If your company also uses Bitbucket, Hipchat or Stride, you manage user access separately within those products.


We're moving towards simplifying the admin experience by combining the access and security management of all users into a single location. 

Hipchat, Stride and Bitbucket will become part of your Atlassian Cloud site and you'll manage users for these products from within the Site administration.

Last modified on Jun 4, 2018

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.