App scope and permissions
- Robert Alexander Marshall
Global scope and permissions
Each app for Confluence Cloud (like Comala Document Control) has to be configured with a specific scope.
Scopes allow an app to request a particular level of access to an Atlassian product.
This configuration is done automatically when the app is installed and adds the Comala Document Control app user as an individual user in the Global permissions screen
The automatic configuration also adds the Comala Document Control app user as an individual user for each space in the Space permissions screen.
The app user is assigned all individual user permissions for the space except Restrictions Add/Delete, Delete own, Archive, Space Export.
Within an instance, a global administrator can decide to further limit an app's actions. This is valuable because it allows administrators to safely install apps that they otherwise might not.
Changes in
scope by a global administrator may affect the global permissions for the app user and the functioning of the app in the instance
individual space permissions for the app user (due to either the global change or a space administrator change) may affect the functioning of the app in that space
Page restrictions added to content prior to the addition and application of the Document Control app workflow to the content may cause an error.
See Troubleshooting.
Page- level restrictions
Page-level restrictions can affect the successful application of the workflow. If the page-level restrictions do not include the Comala Document Control app add-on user, page activity is not processed by the workflow, for example, if the page is updated or a page is created with restrictions.
When this occurs, a message is displayed when the app attempts to initialize the state byline on the page. To resolve this, ensure the Comala Document Control app add-on user (or, in some cases, the current user) is added to the space permissions and any page restrictions, then refresh the page.