Roles & access

Two roles, both answered by Jira

Concessa keeps no list of members. It asks Jira two questions at the moment they matter, and caches neither answer.

Project administrator

Anyone holding Administer projects on the Jira project. They configure the app, define freeze windows and are the only people who can override one. Overriding a freeze is the deliberate setting-aside of a control the project agreed to, so it must be attributable to somebody who owns the project.

Agent

Anyone in any of the Jira project roles the administrator bound — directly, or through a group in one of them. An administrator can bind more than one, for sites where change managers and release managers are separate roles in Jira; access is the sum of them. Agents record changes, request approvals and answer the ones addressed to them.

Every administrator is also an agent. An administrator who could configure the app but not use it would be an odd thing to ship, and it removes the trap where the first person to open the app in a new project cannot get in.

What each role can do

One row is No for everybody, and it is there on purpose: no person of any role can take a change out of Approved. The system does it, in one case, when a change’s planned dates move outside the window it was approved for — see The governance lifecycle.

Action	Project admin	Agent	Everyone else
Record and edit a change	Yes	Yes	No
Request an approval	Yes	Yes	No
Answer an approval addressed to them	Yes	Yes	No
Move a change through its lifecycle	Yes	Yes	No
Take a change out of Approved	No	No	No
See the CAB workbench, calendar and evidence	Yes	Yes	No
Take an evidence export	Yes	Yes	No
Bind or clear the agent role	Yes	No	No
Create and remove freeze windows	Yes	No	No
Override a freeze window	Yes	No	No

“Everyone else” sees an explanation naming the role, or roles, they would need to be added to — not an error, and not a blank panel.

Granting access

A project administrator opens Project settings → Concessa, picks one or more project roles and saves them. Saving again replaces the whole list, which is also how a role comes back off it. Membership stays in Jira’s own People screen, where it already lives.

The Concessa project settings page, showing the bound agent roles with a count of named users and groups, a role selector, freeze windows in a table, and a licensing note. — Binding the agent roles. The count tells you the consequence of the roles you picked.

Licensing is separate, and simpler

Atlassian charges for Concessa per agent, at the site level, through the Marketplace. The app itself contains no plan, tier, entitlement, trial state or feature flag — there is nothing to withhold from somebody who is licensed and in the role.

That means the two questions are genuinely independent: Atlassian decides whether your site is licensed, and your project administrator decides who inside the project can use it.

Put change governance where the work already happens

Concessa is a pure Forge app, charged per agent. No external systems, no data leaving your site, nothing to host. Access starts with a conversation.

Request access Read the setup guide