"You must be a platform administrator to perform this action"
Why Script Master refuses an action on its admin page, and who can do it.
Symptomβ
An action in Script Master fails with You must be a platform administrator to perform this action. It can happen when you open a list, save an item or open its history.
You aren't a Jira admin or Confluence adminβ
Cause: Script Master checks on the server, for every action, that you administer the product. In Jira that's the Administer Jira global permission. In Confluence it's Confluence admin rights.
Solution: Ask a site admin to give you admin rights in the product, or to make the change for you. See Permissions.
You opened workflow rule history as a space adminβ
Cause: In a team-managed space, space admins can edit the workflow and its Script Master rules. Version history and Recent runs of those rules still need a Jira admin.
Solution: Ask a Jira admin to open the history for you. See Known limitations.
The product didn't answer the checkβ
Cause: If Jira or Confluence can't answer whether you're an admin, Script Master refuses the action to be safe.
Solution: Reload the page and try again.
Relatedβ
- Permissions: who can use each part of Script Master.
- Set who can use each tool: how to let people without admin rights use a tool.