What the app reads, and what it does not
Scopes
| Scope | Why |
|---|---|
read:cmdb-object:jira, read:cmdb-schema:jira, read:cmdb-type:jira, read:cmdb-attribute:jira | Read the schemas, object types, attributes and objects in your scope. |
read:servicedesk-request | Only to read the Assets workspace id. The app does not read requests. |
read:jira-user, read:user:jira | Whether an account is active (rules AS2, AS3), display names on screen, and whether the person opening the admin page is a Jira administrator. |
storage:app | The app's own storage inside your Atlassian site. |
There are no write scopes and no external connections.
What is stored
- Account identifiers, Assets object identifiers and keys, schema and type identifiers.
- A SHA-256 hash of each asset's name — not the name.
- Decisions, reasons written by owners and administrators, dates, and the hash chain.
Limits
- The app sees what Assets returns for the configured scope and owner field. Assets outside the scope, or owners kept in another field, are not covered.
- It records decisions; it does not inspect devices or confirm data wiping.
- Access rights in Jira are a different subject: see Vouchline for Jira access reviews.