Prepare to set up units in your organization
This feature is currently in beta and is gradually rolling out. It may not be available to all organization admins at this time.
Setting up units is a foundational change that transforms how your organization manages data, users, Search and Rovo experiences. Before you begin, make sure your stakeholders and technical dependencies are ready. See Structure your organization using units.
Checklist for unit set up
Before setting up units,
Identify the unit admins who will manage users, groups, and apps within the unit. Understand the role of unit admin.
Review existing users and groups that exist within unit boundaries. When units are enabled, you may want to clean up or remove users and groups from units, whose membership in this units no longer makes sense.
Review any application links or integrations that require data to flow between sites. If connected sites are placed in different units, the integration may require additional configuration.
If you are in the original user management experience, there is a 2 step process to enabling units. The first step is to enable units for admins in Atlassian Administration, followed by a second step to enable units for end users. This gives admins a period to understand current unit boundaries within their organization, and take further steps to change these boundaries, such as merging two units together, before enabling unit boundaries for end user experiences.
How units work with Rovo and Teamwork Graph
Units define the data boundary for Rovo and the Teamwork Graph:
Rovo will work across up to five sites within a single unit. Rovo Search, Rovo Chat, and Rovo agents will access data only from sites within the same unit, and according to the individual permissions of the user using these experiences
When users invoke Rovo (
/rovo), they can only discover and interact with data within their unit that they have access to.The Teamwork Graph context will be limited to, and populated by data within the unit boundary.
If you are in the original user management experience and enable units, Rovo is limited to one site per unit until units are merged. See see Merge Units.
How admin and user experience change with units
Enabling units introduces a new layer to your Atlassian organization setup, with units sitting between your organization and sites. Organization admins can access the Units page from the side navigation to view and manage units. Set up units in Atlassian Administration.
For organization admins managing units, refer to How units impact organization administration for which admin experiences reference unit boundaries
For supported apps, units change the scope of discovery and collaboration experiences. Link previews, site pickers, cross-app connections, automations, and notifications will show content from sites within the user's unit. Users in multiple units can switch between them using the unit switcher. Manage user access to units.
Which apps are scoped to a unit boundary
Unit boundary applies? | Apps | Boundary behaviour |
|---|---|---|
Yes |
| Users can only find, link to, and interact with content from sites in the same unit. Existing links across units keep working. |
No |
| These apps work the same way they did before you set up units. Some can connect to content across units. For example, one Bitbucket workspace can connect to Jira sites in two different units. Others stay limited to a single site. |
What happens to apps connected across units
Enabling units changes how data flows between your apps.
Admins should audit and review existing cross-unit connections, such as Application links or shared Teamwork Graph content using the Connections tab available on the unit details page.
Existing connections created before enabling units will continue to work. Org admins who have permissions across all units in an organization can create cross unit connections such as app links.
Post-enablement checklist
After a unit is enabled,
Test Rovo to ensure it is returning results from the intended sites within the unit.
Confirm that users can mention each other within the unit boundary.
Ensure that the new unit admins have the correct permissions in Atlassian Administration.
Was this helpful?