.png)
Automate Jira access provisioning and deprovisioning through Rippling so engineering and product teams get the right project access on day one and lose it cleanly when they leave.
The Rippling–Jira integration uses Rippling as the identity source for Jira user provisioning. When a new hire joins in an engineering, product, or technical role, Rippling automatically creates their Jira account and assigns them to the correct projects and groups based on their department and job level. When they leave, Jira access is revoked as part of Rippling's standard offboarding workflow.
For companies using Jira Cloud with SSO, Rippling also manages the identity layer — ensuring Jira access is tied to active employment status rather than manually managed licenses.
The most common gap is provisioning Jira accounts manually outside of Rippling, which breaks the offboarding workflow. When IT manages Jira access separately, terminated employees often retain Jira licenses and project access for days or weeks after their last day.
Teams also miss configuring group-level provisioning — assigning users to the right Jira projects and permission schemes based on their Rippling department and role, rather than defaulting all users to a single group.
thePeopleStack configures SCIM-based provisioning between Rippling and Jira Cloud, including group mapping for project-level access aligned to Rippling department and job level structure. We ensure offboarding events in Rippling trigger immediate Jira license revocation and document the provisioning logic for IT handoff.
For companies with Canadian employees using Jira, thePeopleStack ensures provisioning rules respect any relevant data handling considerations for Canadian employee records stored in Atlassian's cloud infrastructure.
Yes. Rippling supports SCIM provisioning for Jira Cloud through Atlassian Access. This allows Rippling to create, update, and deprovision Jira users automatically based on employment status changes.
Yes, through group-level provisioning. Rippling maps department and job level to Jira groups, and Jira's permission schemes control which projects those groups can access. This eliminates manual project assignment for new hires.
When a termination is processed in Rippling, the SCIM integration deprovisions the Jira account — removing access to all projects and releasing the license. This happens as part of Rippling's standard offboarding workflow without requiring manual IT action.
Yes. SCIM provisioning for Jira Cloud requires an Atlassian Access (now called Atlassian Guard) subscription. thePeopleStack can advise on licensing requirements during the scoping process.
Yes. Rippling's Atlassian SCIM integration covers both Jira and Confluence under the same Atlassian Access configuration. thePeopleStack can configure both simultaneously.