Multiple customer SSO configurations per Workspace
Allow a Featurebase Workspace to configure and manage multiple customer-facing SSO setups instead of relying on one global SSO login URL and JWT configuration.
This would support companies that have multiple products, brands, portals, or customer identity systems within one Workspace.
Each SSO setup should be able to have:
Its own login URL and JWT verification configuration
Routing rules that associate it with specific brands, custom domains, Messengers, Help Centers, or public portals
Support for returning the customer to the correct surface after authentication
Featurebase should resolve the appropriate SSO setup from the active brand or domain while keeping the customer data and product configuration centrally managed in one Workspace.
This request concerns customer-facing SSO and is separate from Enterprise SSO used by teammates to access the Featurebase dashboard.
- Post type
- 💡 New feature
Log in to comment and vote
Comments1
Alvar
Aug 12
Our specific use case is that we operate two different brands in the same Featurebase Workspace, and each brand has its own customer SSO system.
Customers visiting Brand A's domain, Messenger, or Help Center should authenticate through Brand A's SSO, while customers visiting Brand B should authenticate through Brand B's SSO. After login, they should be returned to the correct branded surface.
Each brand should also continue using its associated Help Center and content without requiring us to duplicate that content just to support a separate login flow.