Docs
Single sign-on
Let your team sign in to Flipbird with Microsoft Entra ID, Google Workspace, Okta or any SAML 2.0 identity provider.
An Owner sets up single sign-on under Settings, Sign-in, when the plan includes it. Run a test sign-in before you require it: until then everyone can still sign in with a code sent to their email.
Choose your identity provider
- Microsoft Entra IDCreate a non-gallery enterprise application in your Microsoft Entra tenant, point its SAML settings at this workspace, and give Flipbird the application's federation metadata URL.
- Google WorkspaceAdd a custom SAML app in the Google Admin console, point it at this workspace, map the email and name attributes, turn it on for your users, and upload Google's IdP metadata file to Flipbird.
- OktaCreate a SAML 2.0 app integration in the Okta Admin Console, point it at this workspace, then add the email and name attribute statements on its Sign On tab, assign it, and give Flipbird its metadata URL.
- Other SAML 2.0 identity providerAny identity provider that speaks SAML 2.0 works if it can sign assertions with RSA-SHA256 and post them to this workspace. Set it up with the values below and give Flipbird its metadata.
The values your provider asks for
Each guide says where these go. They are shown here for a workspace at your-workspace; your own are under Settings, Sign-in in your workspace.
Entity ID
https://your-workspace.flipbird.io/api/sso/metadata Assertion Consumer Service (ACS) URL
https://your-workspace.flipbird.io/api/sso/acs Metadata URL
https://your-workspace.flipbird.io/api/sso/metadata Sign-in URL
https://your-workspace.flipbird.io/api/sso/login Name ID format
urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress