Engineering · SCIM pricing
Atlassian SCIM pricing
Issue tracking and team wiki suite including Jira and Confluence. SCIM costs extra.
SCIM pricing for every app →What Okta covers for Atlassian, and what StitchOps adds.
Okta signs users in and manages accounts where the app supports it in the Okta Integration Network. StitchOps covers the rest of the Atlassian account lifecycle.
In the OIN with SWA password fill only. No SAML, OIDC or provisioning.
StitchOps covers 6 of 8 capabilities for Atlassian.
| Capability | Okta, from the OIN | StitchOps |
|---|---|---|
| Single sign on | Password fill only (SWA). No SAML or OIDC. | Enterprise password management signs users in to Atlassian with vaulted credentials. Users never need the password. |
| Shared accounts and MFA | Not part of the OIN listing. | Shares Atlassian logins and their MFA across a team, with credentials kept in your vault. |
| Joiners | Creates accounts through the OIN connector. | Not needed. |
| Movers | Updates accounts through the OIN connector. | Not needed. |
| Leavers | No deprovisioning in the OIN. | Removes Atlassian access the day someone leaves, anywhere a person can log in and act, and saves evidence of the removal. |
| Password rotation | Pushes the Okta password to the app. No rotation of shared logins. | Changes the Atlassian password on a schedule and the day someone leaves, and updates your vault in the same run. |
| Access reviews | No connector to read or remove Atlassian accounts. | Pulls the Atlassian user list on a schedule, compares it to your directory, and removes what you approve. |
| Audit evidence | Nothing logged inside Atlassian. | Step level evidence for every action StitchOps takes in Atlassian. |
Single sign on
Okta, from the OIN
Password fill only (SWA). No SAML or OIDC.
StitchOps
Enterprise password management signs users in to Atlassian with vaulted credentials. Users never need the password.
Shared accounts and MFA
Okta, from the OIN
Not part of the OIN listing.
StitchOps
Shares Atlassian logins and their MFA across a team, with credentials kept in your vault.
Joiners
Okta, from the OIN
Creates accounts through the OIN connector.
StitchOps
Not needed.
Movers
Okta, from the OIN
Updates accounts through the OIN connector.
StitchOps
Not needed.
Leavers
Okta, from the OIN
No deprovisioning in the OIN.
StitchOps
Removes Atlassian access the day someone leaves, anywhere a person can log in and act, and saves evidence of the removal.
Password rotation
Okta, from the OIN
Pushes the Okta password to the app. No rotation of shared logins.
StitchOps
Changes the Atlassian password on a schedule and the day someone leaves, and updates your vault in the same run.
Access reviews
Okta, from the OIN
No connector to read or remove Atlassian accounts.
StitchOps
Pulls the Atlassian user list on a schedule, compares it to your directory, and removes what you approve.
Audit evidence
Okta, from the OIN
Nothing logged inside Atlassian.
StitchOps
Step level evidence for every action StitchOps takes in Atlassian.
Okta coverage from the Okta Integration Network, read October 10, 2026. Bitbucket on okta.com StitchOps for Okta →
SCIM and API tax
What Atlassian charges to automate accounts.
Atlassian includes SCIM provisioning only on Add-on (Atlassian Guard Standard), at $4.2 per user a month. The plan most teams buy is Not published.
SSO sits on the same plan as SCIM or above it. If you need SSO anyway, that upgrade is not avoidable, and the calculator counts it that way.
Pricing notes
Guard Standard $4.20 per user a month includes SCIM. Guard Premium $8.18 per user a month. Add on layered on top of Jira/Confluence/etc. Multiplier N/A because no base 'team plan' on this product specifically.
Last verified 2026-06-12. Source · SCIM pricing for every app · Method
Pricing data includes the SCIM Tax Index (Iden), CC BY 4.0, https://scimtax.org/. Modified and extended by StitchOps.
Estimate Atlassian and your other apps
Loading prices.
Expected scenario, list prices, SSO required, default department shares.
Automate Atlassian accounts on the plan you have.
StitchOps carries what your identity provider decides into the app, through an API when one exists, and anywhere a person can log in and act when one does not.
Joiners
Create the Atlassian account with the right role when your HR system or identity provider says someone starts.
Movers
Change Atlassian roles, teams and access when someone changes department or manager.
Leavers
Remove Atlassian access the same day someone leaves, and free the seat.
Access checks
List who can log in to Atlassian on a schedule, with evidence for the audit.
Common questions.
Does Atlassian support SCIM?
Yes, but only on Add-on (Atlassian Guard Standard), at $4.2 per user a month. On the plan most teams buy, SCIM is not available.
Which Atlassian plan includes SCIM?
Add-on (Atlassian Guard Standard), at $4.2 per user a month, against Not published for the plan most teams buy.
Can Atlassian accounts be automated without upgrading?
Yes. StitchOps creates, changes and removes Atlassian accounts on the plan you already have, triggered by the events your identity provider already sends. It uses an API when one exists and works anywhere a person can log in and act when one does not.
Is Atlassian in the Okta Integration Network?
Yes. As of October 10, 2026, the OIN lists Bitbucket and Atlassian Jira Cloud with SWA sign in and provisioning to create and update users.
Can Okta deprovision Atlassian users?
Not through an OIN connector. StitchOps removes Atlassian accounts the day someone leaves, anywhere a person can log in and act, and saves evidence of each removal.
How do you rotate Atlassian passwords when someone leaves?
StitchOps logs in to Atlassian, sets a new password, confirms it took effect, and updates 1Password, Keeper or the StitchOps vault in the same run.
Last updated . Product names are trademarks of their respective owners. StitchOps is not affiliated with or endorsed by them.
Start with one workflow that never had an API.
Fifteen minutes on your top three manual processes. We tell you which one to run first.