The environment public sector requirements actually permit.
Atlassian's government environment serves public sector organizations and their suppliers, where the compliance regime constrains which environment is permissible at all. Our work is identity, change control, and migration into a compliance-constrained environment.
Atlassian's government offering exists for organizations whose compliance regime rules out the standard cloud. The identity and change work on top is unchanged.
What it is
Atlassian's government environment serves public sector organizations and their suppliers, where the compliance regime constrains which environment is permissible at all.
The platform differs. The work on top does not: identity has to be designed, change control has to mean something, and the migration into it has to decide what carries forward.
What it does
A compliance-constrained environment
Which is the requirement, and the reason the decision is rarely optional.
Where it fits
L2, platform and migration. It changes where the estate runs rather than how it is governed, which means every layer above still needs the same design. Compliance constrains the environment; it does not produce a permission model.
What we do with it
Migration into it
Deciding what carries forward and what is retired, with the identity workstream in scope.
Identity and evidence
The permission model and the access reviews a compliance regime will ask to see.
Change control that produces evidence
Approval records that survive an audit rather than describing intent.
Where it earns its place
A public sector organization moving off self-managed
The environment is prescribed. The permission model still has to be designed.
A supplier inheriting a compliance requirement
Meeting the standard is a platform decision and a governance one, and only the first is bought.