Google Workspace

Before you begin

You will need your socure_public_account_id, available in the RiskOS™ Dashboard on the Developer Workbench > API Keys page under the Customer ID section.

Set Up Single Sign-On (SSO) with Google Workspace

1. Configure SAML in Google Workspace

Follow these steps to create a SAML 2.0 integration in Google Workspace:

Log into your Google Workspace account.
From the Admin Console Home Page, go to Apps > Web and mobile apps.
Click Add App > Add custom SAML app.
On the App Details page:
- Enter the app name as Socure SSO Integration.
- (Optional) Add a description.
- (Optional) Upload a PNG or GIF file as an app icon. If no icon is uploaded, the system will generate one using the first two letters of the app name.
Click Continue.

2. Configure SAML settings

On the Google Identity Provider Details page, enter the following values:

Property	Value
ACS URL	Enter: `https://api-dashboardv2.socure.com/saml2/SSO`
Entity ID	Enter one of the following: Sandbox environment: `https://riskos.sandbox.socure.com/saml2/socure_public_account_id` Production environment: `https://riskos.socure.com/saml2/socure_public_account_id`

Property

Value

ACS URL

Enter: https://api-dashboardv2.socure.com/saml2/SSO

Entity ID

Enter one of the following:

Sandbox environment: https://riskos.sandbox.socure.com/saml2/socure_public_account_id
Production environment: https://riskos.socure.com/saml2/socure_public_account_id

3. Configure SAML attribute statements

When setting up attribute statements, ensure the following attributes are configured:

Name	Name Format	Value	Required?
`urn:oid:2.5.4.42`	Unspecified	`user.firstName`	Yes
`urn:oid:2.5.4.4`	Unspecified	`user.lastName`	Yes
`urn:oid:2.5.4.20`	Unspecified	`user.phoneNumber`	Yes
`urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress`	Unspecified	`user.email`	Yes
`https://dashboard.socure.com/attributes/role`	URI Reference	`String.join(",", appuser.RoleName)`	Optional

If you want to manage what role(s) a user should have when they access RiskOS, you will need to add a new custom attribute. Fill out the details of the new custom attribute as follows:

Data type: string array
Display Name: https://dashboard.socure.com/attributes/role
Variable Name: RoleName
Enum: Checked
Attribute Members:
Display name is flexible and can be defined as you prefer, however the value has to match a valid RiskOS™ system-defined role name.

The following table lists the valid system-defined role names available in RiskOS™:

Example Display Name	Value
Admin	administrator
Acc Owner	account owner
Dev	developer
Fraud Analyst	fraud analyst
Compliance Analyst	compliance analyst
Compliance Officer	compliance officer
Compliance Supervisor	compliance supervisor

📘
Note:
In future releases, RiskOS™ will support custom role names.

4. Enable the SAML App in Google Workspace

Once the SAML App integration is created, enable access for users:

From the Admin Console Home Page, go to Apps > Web and mobile apps.
Select your Socure SSO Integration app.
Click User access, then select On for everyone.
Click Save.

5. Send the SAML Metadata to Socure

After setting up the SAML App integration, click Download metadata to download the SAML metadata file and securely share it with Socure.

Do not copy and paste just the X.509 certificate from the SAML Setup Instructions page. Socure requires the full SAML metadata file (XML format), which includes your entity ID, endpoints, and certificates. Be sure to download and share the complete metadata file.

📘
Important: Customers must provide two separate metadata files to Socure:

One for the RiskOS™ Sandbox environment

One for the RiskOS™ Production environment

After receiving your SAML metadata file, your Technical Account Manager will confirm when SAML is enabled for your account.

6. Test the integration

To test the SAML integration, go to the IdP Admin Console, create a user, assign Socure's RiskOS™ app to the user and assign role(s) via the custom RoleName SAML attribute. When the user launches the RiskOS™ app from the IdP dashboard, the following occurs:

The Users tab on the Users and Roles page in RiskOS™ is populated with the user's name, email address, and phone number.
The user is assigned the role(s) specified in the RoleName custom SAML attribute. If role(s) is not assigned, the system will default to assigning Analyst role to the user.

7. Assign users to RiskOS™

If you are planning to manage role assignment to users and you have configured the custom SAML attribute for RoleName, you can assign role(s) to the user when assigning the application. If a role is not assigned, the system will default to assigning Analyst role to the user.

📘
Note:
RiskOS™can have only 1 user assigned as Account Owner.
A role assigned to user is applicable in both Sandbox and Production. That is, if you assign a Developer role to a user, the user will have Developer role in both RiskOS Sandbox and RiskOS Production. In early 2026, we will be enhancing role-based access management to allow customers to assign roles by environment (e.g. assign [email protected] Administrator role only in Sandbox and assign only Developer role in Production).

📘
Note:
Users are required to re-authenticate every 12 hours by default; however, you can specify a shorter duration using the maxAuthenticationAge parameter for further security hardening.