Skip to main content

SAML Integration

This guide covers SAML SSO between Bicycle and your identity provider (IdP). The same pattern works with major providers including Okta, Google Workspace, and Microsoft Entra ID (Azure AD).

Provider-specific walkthroughs:

Overview

Setup has two parts:

  1. Identity Provider (IdP) configuration — groups, SAML app, access
  2. Bicycle platform configuration — metadata / artefacts, domain, role mapping

Part 1: Identity Provider configuration

Step 1: Create user groups

Bicycle supports three roles: Viewer, Editor, and Admin. Create matching groups in your IdP so users get the right Bicycle role from group membership.

  1. Open your IdP admin dashboard.
  2. Create three groups, for example:
    • BicycleViewers — Viewer
    • BicycleEditors — Editor
    • BicycleAdmins — Admin
tip

Prefix group names with Bicycle or bicycle- so they are easy to find and manage.

  1. Assign the initial set of users to the appropriate groups.

Step 2: Create the SAML application

  1. In your IdP admin dashboard, open application / SSO integrations.
  2. Create a new SAML 2.0 application.
  3. Download the IdP metadata file (you will upload it in Bicycle, or paste the equivalent fields).
  4. Configure the service provider settings:
SettingValue
ACS URL / SSO URLhttps://app.bicycle.ai/api-proxy/api/tenants/auth/login/saml/callback
SP Entity IDhttps://app.bicycle.ai
  1. Configure SAML attributes:
SettingValue
Name ID formatEMAIL
Name ID valueUser's primary email
Group attributeName: groups — include the Bicycle* groups from Step 1
note

Use the Entity ID and ACS URL your Bicycle contact confirms if your environment differs from the defaults above.

Step 3: Configure application access

Enable access to the SAML application using one of:

  • Option A: Enable for all users (Everyone)
  • Option B: Enable only for the three Bicycle groups from Step 1

Part 2: Bicycle platform configuration

  1. Sign in to Bicycle as a tenant administrator.
  2. Open Admin → Authentication (Identity Provisioning / SAML SSO).
  3. Enable SAML SSO.
  4. Provide IdP details — either upload the IdP metadata file, or enter:
FieldSource
Entry Point (Login URL)IdP SSO URL
IssuerIdP entity ID
Callback URLBicycle ACS URL (usually pre-filled)
CertificateIdP signing certificate (Base64 / PEM)
Email domainYour organization email domain
  1. Map IdP groups to Bicycle roles:
Bicycle roleExample IdP group
AdminBicycleAdmins
EditorBicycleEditors
ViewerBicycleViewers
  1. Save the configuration.

Example SAML SSO configuration in Bicycle Admin

Login flows

After SSO is enabled, users can sign in via:

FlowHow users start
Tenant loginhttps://app.bicycle.ai/{tenant}/login → choose SSO
Global loginhttps://app.bicycle.ai/account/login → choose SSO
IdP-initiatedLaunch Bicycle from your IdP app catalog / My Apps

Bicycle sign-in page with OTP, Password, and SSO options

User management

To grant additional users access after SAML is live:

  1. Add the user to the appropriate Bicycle* group in your IdP.
  2. Confirm they can access the Bicycle SAML application.
  3. Have them sign in once so Bicycle creates or updates their account.

Troubleshooting

If users cannot sign in:

  • Confirm they are in the correct Bicycle group
  • Confirm they have access to the Bicycle SAML application
  • Confirm their email domain matches the domain configured in Bicycle
  • Review IdP authentication logs for errors

Support

For additional help: