Provisioning

Provisioning is how the people who run and use your program get into Introw, and how their access stays correct over time, without a list you maintain by hand.

Getting people in should not be a project. Provisioning takes partners, their owners and their contacts from the CRM, and your own team from your identity provider, then keeps all of it current.

​

The problem it solves

Getting the right people into a partner program, and out of it again, is usually manual, duplicated, and a security risk:

​

Impact

The first thing a partner experiences is getting in. When their colleagues are already there and access follows a CRM field rather than a request, the program starts with competence instead of a ticket.

​

See it work

​

How it works

Your CRM already knows your partners, who owns them, and who works there. Introw turns that into a live roster, with no import spreadsheet and before anyone sets up SSO. The partner accounts you pick become partners. Each account’s CRM owner is suggested as an internal team member: accept with one click and they become that partner’s manager. Any partner managers you assign through a CRM field are matched to your team, and every contact on the partner’s company is imported automatically. Access then runs off the same live CRM data. You grant portal access with a toggle, or straight from a CRM field, and group people into dynamic segments built on CRM properties. Who can see what updates itself as the CRM changes. Importing, syncing, and access are one motion, not three. For your internal team you can layer on single sign-on and SCIM, and nothing is ever typed twice or left to drift from the system of record. Instead of re-keying your partner org into a portal and chasing access one person at a time, you point Introw at the CRM and your identity provider once. The partner list, its ownership, and its contacts arrive on their own and stay current. Access and visibility come from four things: a toggle, a CRM field, dynamic segments built on CRM data, and - for your team - SSO or SCIM. The right people are always in with the right scope. The wrong people are out the moment the source of truth says so. Your program is staffed and accessible from day one, and it stays that way with no manual roster to maintain. The people and their access flow straight from your systems of record into a scoped, current roster:

​

Run it from your AI assistant

​

Going deeper

Works with