Permissions
Script Master is an admin tool: only Jira admins and Confluence admins can open its admin page and change scripts. This page lists what everyone else can reach, and whose permissions each kind of script uses when it runs.
Script Master adds no roles of its own. The one setting that gives people without admin rights access to something is the access level of each tool in Tools.
The admin pageβ
| Product | Who can open it and change items | How it's checked |
|---|---|---|
| Jira | Jira admins: people with the Administer Jira global permission | Script Master asks Jira for the caller's own permissions |
| Confluence | Confluence admins | Script Master asks Confluence whether the caller administers the site |
Jira and Confluence show the admin page to admins only. On top of that, Script Master checks again on the server for every action that reads or changes items. If the check fails, or the product can't answer, the action is refused with You must be a platform administrator to perform this action.
What people without admin rights can reachβ
| Part of the app | Who sees or uses it | Whose permissions the script uses |
|---|---|---|
| Fragments | Everyone who can see the work item, page or space where the fragment is shown. If you limited the fragment to some spaces, only there | The viewer's, in their browser |
| Gadgets (Jira) | Dashboard editors add the Custom Gadgets gadget and pick a gadget. Everyone who can see the dashboard sees it | The viewer's, in their browser |
| Macros (Confluence) | Page editors insert the Custom Macro macro and pick a macro. Everyone who can see the page sees it | The viewer's, in their browser |
| UI Modifications (Jira) | Everyone who fills in a form the UI modification applies to, including customers on a Jira Service Management portal | Runs in the person's browser |
| Script Master Tools | People the tool's access level allows: All users, Restricted to groups or Disabled | The person running the tool's |
| Web Triggers | Anyone who has the web trigger's URL | The app's, through the Companion App |
| Scheduled Jobs | Nobody: they run on their schedule | The app's, through the Companion App |
| Custom Fields (Jira) | Everyone who can see the work item sees the field's value | The app's, through the Companion App |
| Workflow post functions (Jira) | Everyone who runs the transition | The app's, through the Companion App |
| Validators and conditions (Jira) | Everyone who runs the transition | Jira evaluates the expression |
The gadget and macro pickers list only items that are turned on. A macro that's turned off shows Macro disabled on the page.
Toolsβ
Tool access decides which tools a person finds on the Script Master Tools page. It isn't a security boundary: every tool runs as the person using it, so their Jira or Confluence permissions decide what they can change. See Set who can use each tool.
Workflow rulesβ
Anyone who can edit a workflow can add, change and remove Script Master's post functions, validators and conditions on it, including space admins of team-managed spaces. Version history and Recent runs for those rules need a Jira admin. See Known limitations.
Things to knowβ
- The code of fragments, gadgets and macros reaches every viewer's browser. It has to, because it runs there. Never put tokens, passwords or other secrets in them.
- Web trigger URLs have no sign-in. Anyone with the URL can call it. Check a secret or the caller inside the script. See Web Triggers.
- Server-side scripts run as the app, not as a person. A web trigger, scheduled job, scripted field or post function can reach everything the Companion App's permissions allow, whoever caused it to run.
- The live preview runs as you. When you preview a fragment, gadget or macro "as" someone else, only the context is theirs. Data requests still use your permissions.
Licenseβ
Creating items and running scripts from the admin page also needs an active license. See Licensing.
Relatedβ
- Data security and privacy: the scopes the app asks Atlassian for.
- The Companion App: where server-side scripts run, and with which permissions.
- "You must be a platform administrator to perform this action": what to do when the admin check refuses you.