Permissions and scopes
Scopes
The app asks for five scopes. It does not use any external network access.
| Scope | Why it is needed |
|---|---|
storage:app |
Stores environments, bookings, deployments and settings in your installation’s app storage. |
report:personal-data |
Reports the Atlassian account IDs the app stores, so closed accounts can be handled. |
read:jira-user |
Shows display names and fills user pickers. |
read:jira-work |
Reads issues and projects linked to bookings, and checks who may see them. |
write:jira-work |
Adds notification comments on linked issues, creates a Jira issue when you choose to (for example from a failed deployment), and runs the comment or transition actions an administrator configures. |
What people can do
The app checks every request on the server, not in the browser. The role of the person is worked out for each request from Jira’s own permissions and the lists an administrator keeps. People cannot approve their own bookings. Environments linked to a Jira project are visible only to people who may browse that project, and hidden environments look as if they do not exist.
Inbound CI endpoint
ProbePilot declares one Forge web trigger, used to receive deployment events from your own CI. It always answers with fixed responses, such as accepted, unauthorized or too large. It requires a per-source token sent in a header; a token in the URL query string is refused. Tokens are stored only as hashes, requests are limited to 256 KB, and repeating the same event is safe. The trigger URL is a secret: treat it like a credential, and create a new token if you think it leaked. Requests come from your own CI, never from servers we operate.