docs: Document Atlassian OAuth permissions and service account requirements#319
Merged
prithvi2206 merged 1 commit intomainfrom Mar 24, 2026
Merged
Conversation
…ntegration docs Adds a new "Permissions Required" section documenting: - Specific OAuth scopes requested for Jira (read:jira-work, write:jira-work, read:jira-user) - Specific OAuth scopes requested for Confluence (read:confluence-space.summary, read:confluence-content.all, plus granular scopes) - offline_access scope for token refresh - Service account permission requirements (User role for Jira, Can view for Confluence) This addresses a customer question about the minimum permissions needed to set up a dedicated service account for the Atlassian integration. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
![promptless[bot]](https://avatars.githubusercontent.com/in/979718?s=60&v=4){kind=small}
|
|
||
| ## Permissions Required | ||
|
|
||
| The OAuth consent screen displays the permissions Promptless requests when you connect Atlassian. Promptless requests only the scopes needed to read Jira issues and Confluence pages for documentation context. |
Contributor
Author
There was a problem hiding this comment.
OAuth scopes defined in IntegrationsList.tsx - includes classic scopes (read:jira-work, write:jira-work, read:jira-user) and Confluence scopes (read:confluence-space.summary, read:confluence-content.all, plus granular scopes for API v2 compatibility)
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Open this suggestion in Promptless to view citations and reasoning process
Adds a new "Permissions Required" section to the Atlassian Integration page, documenting the specific OAuth scopes requested and service account permission requirements.
What's new:
read:jira-work,write:jira-work, andread:jira-userscopes with their purposesread:confluence-space.summary,read:confluence-content.all) and granular scopes for API v2 compatibilityoffline_accessfor token refreshWhy this matters:
A customer (Alation) asked for a connection spec with minimal permissions to create a service account for the integration. The existing docs mentioned service accounts but didn't provide specific OAuth scope or permission requirements. This update gives enterprise customers concrete, actionable information for setting up dedicated service accounts with least-privilege access.
Related trigger: Slack thread in #dogfood - Alation questions about Atlassian integration permissions