Introduction

Confluence typically houses key documentation and evidence that is pulled in manually for every audit. That's where the Complyance Confluence integration comes in.

The integration can automatically renew evidence by pulling the latest document from Confluence. This happens automatically and ahead of evidence expiry.

Please note: this integration is only for Confluence. For the Jira instructions, please go to this guide.

Configuration

Step 1: Create a new user

Create a new user for Complyance in your Atlassian environment, so you can clearly manage permissions.

Step 2: API token generation

Once created, log in with the newly created integration user. To generate an API token:

• Click on the user avatar in the top-right corner
• Click on Manage account
• In the navigation menu, click on Security.
• Scroll down to the API tokens section and click the Create and manage API tokens link.
• Click the Create Classic API token button.
• Give your token a name that helps you identify its purpose. For example, you can name it after our platform.
• Change the ‘Expires on’ date to one year in the future.
• Click Create.
• A new API token will be generated. Make sure to copy it immediately as you won't be able to see it again.
• Important: Treat your API token like a password. Keep it secure and do not share it openly.
•  

Step 3: Securely share information with Complyance

Securely provide the 3 pieces of information below to the Complyance team via our shared 1Password vault

• • API base URL - ex: https://complyance.atlassian.net
  • Client email - email of the user created in Step 2
  • API token - token created in Step 2

Your integration is now connected and ready to be set up!