Single Sign-On (SSO)

Understanding SSO options in Frill

Frill supports Single Sign-On (SSO) to simplify authentication for your team and end-users. You can choose from multiple authentication methods depending on your needs and infrastructure.

SSO for your team

Team SSO controls how your colleagues access the Frill admin dashboard. Available on all paid plans, it supports:

  • SAML 2.0 — Enterprise standard protocol, ideal for Okta and similar identity providers

  • OIDC/OAuth 2.0 — Modern authentication, used by Microsoft Entra ID (formerly Azure AD)

  • Token-based (JWT) — Custom authentication where your server generates signed tokens

When enabled, team members sign in through your identity provider instead of using Frill passwords.

SSO for end-users

Widget SSO identifies customers viewing your embedded Ideas boards, Roadmaps, or Announcements. It uses JWT tokens to:

  • Personalize content based on user attributes

  • Track votes and comments by authenticated users

  • Control access to private boards

  • Prevent duplicate accounts

End-users never see a login prompt—your application passes authentication tokens directly to Frill widgets.

Team SSO and widget SSO work independently. You can enable one, both, or neither depending on your needs.

Choosing the right option

Use SAML or OIDC if you manage team access through an identity provider like Okta or Microsoft Entra ID. Use token-based authentication if you want full control over the authentication flow or need to identify end-users in widgets.

For implementation details and code examples, visit the SSO developer documentation.

Was this helpful?