---
title: "Set up company sign-in and user provisioning - In Parallel help"
description: "For IT admins setting up single sign-on with Okta or Microsoft Entra ID and managing the member lifecycle with SCIM."
url: https://www.in-parallel.com/help/set-up-company-sign-in-and-user-provisioning/
---

# Set up company sign-in and user provisioning

For IT admins setting up single sign-on with Okta or Microsoft Entra ID and managing the member lifecycle with SCIM.

how to · admin

On this page

IT administration

If you manage identity for your company, use this guide to connect Okta or Microsoft Entra ID so employees can sign in with their work account. If your directory also manages who has access when people join or leave, follow the SCIM provisioning steps.

## Before you start

Choose one non-admin pilot user whose work email you control. You can do the setup yourself if you have all three kinds of access, or divide it among colleagues.

- **In Parallel Company admin.** Open the user menu, select **Settings** , then select your Company. You’ll verify domains and configure sign-in under **Security** , create a token under **Provisioning** if using SCIM, and check the pilot under **Members** . [Manage your Company settings](https://www.in-parallel.com/help/company-settings/)
- **Identity-provider admin.** Configure the application in Okta or Microsoft Entra ID, assign the pilot, and use your provider’s logs to check the result.
- **DNS administrator.** Publish the TXT record for each domain used in employee email addresses. The Company admin can then confirm verification in In Parallel.

## Verify your work email domain

**Check your access policy before claiming a domain.** With **Domain auto-join** on, anyone with a verified work address on that domain can join without an invitation through an enabled Google or Microsoft sign-in. Assigning just the pilot to your single sign-on (SSO) app limits access through that app. Employees can still use those other enabled methods. If your policy requires invitation-only access, discuss the setup with your In Parallel Customer Success contact before claiming the domain.

1. In **Company settings → Security → Domains** , find the work email domain under **Domain auto-join** . If it’s missing, claim it there if the option is available, or ask your Customer Success contact to help add it.
2. Under **Verified domains** , find that exact domain. Select **Check DNS** if the TXT record is hidden. Ask your DNS administrator to publish a TXT record using the **Host** and the full **Value** shown. Paste the value without adding quotes.
3. Select **Check DNS** again and look for **Verified** . If the check fails, compare the published value and check whether your DNS provider appended the domain to the host twice. Allow time for DNS changes to propagate.
4. Repeat for each domain used in work email addresses, including subdomains. One verification per domain covers Okta, Entra SAML and SCIM.

Turning off **Domain auto-join** removes the claim and its verification. Okta and SAML sign-in and new-user provisioning stop for that domain. SCIM can still deactivate existing members.

## Set up single sign-on

Follow the steps for the provider your company uses. Once SSO is configured, an assigned employee with a verified-domain address can join on first sign-in. If you plan to test SCIM creation, assign a pilot who is new to the company in In Parallel and provision them before their first sign-in.

### Okta

1. Open **Company settings → Security → Okta sign-in** . In a second tab, open the Okta Admin Console and select **Applications → Applications → Create App Integration** .
2. Choose **OIDC – OpenID Connect** and **Web Application** . Use **Authorization Code** for the grant type and **Client secret** for client authentication. The sign-in scopes are `openid` , `email` and `profile` .
3. Copy **Sign-in redirect URI** and **Initiate login URI** from In Parallel into the matching Okta fields. Set **Login initiated by** to **Either Okta or App** and assign the pilot user.
4. Back in In Parallel, enter your end-user Okta domain, **Client ID** and **Client secret** . Use the hostname employees visit to sign in. The address containing `-admin` opens the Admin Console. A custom hostname must match or sit under a domain you verified in In Parallel. Select **Save and turn on** .

For an optional sign-in check, sign in through **SSO** as the pilot in a private window. Confirm the company name, then look for **Last successful Okta sign-in** in Company settings. At least one other sign-in method stays enabled alongside Okta.

### Microsoft Entra ID (SAML)

1. Open **Company settings → Security → SAML sign-in** . In the Microsoft Entra admin center, select **Enterprise applications → New application → Create your own application** . Choose the non-gallery option. Limit ownership to the IT admins who manage sign-in.
2. In the enterprise application, set **Assignment required** to **Yes** . Assign the pilot user or test group. Under **Single sign-on** , choose **SAML** .
3. Under **Basic SAML Configuration** , copy all three values from In Parallel into the matching fields. **Identifier (Entity ID)** identifies your company’s connection. **Reply URL** receives the SAML response. **Sign on URL** starts sign-in from My Apps or Entra’s test button.
4. Sign the SAML assertion with **SHA-256** . Signing both the response and assertion also works. Leave token encryption off. Set the email claim source to `user.mail` and confirm the pilot has a value on the verified domain.
5. Under **Single sign-on → SAML Certificates** , copy the **App Federation Metadata URL** . Paste it into **SAML sign-in** in In Parallel and select **Save** . When the pilot is ready to sign in, open a private window and select **SSO** on the In Parallel sign-in page. The pilot can also use the My Apps tile if your IT team has made it available. Confirm the pilot reaches the intended company.

### What to tell employees

Send employees the [In Parallel sign-in page](https://www.in-parallel.ai/?intent=login). If someone has a Workspace invitation, ask them to open it first and use the address it was sent to. Your company chooses which methods are available. To change them, contact your In Parallel Customer Success contact.

- **Okta or Entra SAML.** Select **SSO** , enter your work email and select **Continue** . The email domain directs you to your provider. If both providers appear, choose the one your IT team uses. You can also use the Okta or My Apps tile if IT has made it available.
- **Microsoft.** Choose **Continue with Microsoft** for Microsoft account sign-in. For a company-managed Entra SAML app, choose **SSO** . If Microsoft displays **Need admin approval** , ask your Microsoft administrator to review the request.
- **Google.** Choose **Continue with Google** , select your work account and grant the requested calendar access to complete sign-in.
- **Email.** Enter your work address and select **Send code** . Enter the six-digit code from the email in the browser where you requested it. It works once and expires after ten minutes. If you request another code there, use the newest one.

After email, Okta or Entra SAML sign-in, employees can connect a calendar under **Settings → Account → Connections**. AI clients have their own Workspace connection. [Getting started with In Parallel](https://www.in-parallel.com/help/getting-started-with-in-parallel/) · [Connect your AI tool to In Parallel](https://www.in-parallel.com/help/connect-your-ai-tool-mcp/)

If SSO can’t find a connection, compare the domain after the pilot’s `@` with **Verified domains**, including any subdomain. Check the saved provider in **Security** and the pilot’s app assignment. Okta must report the email as verified. For Entra, check `user.mail` and the three **Basic SAML Configuration** values.

## Connect your directory with SCIM

SCIM (System for Cross-domain Identity Management) lets your directory create, update and deactivate In Parallel members. Employees still use one of your company’s enabled sign-in methods.

Choose one directory to manage each member. Any active provisioning token for your company can update the same members. Start with the pilot only. You can assign a directory group to select users, but In Parallel provisions individuals. Leave group provisioning and password synchronization off.

1. In In Parallel, open **Company settings → Provisioning** and select **Copy base URL** .
2. Give the connection a recognizable label and select **Create token** . Store the full token in your approved credential store while it’s visible. Creating the first active token turns provisioning on.
3. Follow the steps for your directory below.

### Okta provisioning

In Parallel recommends **SCIM 2.0 Test App (OAuth Bearer Token)** for its provisioning connection, including production. Okta documents this template for development and testing only. Check with your IT team and In Parallel support before expanding beyond the pilot. [Okta’s guidance on SCIM Test Apps](https://support.okta.com/help/s/article/What-are-SCIM-20-Test-Apps?language=en_US)

1. In **Applications → Browse App Catalog** , select **SCIM 2.0 Test App (OAuth Bearer Token) → Add Integration** . Use a separate app from your Okta sign-in app. You can customize its name and icon.
2. Open **Provisioning → Configure API Integration → Enable API Integration** . Paste the base URL into **SCIM 2.0 Base URL** and the token as copied into **OAuth Bearer Token** . Select **Test API Credentials** , then **Save** .
3. Set the application username to the pilot’s sign-in email. Under **Provisioning → To App** , enable **Create Users** , **Update User Attributes** and **Deactivate Users** . Assign the pilot to both apps and check the provisioning result in Okta.

### Microsoft Entra ID provisioning

1. Open **Provisioning** in your In Parallel non-gallery enterprise application. You can use the same app as for SAML. Configure automatic provisioning and paste the base URL into **Tenant URL** and the token into **Secret Token** . Select **Test Connection** and save.
2. In the user attribute mappings, map `mail` to `userName` . Use the email the pilot signs in with, which may differ from `userPrincipalName` . For name updates, map `givenName` to `name.givenName` and `surname` to `name.familyName` . Turn off the group mapping.
3. Set the scope to assigned users and groups. Assign the pilot, run **Provision on demand** for that person and check Entra’s provisioning logs.

Entra normally syncs changes about every 40 minutes. In Parallel applies each change when it receives the SCIM request. A paused user can still have access until the deactivation reaches In Parallel. Check the user’s provisioning log in Entra before testing access.

## Test joining, leaving and returning

Keep a Company admin signed in separately. Use the non-admin pilot for all four checks. SCIM creation sends no invitation email, so give the pilot the sign-in link or their provider tile.

1. **Create.** Run provisioning for the assigned pilot. Find the successful create in the provider’s log and the work email in **Company settings → Members** . Sign in as the pilot in a private window and check the company name.
2. **Update.** Change the pilot’s name in the directory, sync and confirm the new name in **Members** .
3. **Pause.** Have the directory send a deactivation ( `active = false` ). Check that the pilot’s open session closes and that a fresh sign-in is refused, including through another enabled method. Removing only the sign-in app assignment leaves other methods available.
4. **Resume.** Reactivate the pilot ( `active = true` ), sync and confirm they can sign back in to the same membership.

After the checks pass, expand the approved app assignments. In Entra, start scheduled provisioning for the intended users.

If a user is missing, check their individual provisioning log entry. For a domain error, verify the exact email domain and retry. For an address conflict, check **Members** for the email. If it belongs to another account, contact support. For an authorization error, check the base URL and confirm the token is active and belongs to the intended In Parallel company.

## Offboard a member or rotate a token

**Pause or depart a member.** A pause is reversible. A SCIM `DELETE` triggers departure. In Parallel closes the member’s sessions, hands over open work and stops returning the member to the directory. To bring them back, have the directory create them again. Completed handovers stay in effect.

**Preserve admin access.** Manage Company admin roles in In Parallel. SCIM creates ordinary members and restores a departed admin as an ordinary member. Give another member the Company admin role before pausing or departing the last active admin.

**Rotate a provisioning token.** Create a second token, update the directory and test the connection. Check the new token’s last-used time under **Provisioning**, then revoke the old token. Use the same sequence if you lose a token. Tokens work until revoked. Revoking the last active token stops all directory updates, including deactivations.

If you need help, send the company name, the failed step, the time with time zone and the error message. Remove tokens, client secrets and sign-in codes from screenshots. [Contact In Parallel support](mailto:support@in-parallel.com)

[All help articles](https://www.in-parallel.com/help/)
