DATE:
AUTHOR:
The Jira team
Admin Reporting

Maintain central guardrails while empowering teams to build with Space Policies

DATE:
AUTHOR: The Jira team

Enterprise Jira admins have long faced a difficult choice: keep team-managed space creation open and risk configuration sprawl, duplicate fields, and inconsistent statuses – or lock it down and become the approval bottleneck for every new space and routine field request.

When governance requires manual gatekeeping, everyone slows down. Teams wait in backlog queues just to kick off work, while admins spend valuable hours triaging configuration tickets and cleaning up fragmented data instead of driving high-impact initiatives.

Space Policies eliminate this tradeoff. It allows Jira admins to establish centralized configuration guardrails – standardizing global fields and statuses – across team-managed spaces. Admins protect cross-organization data integrity and streamline reporting, while teams retain the agility and autonomy to spin up and customize their own spaces instantly within trusted boundaries.

How it works

Choose from ready-to-use governance guardrails. Define boundaries once and let teams self-serve inside approved standards. Space Policies offers three out-of-the-box configuration options tailored to your governance needs:

  • Global fields only: Teams can leverage existing global fields, but cannot create space-specific custom fields that cause sprawl.

  • Global statuses only: Teams use standardized global workflow statuses, ensuring consistent cross-team lifecycle tracking without creating custom status variations.

  • Global fields and statuses: Enforces both shared fields and standardized statuses for comprehensive alignment across spaces.

(Note: A team-managed space can have one policy applied at a time.)

Automate governance with site-wide default policies. Set governance on autopilot. Admins can designate one Space Policy as the default for all new team-managed spaces across their Jira site. Newly created spaces automatically inherit the default guardrails at creation – eliminating the need for admins to manually configure or assign policies to every new space.

Inherit policies seamlessly through custom templates. Scale best practices across departments with custom templates. By attaching a Space Policy to the space that backs a custom template, every new team-managed space created from that template automatically inherits the right guardrails. If a template doesn’t have a specific policy assigned, it seamlessly falls back to your site-wide default policy. End users get compliant spaces on day one without any extra configuration steps.

Safeguard cross-organization reporting and eliminate ticket backlogs. By keeping critical fields and statuses consistent across team-managed spaces, Space Policies ensures leadership dashboards, portfolio rollups, and compliance reports remain clean and reliable. Teams kick off spaces immediately without opening an admin ticket, while admins reclaim hours previously spent maintaining custom setups.

Get started

FAQs

Question

Answer

Who can configure and manage Space Policies?

Jira site and organization administrators can create, edit, and assign Space Policies via Jira admin settings.

How many policies can a single space have?

A team-managed space can have one policy assigned to it at a time.

Do newly created team-managed spaces require manual policy assignment?

No. Admins can set a site-wide default Space Policy so every newly created team-managed space automatically receives guardrails at creation.

How do Space Policies work with custom templates?

You can link a policy directly to the space backing a custom template. Any space created from that template automatically inherits the policy.

Can end users in team-managed spaces still customize their workflows?

Yes. Within the established policy guardrails (e.g., using global fields or statuses), teams retain full autonomy over their views, board columns, work item layouts, and team settings.

What policy options are available out of the box?

You can choose between Global fields only, Global statuses only, or Global fields and statuses.

Powered by LaunchNotes