Matify/Config Undo for Jira

Permissions and security

The six permissions (scopes), in plain words

ScopeWhat Config Undo uses it forRead / write
read:jira-workRead permission schemes; check that the person using the app holds Administer Jiraread
manage:jira-configurationRead the audit log, workflow history, workflows, workflow and notification schemes, custom field contexts and options, field schemes. Write schemes, workflows and options only for an approved restoreread + write
manage:jira-projectWrite project settings (details, scheme associations, role actors, components, versions) and screens only for an approved restorewrite
read:jira-userShow people's names in the app when you view a page, and the author filter; show group names in diffs. People's names are never storedread
storage:appStore versions, the journal, restore points, requests and the ledger in Forge hosted storage on your siteapp storage
report:personal-dataReport stored account ids to Atlassian weekly so closed accounts are erased—

There is no narrower classic scope that lets an app read the audit log, workflows, notification schemes or field contexts, and Jira has no granular scope for notification-scheme writes. Config Undo doesn't ask for issue writes (write:jira-work), webhooks, Confluence or any external access.

What the app user can do — stated plainly

Because of manage:jira-configuration and manage:jira-project, Jira gives the Config Undo app user Jira-admin-equivalent permissions. In our capability test it held Administer Jira, Administer projects and Bulk change. Jira's global permission settings can't narrow this.

Config Undo itself writes to your Jira configuration only when all of these hold:

The guided safe test is the only case with fewer conditions: on your request it creates a permission scheme named "Config Undo test …" that no project uses, restores it after you changed it, and deletes it again. Its restore doesn't need restore to be enabled for permission schemes or a second approver. That exception applies only to the test scheme the current test created, which the server checks before every step, and the test refuses to restore the scheme if it has been added to a project. The kill switch and the licence apply to the guided test like to every other write.

Config Undo never deletes your schemes, workflows, screens, fields or projects. In restores it disables options and archives versions instead of deleting them, and lists components for manual removal.

Who can use the app

Only users with the Administer Jira global permission. Every request from the app's pages is checked on the server: the app asks Jira whether the calling user holds Administer Jira (cached for at most five minutes) before it returns any data or does anything. Menu visibility is only a convenience, never the security boundary.

Restore-specific rules, all enforced on the server:

Four-eyes approval protects against mistakes. It is not a control against a malicious administrator: any Jira admin can switch to single-admin mode or delete all app data. Both need an explicit confirmation and are recorded in the ledger (Delete all app data removes the ledger too, so export it first if you need it as evidence).

How restores appear in Jira's audit log

How the restore runsJira's audit log showsConfig Undo records
Directly in the approval request (most single-object restores; estimated up to about 18 seconds)the approving admin — the write is made with that admin's own permissionsledger + journal entry "restored by Config Undo"
In the background (longer restores)the Config Undo appledger with the approver; before the first write the app re-checks through Jira's permissions API that the approver still holds Administer Jira
Started directly, finished in the background (the restore took longer than estimated, or Jira asked the app to slow down)the approving admin for the first steps, the Config Undo app for the restledger entry "Continued in the background as the app" with the number of remaining steps

The preview tells you in advance when a restore is estimated to run in the background. The guided safe test creates and deletes its test scheme as the app.

Reads of your configuration (recording, previews, compare with live) are made as the app.

Platform and architecture

Application security

No compliance certification (such as SOC 2 or ISO 27001) is claimed for Config Undo or Matify.

Reporting a security issue

Email support@matifyapps.de with "security" in the subject, or use the login-free form with the type "Security vulnerability". Please don't open a public issue. Matify follows Atlassian's Security Bug Fix Policy for Marketplace apps; see the Matify SLA.

More detail: Data security and privacy statement.