Collaboration

Atlassian (Jira & Confluence)

Manage Jira issues and Confluence pages in plain language, using the admin's own Atlassian account.

Dex connects to Atlassian Cloud via OAuth 2.0 delegated tokens — every action runs as the authorizing admin, so all changes respect that user's existing Jira and Confluence permissions and show up in the native audit trail. Admins and employees can search, create, transition, and comment on Jira issues, and list, create, and update Confluence pages, all from a Dex chat.

Book a Demo

What Dex does with Atlassian (Jira & Confluence)

Dex handles both admin workflows and employee self-service — all policy-guardrailed and audit-logged.

For admins (CoAdmin)

Search Jira issues with JQL across any project the authorizing admin can see
Create Jira issues — pick project, issue type, summary, description, assignee, priority, labels
Update issues: edit fields, change priority, add labels, reassign
Transition issues through any workflow (To Do → In Progress → Done, or custom states)
Add comments to issues using Atlassian Document Format (rich text, mentions)
List projects, boards, users, and custom fields across the Atlassian site
List Confluence spaces, search content with CQL, and get page content in storage format
Create and update Confluence pages (handles version number automatically on edits)

For employees (self-service)

Search your own Jira tickets and get status updates in chat
Create a Jira issue in your team's project in a single message
Transition a ticket you own ("mark PROJ-123 as done")
Add a comment to a ticket without opening Jira
Pull up a Confluence page by title and have Dex summarize it

Just ask Dex

Your team types a request in plain language. Dex investigates, plans, and executes — with the right guardrails.

Admin prompts

>Create a Jira Task in project IT titled "Rotate VPN certs" due next Friday, assigned to me
>Search all unresolved Bugs in DEX updated in the last 7 days
>Transition JIRA-482 to "In Review" and add comment "ready for QA"
>List every Confluence space in the Engineering org
>Create a Confluence page in the "Onboarding" space titled "New hire checklist — April 2026" with this content: ...
>Show all Jira issues assigned to alice@acme.com that are older than 30 days

Employee prompts

>What Jira tickets do I have open this sprint?
>Create a bug in PROJ: "Dashboard shows stale data after refresh"
>Mark PROJ-1207 as In Progress
>Add a comment to PROJ-1198 saying I'll pick it up tomorrow
>Find the Confluence page about the password rotation policy

Policy actions

Every action Dex can take on Atlassian (Jira & Confluence) is declared, scoped, and guardrailed. Admins control which apply, who approves them, and whether they're limited to self-service.

Action	What it does	Guardrails
`atlassian_jira_search`	Search Jira issues with JQL	—
`atlassian_jira_create_issue`	Create Jira issues	approval
`atlassian_jira_update_issue`	Update Jira issue fields (summary, description, priority, labels, assignee)	approval
`atlassian_jira_transition_issue`	Move a Jira issue through its workflow (e.g. To Do → Done)	—
`atlassian_jira_add_comment`	Add a comment to a Jira issue	—
`atlassian_confluence_search`	Search Confluence content with CQL and list spaces	—
`atlassian_confluence_read_page`	Read Confluence page content	—
`atlassian_confluence_manage_page`	Create and update Confluence pages	approval

How to configure Atlassian (Jira & Confluence)

Onboarding takes minutes. Dex validates your credentials before saving them.

Setup steps

1
SysAid pre-configures a global Atlassian OAuth app — no per-tenant client ID/secret needed. The client ID and secret live in Dex server environment variables.
2
In Dex, the admin enables the Atlassian integration from the app catalog.
3
Dex opens the Atlassian consent screen — the admin signs in with their Atlassian account and approves the requested scopes (Jira read/write, Confluence read/write, offline_access).
4
After approval, Dex calls /oauth/token/accessible-resources to discover the admin's Atlassian sites and stores the cloud ID + refresh token.
5
Refresh tokens are rotated automatically; the admin only re-consents if SysAid adds new scopes or the token is revoked.
6
Additional admins/users can authorize with their own Atlassian account to run actions in their own permission scope.

Vendor documentation ↗

No extra credentials

This integration is covered by your Microsoft 365 tenant authorization to Dex. There are no per-app credentials to create or rotate.

Requirements

•Atlassian Cloud account (Atlassian Data Center / on-prem Jira not supported)
•Admin must have a user account in the Atlassian site with the scopes Dex requests (read:jira-work, write:jira-work, read:jira-user, read:confluence-content.all, write:confluence-content, read:confluence-space.summary, offline_access)
•All Dex-initiated changes are attributed to the authorizing admin in the Atlassian audit log
•Confluence API uses v2 endpoints (/wiki/api/v2/) — older v1-only Confluence features are not supported
•Rate limits: Atlassian enforces ~10 req/sec per user token with burst budget; Dex backs off on 429s

Related integrations

See Dex run Atlassian (Jira & Confluence)

Book a 30-minute walkthrough with our team and see how autonomous IT works in your environment — or get started for free.

Book a Demo Browse all integrations →