AssetPilot roles, permissions and Forge scopes

AssetPilot for Jira maps app roles to Jira groups and enforces access on the server. This page explains each role and the Forge scopes requested at installation.

Roles inside AssetPilot

Map roles to Jira groups in Settings → Access.

Roles come from Jira groups and are checked on the server.

Role	Can
Admin	Everything, including settings, asset types, the lifecycle and access. Jira admins are always AssetPilot admins.
Manager	Create, edit, import, check out, check in and delete assets.
Viewer	View assets and their history. Access can cover everyone on the Jira site or only selected groups.

Forge scopes

Scope	Why AssetPilot needs it
read:jira-work	Read an issue's summary, reporter and assignee for the Assets panel and linked-issue cards.
write:jira-work	Write one issue property (assetpilot) with linked asset ids and tags, so JQL works. No other issue data is changed.
read:jira-user	Search users when assigning an asset and read the current user's groups to determine their role.
storage:app	Store AssetPilot data in Forge storage.

AssetPilot declares no external hosts. It calls only the Jira REST API of the Jira site where it is installed.

Calls run as the signed-in user. The daily digest is the only job that runs as the app.

See Data and privacy for storage and deletion details.