Deactivate user across Atlassian products
Automatically deactivate a departing user across Atlassian products from a Slack request with Stepwork, ending Jira and Confluence access in one run.
- Use case
- Employee offboardingIT
- Best for
- IT Administrator, Helpdesk Technician
- Applications used
Atlassian Administration
Slack
- Business outcome
- Risk reduction
The problem
One product closes. The other seat stays open.
IT often deactivates Atlassian accounts by hand and misses a product. Jira is closed while Confluence still works, or the other way around.
Seats keep billing and access keeps lingering. Offboarding looks done in the ticket while one product is still live.
The outcome
Jira and Confluence access end together
Stepwork signs in to Atlassian admin, finds the user, and revokes site access across Jira and Confluence so both seats free. The run records who asked. For a new hire who needs both products, use Create user with product access in Atlassian.
- The user is found in Atlassian admin.
- Site access is revoked across Jira and Confluence.
- If the user cannot be found, the run stops.
The process
From Slack request to Atlassian access revoked
IT posts the departing user’s email in Slack. Stepwork revokes site access across products.
- Step 1
Request it in Slack
A teammate posts the departing employee’s work email. That message starts the flow, and Stepwork records who asked and when.
- Step 2
Find the user
Stepwork signs in to Atlassian admin and locates the user. If nobody matches, the run stops.
- Step 3
Revoke product access
Stepwork revokes site access across Jira and Confluence, freeing both seats in one pass.
- Step 4
Confirm and reply in Slack
Stepwork checks that access is revoked, then posts the result back in Slack.
Why Stepwork
Atlassian offboarding stays on the path you recorded
A deterministic agent runs the revoke path you recorded. One product does not stay open while the ticket says the person is gone.
Similar use cases
Similar use cases
Deactivate user account in OktaSigns into the Okta admin console, locates the user by email, deactivates the account, and confirms the status change ended all SSO sessions.
FAQ