Skip to main content
Some companies run the same SaaS more than once: one Google Workspace per subsidiary, or a separate Microsoft Entra tenant for a newly acquired entity. Connect each of them to Primo as its own instance. Each instance has its own connection, accounts and settings. To connect a SaaS for the first time, see Connect your SaaS.

​
Add another instance

1

Go to SaaS > Directory and click Add a SaaS

Under Or choose from our catalog of SaaS, click the SaaS, even if you already added it.
2

Open the new instance

Primo adds a new instance and opens its page. It takes the name of the SaaS, followed by a number when that name is already used: Slack (2), Slack (3).
3

Connect the instance

Follow the on-screen instructions on its page, as for any SaaS. For Google Workspace or Microsoft Entra ID, sign in with an administrator account of the tenant this instance covers. See Connect your email provider.
There is no limit on the number of instances.
Adding a SaaS from the catalog requires SaaS Management, except for Google Workspace, Microsoft Entra ID and Vanta. Without it, the other SaaS show a star icon in the catalog, and clicking one opens the SaaS Management upgrade window.

​
Rename an instance

Give each instance a name your team recognizes, such as the entity or the domain it covers.
1

Open the instance from SaaS > Directory

Click its name at the top of the page.
2

Type the new name

Press Enter to save, or Escape to cancel.
Renaming requires the Manage SaaS permission. The new name shows wherever the instance appears, including the SaaS list and the accounts on employee profiles.

​
Understand how instances work

  • Each instance has its own row in SaaS > Directory and its own page, with its own accounts, licences and provisioning rules.
  • On an employee’s profile, the accounts of one instance are listed together, and each account shows the name of its instance.
  • An account found by SaaS discovery goes to the instance that already has an account with that email. Otherwise it goes to the instance with the most accounts on the same email domain. If none matches, it goes to the instance added first.
  • At offboarding, each instance where the leaver has an account is listed separately, and Primo deprovisions the leaver on the instances selected for deprovisioning.
  • You can connect SSO on each instance separately, with its own service provider identifier.
  • When an instance is your company’s email provider, Primo adds its email domain to your company’s domains when it’s missing, and checks again at each sync. Your other domains stay as they are. Only one instance can be your company’s email provider.
  • Windows Autopilot keeps using the Microsoft Entra instance it was set up with.

​
What if the tenant is already connected?

A Google Workspace or Microsoft Entra tenant can be connected to one instance of that SaaS only. If another instance already uses it, Primo refuses the connection and saves nothing. When it can, the message names the instance that holds the tenant. Connect another tenant, or keep using that instance. Reconnecting an instance to its own tenant still works.

​
Contact

If an instance doesn’t connect or accounts land on the wrong instance, contact support@getprimo.com with:
  • The SaaS and the names of its instances
  • The tenant or the domain you tried to connect
  • The error message Primo showed, if any