AssetPilot Connect permissions and external hosts
AssetPilot Connect uses Forge scopes for storage and admin checks, plus external hosts for configured connections to AssetPilot for Jira and other services. Only Jira admins can open Connect's settings.
Pre-release
AssetPilot Connect is not on Atlassian Marketplace yet. It requires AssetPilot's app REST API, which is not in production. This page describes the release candidate.
Forge scopes and external hosts
| Permission | Why Connect needs it |
|---|---|
storage:app | Store settings, run and delivery logs, API key hashes and secrets in Forge storage |
read:jira-user | Show who connected the app and who created each API key |
read:jira-work | Check that the person changing settings is a Jira admin |
| External hosts | Atlassian sign-in and API hosts, the MDM, Slack and Teams hosts on the MDM and notifications pages, and the webhook URLs you add |
Admin checks
The server checks that the caller is a Jira admin for every settings change.
See Data and privacy for storage and external data flows.