Just-in-time provisioning (JIT) creates a person's account in a tool the first time they sign in to it through single sign-on, using the details their identity provider sends with the login. Nobody has to send an invite. The catch is in the name: it only acts at sign-in, so it never removes anyone. When people leave, their JIT-created accounts stay.
It is a useful feature, often switched on by default once SSO is set up. Here is how it works, how it compares with SCIM, which tools support it, and the gap it leaves at the other end.
How JIT works
JIT rides on top of single sign-on, usually SAML (what SAML is). The sequence runs in five steps.
First, an admin connects the tool to the identity provider (Google Workspace, Microsoft Entra ID, Okta or similar) and assigns the people or groups who may use it. Later, a new hire opens the tool for the first time, and the tool sends them to the identity provider to sign in. The identity provider sends back a signed login message, called an assertion, with their email, name and sometimes a group or role. The tool looks for a matching account. If none exists, it creates one on the spot from those details, and signs them in. Finally, on later logins, some tools update the name or email from the same message.
Zoom's own SSO guide describes its "At Sign-In" setting as creating the account when the user first authenticates. Figma's help center says JIT lets it create and update users, with changes applied the next time the user logs in. That last detail is the important one: everything JIT does happens at a login.
What a JIT login carries
The account JIT creates is only as good as the assertion behind it. Every setup sends an identifier, almost always the work email, because that is how the tool matches the login to an account. Most send a first and last name. Some can send a group or a role, and a few tools will use that to put the new account in the right team or give it the right permission level.
That last part is where expectations go wrong. Role mapping through JIT is rarer than account creation, it has to be configured attribute by attribute in the identity provider, and it only takes effect when the person signs in again. If you promote someone on Monday and they do not open the tool until Friday, the tool learns about it on Friday. If you demote someone who never signs in again, the tool never learns at all.
The email has to match, too. If a person's account in the tool was created by hand with a different address, or their email changes after a name change, JIT may see a stranger and create a second account, which can mean a second paid seat.
JIT vs SCIM
SCIM is the other way to provision accounts: the identity provider calls the tool's API whenever something changes, whether or not anyone signs in (what SCIM is).
| JIT provisioning | SCIM | |
|---|---|---|
| When it acts | Only when the person signs in | Whenever the directory changes |
| Creates accounts | Yes, on first login | Yes, before first login |
| Updates name or email | Sometimes, at each login | Yes, on change |
| Changes roles and groups | Rarely, and only at login | Usually, if the tool supports group sync |
| Deactivates leavers | No | Yes |
| Setup | A setting in the SSO configuration | An API URL and token, plus attribute mapping |
| Usual plan | Whatever plan has SSO | The SSO plan or a higher one |
So is JIT better than SCIM? It is simpler, and for joining it is often good enough. For leaving it does nothing at all. Many tools let you run both: SCIM to create and remove accounts on schedule, JIT as a fallback for someone who signs in before SCIM has caught up. SCIM vs SAML explains why the login standard and the provisioning standard are sold separately.
The offboarding gap
Here is what happens when someone leaves a company that relies on JIT. You suspend them in the identity provider, which is good: they cannot start a new SSO login. But their account in each tool still exists, because JIT has no event to react to; they will never sign in again. In a per-seat tool, that account keeps holding a paid seat until someone removes it. Any session they already had open may keep working until the tool's own timeout. And anything they own (files, channels, API tokens, integrations) stays attached to a person who is gone.
Zoom's guide says this outright: its sign-in provisioning does not deactivate accounts, and deactivation is a SCIM job. Figma's help center puts deactivation under SCIM, not JIT.
There is a second, quieter cost. With JIT on, anyone your identity provider allows into a tool can create a paid seat in it just by clicking the login button. That is convenient on day one and a surprise on the invoice. Check who is assigned to each tool in the identity provider, because with JIT that assignment is the invite list. Per-seat pricing explains why a few stray seats add up faster than they look.
When JIT is enough
JIT does the job when most of four things are true. The tool is free per seat, or you pay a flat price, so leftover accounts cost nothing. Sessions are short, or SSO is enforced so nobody can log in with a password. Leavers' data is not sensitive, or the tool hides it from people who cannot sign in. And you remove accounts by hand anyway, from a checklist, within a day of someone leaving.
If you pay per seat, hold customer data in the tool, or have no reliable removal step, JIT is half a process.
Size changes the picture less than people expect. At ten people, one leaver a year with a forgotten account is easy to miss and cheap to fix. At 50 people with normal turnover, JIT-created accounts accumulate in every tool behind SSO, and nobody can say from memory which ones are still needed.
Which tools support JIT
Most tools that offer SAML SSO also offer JIT, and on the same plan, because it is part of the login. Some examples, from each vendor's own documentation as we read it on 27 October 2026:
| Tool | JIT behavior | Plan it needs | Source |
|---|---|---|---|
| Zoom | "At Sign-In" provisioning creates the account at first SSO login; does not deactivate | Not stated in the guide; needs an approved vanity URL for SSO | Zoom SSO field guide |
| Figma | All SAML SSO setups support JIT; creates and updates users at next login; deactivation is SCIM's job | Organization or Enterprise, where SAML SSO is available | Figma help |
| Jira, Confluence | Creates an Atlassian account at first SAML login and updates name and email at login | Atlassian Guard, a verified domain, and SSO enforced | Atlassian support |
| Slack | Creates the account at first SSO login if none matches; the default once SSO is configured | Business+ or above, where SAML SSO starts | Slack's Trailhead module |
The plan column is the real story. JIT costs nothing extra on top of SSO, but SSO itself is usually on a higher plan; Atlassian needs its Guard add-on (Atlassian Guard pricing). That is the SSO tax again. For the plan details tool by tool, see Figma SSO, Zoom SSO and Slack SSO.
Questions to ask about a tool's JIT
Vendors describe JIT in a line, and the details live in the help center. Before you rely on it, find four answers. Does a JIT account take a paid seat at once? In per-seat tools it usually does, so you want to know before the first click. Can JIT be switched off, or limited to certain groups? If not, the identity provider's assignment list is your only control. Does it update anything after the first login, such as name, email or role, or does it only create? And what removes the account? If the answer is SCIM, check which plan SCIM is on; if the answer is "an admin", that admin is you, and the removal goes on your checklist.
Common mistakes with JIT
Assigning the tool to everyone. In the identity provider, it is tempting to give every app to the whole company so nobody gets stuck. With JIT on, that turns every curious click into a new account, and in a per-seat tool, a new line on the bill. Assign tools to the groups that need them.
Treating JIT as onboarding. JIT creates an account when someone shows up. It does not add them to the right channels, projects or teams unless the tool maps groups, and it does nothing for tools outside SSO. New hires still need someone to set up their access properly.
Forgetting people outside your domain. Contractors and guests usually cannot sign in through your identity provider, so JIT never sees them. Their accounts are created by invite, live outside the system, and are the easiest to forget when the work ends.
Assuming suspension cleans up. Suspending someone in Google Workspace or Entra ID feels final. In a JIT-only tool it changes nothing about the account itself.
Closing the gap
If you rely on JIT, add a removal step that does not depend on a login.
Keep a list of every tool each person has. JIT creates accounts without telling anyone, so the list goes stale fast unless something builds it for you.
Remove accounts on the day someone leaves, tool by tool, using an employee offboarding checklist.
Add SCIM where it is on your plan. Where a tool offers SCIM on the plan you already have, turn it on; that tool's removals become automatic.
Review access quarterly. Look for accounts that match nobody in your directory. With JIT, those are exactly the ones that pile up, and orphaned accounts covers how to find and clear them.
What is deprovisioning? goes through the removal side in more detail, and user provisioning covers the joining side beyond what JIT does.
Where SmashSSO fits
SmashSSO does the half JIT does not. It is not SSO, so it does not create accounts at login. It reads your people from Google Workspace, shows who has an account in each tool, matched by email, and flags accounts that match nobody in the directory, which is where JIT leftovers end up.
When someone is suspended in Google Workspace, it alerts you and shows every tool they still have access to, then removes them through the tool's member API where you have added a token, or through an agent in your own Chrome where you are signed in as an admin. Adding people works through access bundles by role, and any step that would add a paid seat pauses for your approval, which is the control JIT does not have. Every change goes into an audit log.
The limits: the Chrome agent needs that browser open, it is slower than an API, and it can fail when a tool redesigns its screens. It needs Google Workspace as the directory. It costs a flat fee from $199 a month billed annually (pricing). The hub on what SSO is covers the login side if you are still deciding whether you need SSO at all.