Roles and Permissions

OKR Tracker has three app roles — Admin, Manager, and Contributor — that you map to existing Jira groups in OKR Settings → Roles & Permissions. Roles decide who can create OKRs and who can change settings, while Jira's own permission scheme still governs the underlying issues.

App roles mapped to Jira groups ## The three roles

• Admin → maps to the groups that run governance: project and issue-type setup, scoring rules, quarters, reminders, and role mapping itself.
• Manager → creates and manages Objectives and Key Results, and oversees check-ins and rollups across the team.
• Contributor → records weekly check-ins and updates progress on the Key Results they own.

You assign each role to one or more Jira groups, so membership stays managed where your org already manages it.

App roles layer on top — they never bypass Jira

App roles gate OKR Tracker's own actions — creation and settings — but they sit on top of Jira's permission scheme; they never replace or bypass it. Issue create, view, and edit still flow through Jira's native dialogs and are governed by your project's permission scheme. In practice that means a person needs both the app role and the matching Jira permission to act: the role opens the OKR Tracker action, and Jira's scheme authorises the change to the issue itself.

For where OKR data is stored and the scopes that back these reads and writes, see Data Handling and Permissions.