Skip to content
Administration

Unit-aware backup and restore

Backup and Restore now works with units, so organization and unit admins handle backups and restores inside their own unit. It has been rolling out to Atlassian Cloud sites since 21 Oct 2026.

  • Rolling out since 21 Oct 2026
  • Medium impact

What it is

Improvement

Backup and Restore now recognizes units. Organization admins and unit admins can run backups and restores for the apps in their own unit. Restore destinations are checked for eligibility, and Assets are handled before data is restored.

Plans Premium and Enterprise

Admins

Organization admins and unit admins can see and manage backup policies and restore actions that fall inside their own unit.

Written from Atlassian's release note and checked against it automatically. Atlassian's original stays the source of truth.

Before it lands

  1. Decide which organization, unit and app admins should be able to manage backups and restores in each unit.
  2. Check that restore destinations hold no existing customer data in the apps being restored or in Assets.
  3. Verify that the source unit and the destination unit share the same data residency region.
  4. Plan the support-assisted opt-in path if a Premium restore includes Assets.

Where the rollout is

  1. First published Done
  2. Rollout starts Done

What changed

  1. First published by Atlassian

Atlas Bench began tracking Atlassian Cloud on 29 Oct 2026. Changes before that date are not in this history.

Find out who can reach what.

Fixed scope. The assessment starts at the identity layer: human and non-human access, the accounts nobody owns, and what has to be true before an agent gets one. You get the findings, the ownership gaps, and the order to close them in.