> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Connecting Bluebeam to Neo

> Generate a SCIM token in a client's Bluebeam Org Admin and save it in Neo

You connect Bluebeam once for each client that uses it, with one value from that client's Bluebeam account: a SCIM token.

## Before you start

Bluebeam offers SCIM only on an account that has single sign-on (SSO) and SCIM turned on. If the client's account has no **SCIM Provisioning** setting in Org Admin, ask Bluebeam to enable SSO and SCIM for the account first, and set up SSO as Bluebeam's guide says. Org Admin is available to accounts with more than two Bluebeam licences.

> [!NOTE]
>
> If the client's identity provider already provisions Bluebeam through SCIM, you can leave Bluebeam unconnected and change plans where that provider keeps them, by moving the user between its Bluebeam groups:
>
> * **Microsoft Entra ID:** give the agent the Microsoft 365 permissions to change the client's Entra groups.
> * **Okta:** [connect Okta](https://docs.neoagent.io/integrations/okta/connecting-to-neo.md) for the client, and give the agent the Okta permission to change group members.
>
> If you connect Bluebeam as well, tell the agent in its instructions which provider keeps this client's plans, because that provider's next sync can undo a change made in Bluebeam directly.

## 1. Generate a SCIM token in Bluebeam

**1. Sign in to Org Admin**

Sign in to [Bluebeam Org Admin](https://app.bluebeam.com/org-admin) as an admin who may manage SSO and SCIM for the client's account.

**2. Open SCIM Provisioning**

Open **Accounts**, select the client's account, open **Settings**, and select **Configure** next to **SCIM Provisioning**.

**3. Generate the token**

Select **Generate Token**, enter a name such as `Neo`, and select **Generate**. Copy the token: Bluebeam shows it once. An account can hold five tokens, so Neo's token sits beside the one your identity provider uses.

**4. Check the plan groups**

Open **Users** → **Synced Groups**. Each plan Neo assigns needs a group mapped to it, such as **Bluebeam Core**. If the account has no synced groups yet, an agent with the **Plan Groups** permission can create them, and you then map each one to its plan here.

## 2. Add the token in Neo

**1. Open Integrations**

In the Neo Dashboard, open [**Integrations** → **Bluebeam**](https://dashboard.neoagent.io/integrations?open=bluebeam), under HR & Business Apps.

**2. Pick the client**

In **Customer**, choose the client this Bluebeam account belongs to. The client must be on your **Companies** tab. For a second client, click **Add customer**.

**3. Save the token**

Paste the SCIM token and click **Save settings**. Neo checks it against Bluebeam before saving: a mistyped or deleted token is rejected straight away.

> [!WARNING]
>
> If someone deletes the token in Org Admin or turns SCIM Provisioning off, save a new token here. Neo loses access to that client's Bluebeam account until you do.

## 3. Turn Bluebeam on per agent

**1. Open the agent's tools**

Open the agent in the Neo Dashboard, go to its **Tools & Settings** tab and click **HR & Business Apps**, or ask your Neo Support Agent to add Bluebeam to it.

**2. Pick a preset**

Expand the **Bluebeam** block and pick one of its **Presets**, or set each permission group by hand.

| Preset | What it does |
| - | - |
| **Read Only** | Reads users and plan groups; changes nothing |
| **Helpdesk** | Creates and deactivates users and assigns and frees plans, asking a technician before each change |
| **IT Admin** | User and plan changes on their own; creating, renaming or deleting a plan group asks a technician |
| **Full Automation** | Every supported call without approval, except the few that replace a whole record or end many users' plans |

An onboarding or offboarding agent needs **Users** and **Plans & Licences**. A plan report needs both as Read Only.

## Before an agent creates users

Bluebeam creates a user only in an email domain the account's SSO covers. Never put the account's IT Admin in a plan group: Bluebeam then changes them to an Org Admin, and only Bluebeam support can undo it.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.