Permissions and requirements

App scopes

Scope	Purpose
search:confluence	Search Confluence pages
read:jira-work	Read Jira issues
write:jira-work	Update the Case Documentation field on behalf of the agent so Automation for Jira sees the inclusion (new in 1.5.0)
storage:app	Forge KVS storage
read:confluence-space.summary	Read space summaries
read:space:confluence	Read Confluence spaces
read:jira-user	Read the agent's name for the audit trail

Permission upgrade in 1.5.0

write:jira-work is a new scope. A site that already had the app installed must accept the permission upgrade in Apps → Manage apps. See Upgrading from an earlier version.

Agent permissions

• The agent must authorize Confluence access the first time they use the panel.
• Without authorization, the panel cannot search pages or access spaces.
• For Automation for Jira to see the documents the agent adds from the panel or a transition, the agent needs the Edit issues permission and the Case Documentation field must be on the edit screen. See the screen checklist.

Customer permissions

• The customer sees the Shared Documentation panel in the portal without needing a JSM license.
• Access to Confluence page content depends on space/page permissions.
• Customers without a JSM license are configured via unlicensedAccess: customer, unlicensed.

Confluence permissions

• The app only accesses spaces and pages the agent has permission to view.
• The scope read:confluence-content.all is not used — content is accessed only through search and direct references.