SAML Single Sign-on Setup

Whimsical supports Single Sign-on (SSO) based on the SAML spec for customers on our Organization Plan

SAML IdP Providers We Support

Please see the end of the article for screenshots that help you walk through setup for each provider.

  • OKTA (we also support SCIM Provisioning with Okta)
  • OneLogin
  • Ping Identity
  • Google G Suite
  • JumpCloud
  • Microsoft/Azure Active Directory
  • Shibboleth
  • Other - if you use another SAML IdP that isn't listed here (like Auth0), we should still be able to support it. Select Other from the drop-down to upload your XML. If this gives you any trouble at all, please reach out to Support for help via email or in the app!

Instructions for setting up SAML SSO in Whimsical

To begin setup within Whimsical, navigate to your Workspace Settings via this link or via the drop-down in the upper left of your screen.

We've tried to make the SAML SSO setup as simple as possible, and the SAML setup screen shows all the variables you will need to make SAML work for your workspace.

However, the naming of some SAML attributes varies depending on the Identity Provider (IdP), which is why this page is needed 🙂

There are some attributes that are the same for all IdP's:

Whimsical uses the e-mail address of the SAML user to identify them on Whimsical. This will come up with configuration options like "Name ID Format" or "Name ID". When in doubt, try to choose the option that will return the e-mail of the user.

Important note before we proceed:

Whimsical supports JIT (Just-in-time) account provisioning. That means that Whimsical will create an account for a user authenticating via SAML if necessary.

When you're setting up SAML in Whimsical, you can choose the default user role. You can choose between:

  • Editors - paid role with full ability to create & edit
  • Viewers - free role with read & comment only limited permissions

If you choose the default role as Editor, this may result in unexpected charges if a lot of new members sign up via SAML. Workspace admins can always change the member role from Editor to Viewer or Viewer to Editor later on:

Existing Accounts

If you already have a Whimsical account created before enabling SAML for a Workspace, you can continue using it with both means of authentication:

  • Log into your existing account, using the existing login method

  • Then log in using your SAML SSO provider

  • The e-mail address returned by the SAML IdP should now be added to your existing account, and you should be able to login with both authentication methods.


Workspace admin may choose to enforce SAML-only authentication method for a Workspace, which means that a user will still be able to log into their account using other login methods, but will require using SAML SSO before accessing the particular Workspace with the SAML enforced.

Tips for disconnecting SAML SSO in Whimsical

Sometimes, it may be necessary to switch off SSO, or to switch SAML IdP. Here are a few tips to make that as smooth as possible.

Before you do anything, make sure that you disable the "Require SAML to log in" option in the Whimsical SAML settings. Then, switch off the SAML connection.

Disabling SAML shouldn't affect your workspace in a bad way and folks will still be able to continue using Whimsical. However, those who have only created their accounts via SAML will be asked to create a password the first time they'll try to log in after SAML is disabled.

If you set up SAML again with a different provider, you should follow the steps above as if it was the first time connecting.

Examples of how to set up some specific SAML SSO providers:


You can find Whimsical in Okta's Application Network, and see a setup walkthrough here.

G Suite

Attribute mapping in G Suite does not happen automatically, but you should manually map the first name and last name attributes so that those get sent to Whimsical:

This is what the Whimsical SAML app's attribute mapping in GSuite should look like


Unfortunately, profile photo mapping is not supported.

Azure Active Directory

Use the pre-built Whimsical integration in the Azure Active Directory Marketplace for the easiest setup experience!

If the Integration doesn't work for you, or you want to set up things manually, here are a few gotchas to keep in mind: 

  • The EntityID and User Identifier format is still the same as before and listed at the top of this page

  • The Reply URL (ACS URL) can be found in your Workspace Settings

  • The User Attributes have to be WITHOUT Namespace, and the capitalization is important.

Example of a complete, working SAML setup:

Listing of all claims/attributes:

Example on how to remove the Namespace URI for a claim:


While we don't have specific integration support for Auth0 at the moment, we have successfully setup Auth0 integrations with this minimal setup:

Replace the Application Callback URL with the ACS URL provided in Whimsical, and configure the rest of the values like this.

<code>{<br>  "mappings": {<br>    "given_name": "givenName",<br>    "family_name": "LastName",<br>    "picture": "PhotoURL"<br>  },<br>  "nameIdentifierFormat": "urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress",<br>  "nameIdentifierProbes": [<br>    ""<br>  ]<br>}

There may of course be other values in your configs, but these are the ones that matter to the Whimsical SAML integration.

Also please note that you may have setup Auth0 differently, and may have different names for values inside of Auth0. But these are the mappings, formats and probes that work for an out-of-the-box setup.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.