Enable SAML for Your Command Account
Learn how to enable SAML for your Verkada Command organization
You need Organization Admin permissions in order to set up SSO.
Step 1: Begin setup
Click Add New.
You should see your client ID and the fields that you entered into your IdP.
For Client ID: For US orgs: https://vauth.command.verkada.com/saml/sso/ For EU orgs: https://saml.prod2.verkada.com/saml/sso/
For AUS orgs: https://saml.prod-ap-syd.verkada.com/saml/sso/%3Cclient-ID%3E
For Reply ID: For US orgs: https://vauth.command.verkada.com/saml/sso/ For EU orgs: https://saml.prod2.verkada.com/saml/sso/
For AUS orgs: https://saml.prod-ap-syd.verkada.com/saml/sso/%3Cclient-ID%3E
For Sign-on URL: For US orgs: https://vauth.command.verkada.com/saml/login/ For EU orgs: https://saml.prod2.verkada.com/saml/login/
For AUS orgs: https://saml.prod-ap-syd.verkada.com/saml/login/
Note: To confirm which region you’re located, please refer to where your organization was created for Verkada.
Step 2: Upload SAML XML metadata
You will get a warning that the file has not yet been validated.
If the login tests fail, review your metadata file and associated domains.
You may see this common error message: app_not_configured_for_user or other related messages. This can happen when your browser has cached the apps you have access to from when you first logged in and where you had just created the Verkada app with your IdP.
Step 3: Enforce SSO
After configuring SAML for your Verkada Command organization, you have the option to enable SSO Enforcement.
What this means for you:
Anyone using the configured email domain has to go through the SAML process to sign in.
Allows for greater control over user access.
If there is an issue with SAML, users are unable to sign in, unless the issue is either resolved or SSO Enforcement is disabled.
Need more help? Contact Verkada Support.
Last updated
Was this helpful?



