[DC] Manage application access

Permissions in OKR for Jira Data Center allow you to control which users or teams can perform specific actions within the app. By default, all users have full access to all functionalities, but it’s simple to tailor the permissions to suit your organization’s needs.

Basic permissions

Basic permissions are ideal for companies where most users should have full access, but certain tasks, like configuration or editing, need to be restricted to select users or teams.

Open

Full access

This is the default state of the permissions. When applied, everyone can perform all actions in the app. No restrictions are applied.

Global settings control

Restricts access to app configuration settings. Only selected users or groups can modify global app settings. This is useful when a specific team or individual is responsible for overseeing the OKR setup and administration.

Editing control

This restricts the ability to create or edit OKRs. Users can still view OKRs and access global settings, but they cannot modify or create OKRs unless explicitly granted permission.

Global settings & editing control

This combination of permission types allows users not added to either the Global settings control or Editing control lists to become viewers. They can only view OKRs and have no permissions to create, edit, or configure settings.

Advanced setup

This option gives you fine-grained control over permissions. It allows you to:

• Define custom user or group roles.

• Assign permissions based on global roles or OKR ownership.

• Maintain tight control while aligning with your team’s OKR process.

Global roles

Global roles determine what users can do across all OKRs. Two roles are available by default:

• Admin: Full access to all OKR features and settings

• Viewer: View-only access to OKRs

By default, the Admin role is applied to all users. You can change this default and also create custom global roles.

Once created, custom roles appear in the Permissions section. You can then assign specific permissions to each role, such as the ability to delete OKRs or manage collaborators.

Open

OKR ownership-based roles

Ownership-based roles provide more contextual permissions by focusing on OKRs that users are actively involved in.

Open

For example, with a Viewer role assigned as a default role and OKR ownership-based roles on, only people actively engaged (assigned in any way) in the OKR would have some extra permissions regarding it. Others would be just able to view the OKRs.

You can:

• Enable or disable specific ownership-based roles.

• Choose which permissions each role should have.

• Use these roles in combination with global roles for maximum flexibility.

Open