SCIM directory sync for SSO

If your team signs in with SSO, member provisioning is now automatic. Assign someone to Trigger.dev in your identity provider and they're added to your org; unassign them and their access is revoked.

Oskar Otwinowski

Oskar Otwinowski

Software Engineer, Trigger.dev

Matt Aitken

Matt Aitken

CEO, Trigger.dev

Image for SCIM directory sync for SSO

Directory sync is now live for orgs on SSO. Your org's membership follows your directory automatically, so you stop maintaining two lists of who has access. Offboarding stops being a checklist item someone forgets.

Built on your existing SSO

Directory sync rides on the same SAML connection your team already signs in through, under the login and security policy you run everywhere else. Nothing changes about how people sign in; you're adding automatic provisioning on top of it.

How it works

Connect your directory once, then your IdP does the work: add a member, remove one, or change who's in a group, and the change is pushed to your Trigger.dev org automatically. Okta, Microsoft Entra, Google Workspace, JumpCloud, OneLogin, and more all work out of the box.

Once it's on, you manage it from the SSO & Directory Sync settings page in your organization.

Get set up

SCIM directory sync is available on the Enterprise plan. Get in touch and we'll connect your identity provider.

Ready to start building?

Build and deploy your first task in 3 minutes.

Get started now