Units: Frequently asked questions

Basics and setup

Who can use units?

Units are included in the Enterprise plan and are opt-in, so nothing changes until an organization admin enables them. Some organizations not on the Enterprise plan that already have several sites, each with its own user directory (original user management), can view and manage units but can't create new ones.

How many units can my organization create?

Organizations on the Enterprise plan can create up to 150 units. If you don't need to separate teams or data, you can keep all your users, apps and sites in one unit.

Can I customize my units?

Yes. Organization admins and unit admins can name and rename units, add a custom icon, and add a description. The description appears in the unit switcher so users can tell their units apart.

Can I turn on units for only part of my organization?

No. Units are enabled for your whole organization at once. After that, you can create a new unit to test how boundaries work. A new unit doesn't affect your existing sites or units. If you'd like to test in an environment separate from production, contact your Atlassian account team about a demo organization.

How will my organization change after I enable units?

New Enterprise organizations start with one unit and can create more at any time. Existing Enterprise organizations will see Units in the side navigation of Atlassian Administration once it's available. You can then opt in and follow the setup steps.

What changes: all your existing sites and apps are placed inside unit boundaries.

• If your organization uses centralized user management, you start with one unit that contains all your sites and apps.

• If it uses the original user management experience, each site becomes its own unit.

What users notice: units don't change any existing permissions.

• In centralized user management, users won't notice anything until you create more units and give them access.

• In the original user management experience, users with access to more than one site will see a unit switcher.

Before you start: you can't disable units or undo the change once they're enabled. If your organization is large or complex, contact your Atlassian account team to help plan your structure.

Will new apps I add to a unit still appear on sites?

Yes. Adding an app to a unit doesn't change where it's hosted. Jira, Confluence, Jira Service Management and Customer Service Management each get their own URL (for example, yoursite.atlassian.net). Bitbucket and Trello aren't tied to a URL of that kind; their workspaces are hosted on the app's main address (for example, ). Either way, the app belongs to one unit, and its data stays within that unit's boundary.

Can one app belong to more than one unit?

No. Every app and connector belongs to exactly one unit. If teams in different units need the same app, each unit needs its own instance. For example, if users in two units need Jira, each unit needs its own Jira.

How do shared services, like a central IT help desk, work across units?

Units keep administration and data separate, so built-in links between apps only work within the same unit.

For example, a Jira Service Management help center in Unit A can't show knowledge base articles from a Confluence space in Unit B.

When you plan your units:

• Keep connected teams together: put teams that rely on connected tools in the same unit, such as IT support using Jira Service Management and the team maintaining its Confluence knowledge base.

• Only separate when you need to: use separate units for subsidiaries, regions or business groups that need their own administration and don't rely on shared integrations.

Licensing and billing

Can I get units on the Standard or Premium plan?

No. Units are only available on the Enterprise plan. They can't be bought separately or as an add-on. We’ll roll out units to Standard and Premium plan customers with the original user management experience due to site isolation from the original user management experience. These orgs will be able to see and manage units, but not be able to create new units. There are no impacts on your organization.

Do units change my seat count?

No. Units don't add seats or increase your seat count. They organize users, apps, data and administration within your organization. Seats are still based on app access.

Will creating more units increase my licensing costs?

No. On the Enterprise plan, you pay once for each unique active user across your organization. You can create as many units and sites as you need for your governance without paying for extra instances or paying twice for the same user.

If a user belongs to more than one unit, am I charged more?

No. Licensing is based on which apps a user can access, not how many units they belong to.

Are Marketplace apps installed for a whole unit or per site?

Per site, and they're licensed based on the users of that site. For example, if both sites in a unit need the same Marketplace app, you install it on each site. Units don't change How pricing works for multi-instance Market place apps.

How are Marketplace apps billed with units?

Units don't change how Marketplace apps are licensed. They're still billed per site. If a unit has several sites and only one uses a Marketplace app, only that site needs to install and license it.

How do units work with usage-based pricing?

You can share your organization's usage allowance by giving credits to individual users or to groups. Allocating credits to a whole unit isn't available during the beta.

Do units change how Rovo credits are calculated?

No. Your standard How Rovo credits work | Rovo | Atlassian Support still applies, whether or not units are enabled.

Admin model

What's the difference between the admin roles?

The roles differ in what they can administer:

• Organization admin: manages the whole organization, including all users, sites, apps, billing, security policies and identity settings.

• Unit admin: manages the users, apps and settings in the units they're assigned to, with no access to other units or organization-wide settings. One person can be unit admin for several units.

• Site admin: manages a single site and can't see other sites or organization settings. One person can be site admin for several sites in the units they belong to.

• User access admin: manages who can use specific apps in a unit. If your organization uses the original user management experience, this role becomes available when you enable units.

How many unit admins can a unit have?

There's no limit. We recommend giving admin permissions to as few people as possible.

Can I assign the unit admin role through SCIM groups?

No. All admin roles (organization admin, unit admin, site admin and user access admin) are assigned directly to a person. They can't be granted through membership of a group, including groups synced through SCIM.

Can unit admin actions affect the whole organization?

Yes. When a unit admin adds an app or creates a site, it counts toward your organization's limit of 150 sites. When they give users access to an app, those users take up paid seats on your organization's Enterprise plan.

管理者の機能

How does user provisioning work with units?

Your identity provider connection stays at the organization level and is managed by organization admins. With units, organization admins can also set up allocation policies to choose which users from the identity provider are synced into each unit.

How does data residency work if a unit's apps are in different regions?

Each unit has one data residency policy, which applies to all sites and supported apps in it. If your apps have different residency policies today, you'll choose one policy for the whole unit. Apps that must meet different residency requirements need to go in separate units. Not every Atlassian app supports every region. See Understand data residency.

Can I use customer-managed keys (CMK) for a unit?

CMK remains an organization scoped policy. See What is CMK encryption.

How does Atlassian Guard work with units?

Guard works at the organization level. Its policies, such as domain claims, user provisioning and managed accounts, apply across all units in your organization.

Can I copy data from one unit to another?

Yes. Admins with access to both units can use cloud-to-cloud data transfer, sandbox creation and data refresh between units. Organization admins have this access by default. You can also transfer data between units in different organizations if you have admin permissions for both units. Data transfer operates within enforced guardrails and soft limits - such as project and object copy thresholds - to ensure reliable migration performance.

Can I move a unit to another organization?

You can copy app data from a unit in one organization to a unit in another organization that already has units enabled. Use Before you start transferring Atlassian app data, and make sure you have admin permissions for both units.

Can I back up and restore a whole unit?

No. Backup and restore still work per site or app; you can't back up or restore a unit as a whole. Unit admins can start backups and restores for apps in the units they manage.

Are API rate limits split between units?

No, API limits don't change. Admin APIs are still limited per organization, and app APIs are still limited per site or workspace. All APIs are also limited per user, so one user can't use up the whole quota.

Are there APIs for managing units?

Yes. There are APIs just for units, and some existing APIs have new directory settings so you can use them for a single unit.

How many sandboxes can I create?

Enterprise customers can create 5 free sandboxes per app before buying more. See Understand billing for sandboxes. Sandboxes are kept in sandbox units, and you can create multiple sandbox units.

If a sandbox unit has several sandbox sites, does it count as one sandbox or several?

The limit counts sandboxes per app, not per site or unit. For example, if you have 5 Jira sandboxes, you can create one sandbox unit with 5 sandbox sites, each holding one Jira sandbox.