Logging in to Intiveo using Single Sign-on (SSO)

Intiveo now supports Single Sign-on (SSO), which allows you to using a shared identity provider (like Azure or Oracle) as your credentials for Intiveo. Once single sign-on is enabled for your account, you won't need a separate Intiveo password to sign in—you'll simply select your identity provider from the single sign-on options on the login page and enter that password via the window that pops up to sign in to Intiveo.

Requirements

In order to use single sign-on, there are a few requirements.

1. Intiveo supports multiple identity providers to help streamline authentication for your organization. We currently support Azure Active Directory (Entra), Oracle IDCS, Microsoft AD FS, and Shibboleth.If your organization uses a different identity provider (e.g., Google, Auth0, etc.), please contact Intiveo's Support team or your Customer Success Manager (CSM) to discuss adding support for your provider.
2. Enable SSO for your account. By default, all accounts use Intiveo usernames and passwords for user authentication. In order to sign in via SSO instead, Intiveo's staff must enable your identity provider as the sole login option for your organization. Please contact your CSM or Intiveo's support team for help with this.
3. Create a matching Intiveo user for all users. For added security, a member of your organization will not be able to sign in via SSO unless you have created a parallel Intiveo user for that person. You can do this on a case-by-case basis using any existing user with permission to create other Intiveo users, or you can provide your CSM or Intiveo's support team a CSV with all the users you want created for your organization. To complete this task for you, we'll need the following information for each new user:
   • First name
   • Last name
   • Work email address (this must match the one registered with your identity provider)
   • Phone number (this is often the phone number for the office where they work; this would be the number a support team member would call if they needed to reach that user about a support ticket or so on)
   • Required Intiveo user role (this would control which parts of the app that user should be able to access and what sorts of actions that user should be able to complete in Intiveo. If you'd like a list of your existing user roles, contact your CSM or Intiveo's support team.)
   • (For multilocation accounts) Accessible offices (this would control which offices in your account you want the user to be able to access)

Once all of these steps are complete, your users will be able to log in to Intiveo using your existing identity provider credentials.