How to set up SAML 2.0 with OptiSigns and Google Workspace

With Pro Plus and Enterprise plan, you can configure SAML 2.0 with OptiSigns via Google Workspace. The Google Workspace will be acting as the IDP (Identify Provider), and OptiSigns will be working as the SP(Service Provider).

Set up OptiSigns & Google Workspace:

First you need to do some set up in OptiSigns:

If you don't have a sub domain yet, you can set up one by going to:

Fill in subdomain field and click Activate. After that you can use this sub domain for "
You can also map your own domain like by following this article.

This will be the URL that you can share with your users so they can log in to use the app, once integration has set up. In our example we will use


Next go to SAML Single Sign On setting page:

Click Enable SAML SSO.

The settings are:

  • Enable Username & Password login: Allow users to also log in with username/password. It’s recommended to disable once integration is all done. As Admin/Owner, it's recommended that you keep at least 1 account with password log in, in case there's issues, you can always log back in from to reconfigure.
  • Enable User Creation: If users are authenticated, but do not exist in OptiSigns, they will be created in OptiSigns. You should enable this, because you likely already assign/approve users/groups to use OptiSigns, unless for some reason you want to be very strict and want to review roles of users before they can start using OptiSigns.
  • Enable User Override: Every time a user logs in, if their group assignment have changed on SAML, OptiSigns will update, override new profile settings.
  • Note the "Single Sign On URL" and "Audience URI (SP Entity ID) URL", you will need this to use in Google Workspace later.


Next, add OptiSigns as an App in your Google Workspace admin portal:

Log in to your Google Workspace portal as admin -> Apps -> Web and mobile apps

Click Add app -> Add custom SAML app mceclip0.png

In the popup window, enter OptiSigns as the name of the app, you can upload the app icon here as well. Then click continue.


The next page will provide the IDP data. Get these 2 highlighted information then click continue, these need to be maintained in the OptiSigns SAML SSO settings later.

Next page will be the SP information, this is where you should provide the Single Sign On URL, and SP Entity ID you get from your OptiSigns SAML SSO setting.

SP Entity ID from OptiSigns SAML SSO setting should be put under Entity ID.

Single Sign On URL from OptiSigns SAML SSO setting should be put under ACS URL.

Also set the Name ID format to Email.

Then next page is where you maintain the attributes. This step will be explained later in this article. Click Finish, the app is added into the Google Workspace.

After completed the app creation on Google Workspace. You can select the OptiSigns app under the "Web and mobile apps". Click on the OptiSigns app, note the id in the URL, that is the SPID which will be needed.


Go back to your OptiSigns account and maintain above mentioned 3 fields, and save it.

You can get SSO URL, Entity ID and Certificate from your Google Workspace.

  • Put SSO URL from Google Workspace under SAML 2.0 Endpoint (HTTP).
  • Put Entity ID from Google Workspace under Identity Provider Issuer.
  • Put the content from base64 encoded certificate under Public Certificate.

Now your log in portal & integration is all set up.


Assign & map users, groups from Google Workspace to OptiSigns

It's not required, but recommended to create groups of users to be assigned, map to OptiSigns Roles, Teams so they will automatically have the right role & group.

IMPORANT NOTE: If you don't configure this, all users will be assigned User Role & Default Team (screenshot see below)


To configure how OptiSigns should map the user groups to OptiSigns Roles by going to:

Scroll to Advanced Settings and create mapping.
Group Name (can use department from Google Workspace), Role (role in OptiSigns) mapping. 

It's best practice to create group specifically for OptiSigns with name prefix with optisigns- and map to OptiSigns like below:

  • optisigns-admins (SAML group) -> OptiSigns role: Admin
  • optisigns-users (SAML group) -> OptiSigns role: Users
  • optisigns-custom-role (SAML group) -> OptiSigns custom role that you create

How to handle Unmapped users/group:

You can map the "Unmapped users/group" to No Team (Disabled)

This way they will receive an error when trying to log in and will have to reach out to Admins to get  correct teams, roles assigned. This is can be use as safe guard, in case some user accidently got assigned OptiSigns app but not the right groups.


Note that if you map a SAML group to a Team and then delete the team, it will result in new user being mapped to No Team and will have to contact you to be assigned to a team to use the app.


Next, it is time to talk about the attributes mapping. This is the last step when creating the app in Google Workspace.

Currently, OptiSigns support attributes mapping of first name, last name and group. You can define the attribute name in Google Workspace and set it to the same default attributes name used on OptiSigns.

These mappings will pass information to OptiSigns on what's user's Name and Groups.



The "App attributes" are corresponding to OptiSigns

OptiSigns accept firstName, lastName, group by default. Instead of setting the attributes names to the default attributes name used on OptiSigns,  you can also change the attribute name on OptiSigns to match the attribute name you defined on Google Workspace as well.



That's it!

You have configured SAML 2.0 for OptiSigns with Google Workspace.

Now your users can log in using the sub domain that you configured (in this case it was

You can share the URL with your users and they can log in with their SSO credential.


If you have any additional questions or any feedback about OptiSigns, feel free to reach out to our support team at or just submit a ticket here.



Was this article helpful?
0 out of 0 found this helpful



Article is closed for comments.