Permissions and data
Simply Dropdowns follows Confluence's own permissions and stores all of its data in your Confluence site.
Who can do what
| Action | Who |
|---|---|
| Create, edit and delete global sets | Confluence admins |
| Create, edit and delete a space's sets | Admins of that space |
| See the sets | Everyone who can view the space (or use the app, for global sets) |
| Insert and configure dropdowns | Everyone who can edit the page |
| Change a dropdown's selection on the published page | Everyone who can edit the page |
| See a dropdown's selection | Everyone who can view the page |
Where data is stored
All data stays in your Confluence site. The app runs on Atlassian's Forge platform and doesn't send data to any other service.
| Data | Stored in |
|---|---|
| A space's dropdown sets | A property of that space (simply-dropdowns-sets) |
| Global dropdown sets | A private space the app creates for itself, named Simply Dropdowns (app data) (key SIMPLYDROPDOWNS) |
| A dropdown's set, own options and selection | The macro, inside the page body |
Because selections are part of the page body, they're included in page versions and page copies, like any other page content.
Don't delete the app data space
The Simply Dropdowns (app data) space holds the global dropdown sets. Deleting it deletes them.
Permissions the app requests
| Permission | Why |
|---|---|
read:page:confluence | Read the page body to find the dropdown, and check whether you can edit the page |
write:page:confluence | Save a selection into the page body |
read:space:confluence | Read a space's dropdown sets and check whether you're a space admin |
write:space:confluence | Save a space's dropdown sets, and create the app's private space for the global sets |
read:confluence-user | Check whether you're a Confluence admin before changing global sets |