Skip to main content
All CollectionsGetting StartedSetting Up
Velocity Authentication Options
Velocity Authentication Options

Details on accessing Velocity via OAuth or SAML.

Written by James McGill
Updated over a week ago

We use two different authentication flows for user management and security: SAML and OAuth. By providing different authentication options, we allow our customers to distribute access to Velocity to their organization in a secure and controlled way.

  • For OAuth, we provide access to login to Velocity via VCS (Github, Bitbucket, or Gitlab) or Google OAuth.

  • For larger organizations, we offer SAML, or auto-provisioning, which gives companies access to auto-assign roles and access to Velocity.

For added security, we log users out of Velocity every 24-hours.

Admins can configure the ways in which users can authenticate into Velocity from the Authentication settings page. There are three options:

  • No Authentication Method Selected (default)

  • Google as Authentication

  • SAML as Authentication

No Authentication Method Selected

By default, no authentication method is selected meaning users from an organization can log in via Oath using any method.

Google as Authentication

If Google is selected, users from an organization can only login via Google.

  • If users try to login via another way, they will get an error message that says "Your Velocity organization requires signing in with a G Suite OAuth account.

For either No Authentication or Google, if a user puts in their email address in Login with SSO, they will get an error message saying SSO sign-in not found.

SAML as Authentication

If SAML is selected as the authentication, the user will put in their email address to the box at the bottom of the login screen. The user will be taken to the correct SAML portal to login for their organization.

Did this answer your question?