Skip to main content
Bluebeam Revu subscriptions are managed per Bluebeam account: who has a user, and which plan (Basics, Core, Complete or Max) each user holds. Each of your clients that buys Bluebeam has its own account. Connect Bluebeam for those clients, and Neo agents can work in it while they handle an onboarding or offboarding ticket.

What Neo can do with Bluebeam

  • Create the Bluebeam user for a new hire and assign their Revu plan, from the same onboarding ticket as their Microsoft 365 account
  • Deactivate a leaver and free their plan
  • Move a user to another plan, or to Unpaid Collaborator to free a paid seat and keep the account
  • Find a user and check which plan they hold, and list who holds each plan
Neo works through Bluebeam’s SCIM provisioning, the same interface Microsoft Entra ID and Okta use. See Bluebeam API for the permission groups and profiles.

How plans work

Bluebeam gives each user the plan of the SCIM group they belong to, and an admin maps each group to a plan in Bluebeam Org Admin (Users → Synced Groups). Neo assigns a plan by adding the user to that plan’s group, and frees it by taking them out. A user belongs to one plan group at a time.

One connection per client

A SCIM token belongs to one Bluebeam account, so you connect Bluebeam once for each client, with a token from that client’s account, and the connection belongs to that client’s company in Neo. On a ticket that belongs to a company, the agent reaches only that company’s connection. A ticket with no company reaches no client’s connection. In a chat or a scheduled agent, the agent names the client it works for, and Neo accepts only a company on your Companies tab.

Next steps

Connect Bluebeam

Turn on SCIM in a client’s Bluebeam account, generate a token and save it in Neo.