Overview

Permissions in Docs+ are built into every user interaction with the platform. This guide details how permissions work and the options available to your team.

Connected User and Application Link

The main user is the user who initially connected your bot in Slack to your Confluence instance. This user requires admin permissions in Confluence to create a connection to the APIs.

The default permissions for all API calls we make to Confluence are automatically limited to the access of this main user and further limited based on user authorization (see below).

Some of our customers create service accounts for these users.

User connections

The first time users interact with the app, they will be automatically required to connect their Slack account with their Confluence account to establish connectivity and permissions in Confluence.

When you perform your first action in Slack, you will be asked to connect your account. You can also manually trigger the connection by typing /docs-plus connect.

1. Click the Connect Now button in Slack.

2. Click Allow in Confluence.

3. Click the button to go to the home screen in Slack.

How permissions are applied

Learn how permissions can apply to specific scenarios using the following use cases.

Case 1: User space access equals the main user

In this case, the main user has access to Space FIN (Finance) in Confluence, and the connected user has access to FIN (Finance) in Confluence.

• Result: The connected user has access to FIN with the app.

Case 2: User space access less than the main user

In this case, the main user has access to Space FIN (Finance) in Confluence, and the connected user cannot access FIN (Finance) in Confluence.

• Result: The connected user cannot access FIN with the app.

Case 3: User space access more than the main user

In this case, the main user cannot access Space FIN (Finance) in Confluence, but the connected user can access FIN (Finance) in Confluence.

• Result: The connected user cannot access FIN with the app.

  • Why? The main user is the primary connection to Confluence, and the app's permissions are inherited from the main user as a starting point. Every other user's access is a subset of the main user's access.

Case 4: User can view but not update issues in space

In this case, the connected user has VIEW access to space FIN (Finance) in Confluence but does not have UPDATE access.

• Result: Connected users can view issues in FIN but cannot update issues in FIN.

  • Why? Users can never perform actions in the app that are not allowed in the Confluence settings.

Changing the main authorized user

Switching the main authorized user can cause disruptions for your team if you already use our production platform. The disruption is based on the authorizations in Confluence for your API connection and how OAuth works to connect and authorize with the APIs. If you are making this change it might be a good time to move to a service account.

The main impact for users will be requests to re-authorize their accounts.

1. Log in to Confluence using the account you would like to use as your main user.

2. Log in to your account.

3. Scroll down to the Docs+ Status section.

4. Find the Main authorized user in the section.

5. Click the Change link.

6. Click the Allow button in Confluence.