How does user attribution work? Will actions reflect the correct user?
Updated
by Dallas de Marr
Correct user attribution is a critical component of keeping your issues organized. With Docs+ all updates in Confluence are from the user who performed the action - not a "bot" user.
What to know
- All updates will have correct user attribution in Confluence
- Users connect their Slack and Confluence accounts to make updates to Confluence
- Users Confluence permissions are automatically respected by Docs+
How does it work?
- A user mentions a Confluence issue in a channel where the bot is invited.
- The bot responds with issue information
- The user chooses the comment action to add a comment.
- The comment is added to Confluence as the user who added the comment in Slack.
What is happening in the technology?
We use OAuth to communicate with the Atlassian APIs and users are required to authenticate with Confluence to allow our systems to make updates in Confluence on their behalf. This process is known as API impersonation.
The result is that 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 / etc) does not effect the tracking in Confluence.
User connections
The first time users interact with the app they will be automatically be required to connect their Slack account with their Confluence account to establish connectivity and permissions in Confluence.
What to know
- Your password is never shared with our systems
- Every action you take in Slack (create, comment, etc) will be attributed to your account in Confluence.
- Your permissions are based on your Confluence access.
You will be asked to connect your account when you perform you first action in Slack. You can also manually trigger 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.
