How user attribution works: Will actions reflect the correct user?
Overview
Correct user attribution is a critical component of keeping issues organized. With Docs+, all updates in Confluence are from the user who performed the action—not a bot user.
All updates will have correct user attribution in Confluence.
Users connect their Slack and Confluence accounts to make updates to Confluence.
Docs+ automatically respects users' Confluence permissions.
How it works
A user mentions a Confluence issue in a channel where the user invites the bot.
The bot responds with issue information.
The user chooses the comment action to add a comment.
The comment was added to Confluence by the user who added the comment to Slack.
What happens in the technology
We use OAuth to communicate with the Atlassian APIs, and users must authenticate with Confluence to allow our systems to make updates on their behalf. This process is known as API impersonation.
All updates made from Docs+ are reflected in Confluence as the user who performed the action. This ensures the source of the update (Slack / Confluence / Email) does not affect the tracking in Confluence.
User connections
Once users first interact with the app, they are required to connect their Slack account with their Confluence account to establish connectivity and permissions in Confluence.
Your password is never shared with our systems.
Every action in Slack (create, comment) will be attributed to your Confluence account.
Your permissions are based on your Confluence access.
You will be asked to connect your account when you perform your first action in Slack. You can also manually trigger the connection by typing /docs-plus connect.
Click the Connect Now button in Slack.
Click Allow in Confluence.
Click the button to go to the home screen in Slack.