Skip to content

Blog

How to automate onboarding across your tools

Four ways to automate onboarding across your SaaS tools, from SCIM to role bundles, what each costs a 20-person company, and how to stop surprise paid seats.

· 9 min read

You can automate onboarding across your tools in four ways: SCIM provisioning from an identity provider, which is the cleanest but usually needs Enterprise plans; workflow tools such as Zapier-style automations; scripts against each tool's API; and role bundles run by an agent that does the invites for you. Which one fits depends less on technology than on what plans you are on and what you are willing to pay per seat.

Whichever you pick, the hard part is deciding once what each role gets. Automation without that decision just sends the wrong invites faster.

The manual cost

Inviting one person to one tool looks like a two-minute job. Done properly, it is a sequence. You open the tool's admin page and find the members screen, which every tool hides somewhere different. You type the work email, without a typo. You pick the role inside the tool: member, not admin; editor, not viewer. You add them to the right teams, channels, projects or repositories. You decide whether the seat costs money, and check with someone if it does. And later, you check the invite was accepted, and resend it when it was not.

Say a new engineer needs fifteen tools and each takes five minutes when nothing goes wrong. That is well over an hour of clicking, by someone who has other work, before a single invite lands in spam or goes to a personal address.

The time is the visible cost. The invisible ones are worse. Steps get skipped when the person doing them is busy, so new hires start without the error tracker or with admin rights "to save time". Nothing is recorded, so nobody can say later what was given. And the work does not get faster with practice, because it is done from memory each time.

SCIM and its price

SCIM (System for Cross-domain Identity Management) is the standard way to automate this. Your identity provider holds the list of people and their groups; when you add someone to "Engineering", it calls each connected tool's SCIM API and creates their account. What is SCIM explains it in full.

It works well. The problem is the price of getting to it. Tools usually keep SCIM on the same plan as SAML single sign-on, and sometimes a higher one. As we read each vendor's own pages on 27 October 2026:

ToolPlan without SCIMCheapest plan with SCIMExtra per seat, a year
GitHubTeam, $4 per user a monthEnterprise, $21 per user a month$204
FigmaProfessional, $16 per full seat a monthOrganization, $55 per full seat a month, billed annually$468
NotionPlus or Business (Business has SAML SSO)Enterprise, custom pricingNot published
SlackProBusiness+See below

Sources: GitHub pricing, Figma pricing and Figma's SCIM help article, Notion pricing, and Slack's SCIM help article, which says SCIM is "Available on the Business+ and Enterprise plans". Slack's pricing page showed us prices in euros only, so we leave its dollar figure out rather than guess. Figma also requires SAML SSO to be set up before SCIM.

Then add the identity provider. SCIM needs one that can push changes, such as Okta, Microsoft Entra ID or JumpCloud, and provisioning is often a paid tier or add-on there too. Okta pricing and JumpCloud pricing have the current numbers.

A worked example at 20 people

Take a 20-person company where 8 engineers use GitHub and 4 designers use Figma, using the list prices above. Moving the 8 GitHub seats from Team to Enterprise adds $204 a seat a year, or $1,632. Moving the 4 Figma full seats from Professional to Organization adds $468 a seat a year, or $1,872. That is $3,504 a year in plan upgrades for two tools, before the identity provider, and before any of the tools that offer SCIM only on a custom-priced Enterprise plan. The SSO tax calculator runs the same sum for your own tools and headcount.

So SCIM onboarding is not one purchase. It is an upgrade of every seat in every tool that supports it, plus an identity provider, plus manual work for every tool that does not support it at any price. For a company with 500 people that maths can work. For 20, it usually does not. SCIM provisioning works through the full cost.

Workflow tools

Workflow tools (Zapier, Make, n8n and similar) connect a trigger to actions: "when a new user appears in Google Workspace, do these things". For onboarding, that can mean posting a welcome message, creating a task list, or sending invites to the tools the workflow tool has an action for.

They are cheap to start and genuinely useful for the soft parts of onboarding. For accounts, they have limits worth knowing before you build.

Coverage is patchy. A workflow can only invite people to tools whose integration offers that action. Many integrations can post messages or create records but cannot add a member with a role.

Admin tokens move to a third party. To invite people, the workflow needs an admin-level token for each tool, stored in the workflow tool. That is a real security decision; make it on purpose.

Failures are quiet. When a tool changes its API or a token expires, the workflow stops, and often nobody notices until a new hire says they never got an invite.

It rarely covers the other end. Building the removal flow is usually a second project that does not happen, so offboarding stays manual. How to automate offboarding covers that side.

Someone has to own it. The workflow is software. When its author leaves, it becomes an orphan, like their accounts.

Scripts against each tool's member API have the same profile with more control: excellent for the three tools with good APIs, a maintenance job forever after.

Role bundles and agents

The approach that fits most small teams starts with a role bundle: a named list of tools, with the role inside each, for one kind of job. "Engineer" might be GitHub as a member of the engineering team, Linear, Vercel, Sentry, and the engineering Slack channels. Writing the bundles is free, and on its own it already makes manual onboarding faster and more consistent. Role-based access control explains how to define them.

The automation then runs the bundle. For each tool in it, something has to do the invite. Where the tool has a member API on your plan and you are willing to hand over a token, an API call does it. Where it does not, a browser agent can. An agent is software that drives the tool's admin page the way you would, in a browser where an admin is signed in. It needs no Enterprise plan and no API, because it uses the same screens you use.

Agents have honest drawbacks. They are slower than an API. They break when a tool redesigns its admin pages. And some tools' terms of service restrict automated use, so read them for the tools that matter to you. In return they reach tools that no plan you can afford would ever automate. Automated user provisioning compares the options in more depth.

Approvals for paid seats

The fastest way to make automated onboarding expensive is to let it add seats without asking. A bundle that includes a design tool will happily give every new engineer a full seat they will open once. Build the approval into the flow, not around it.

Start by marking which bundle items are paid seats, and which seat type each role needs. Then make the flow pause on paid steps: the free invites run, and the paid ones wait for a yes. Name the approver per tool or per team, usually a manager for their team's tools and finance or a founder for the expensive ones. Finally, keep the yes. Who approved what, and when, belongs in the same record as the invite itself. That record is also what an auditor or a user access review asks for.

Also check which of your tools let anyone with your email domain join on their own. Domain auto-join is automated onboarding with no approval step at all.

The cheapest way to start

You do not have to pick one method for everything. Most small companies end up with a mix, and the cheapest order to build it in looks like this.

Write the bundles first. It costs an afternoon and makes every later step easier, including doing it by hand.

Use what your directory already does. Google Groups that grant shared drives, calendars and mailing lists are free automation you may already be paying for. Put new hires in the right groups and a chunk of onboarding happens on its own.

Use SCIM where you already pay for it. If a tool's SCIM is on a plan you are on for other reasons, connect it. Do not upgrade a tool only to get it unless the numbers above work for you.

Automate the rest by bundle, through APIs or an agent, with approvals on paid seats.

Make sure the same mechanism removes people. Onboarding automation that cannot reverse itself leaves you with faster joiners and the same slow, error-prone leavers. The JML process treats both ends, and the moves in between, as one system.

Where SmashSSO fits

SmashSSO is the role-bundle approach, built as a product. It reads your people from Google Workspace with read-only access. You define access bundles by role; assigning one invites the new hire to every tool in it with the right role. Tools where you have added a token are handled through their member API, and the rest by an agent in your own Chrome, in tabs where you are already signed in as an admin. Any step that would add a paid seat pauses for approval, and every change is written to an audit log. Role changes and removals run the same way, so the other end is covered too.

The limits: the agent needs that Chrome open, runs slower than an API and can fail when a tool changes its screens (a failed run says so and shows its last screenshot). It needs Google Workspace as your directory. It is not SSO and does not change how anyone signs in; if an audit or a customer contract names SAML, you need real SSO. It costs a flat fee from $199 a month billed annually, however many people and tools (pricing). The hub post on user provisioning sets it next to the alternatives.

FAQ

Can onboarding be automated?
Yes. Tool invites can be automated through SCIM from an identity provider, workflow tools, scripts against each tool's API, or role bundles run through APIs and browser agents. The decisions about what each role gets still need a person, once.
What is the cheapest way to automate onboarding?
Start by writing role bundles and using the group-based access your directory already gives you, which costs nothing. Use SCIM only where you already pay for a plan that includes it, and automate the remaining tools by bundle.
Can I automate tool invites without SCIM?
Yes. Many tools have a member API you can call with an admin token, and a browser agent can do the invite through a tool's admin page where there is no API on your plan. Agents are slower and can break when a tool changes its screens.
How do I stop accidental paid seats?
Mark which items in each bundle are paid seats, make the automation pause on those steps until a named approver says yes, and keep a record of each approval. Also turn off domain auto-join in tools where anyone with your email domain can add themselves.

Keep reading

Stop paying for a login button.

Sign in with Google Workspace, connect your tools, and see who has access to what in minutes.

Sign up with Google