Native Enterprise SSO & SCIM Provisioning (SAML, Entra, Okta, Auth0)
Plug-and-play SSO and user provisioning for IT teams, without custom JWT setup.
Covers:
SAML 2.0 SSO with Microsoft Entra ID, Okta, Auth0, Google Workspace, and other major IdPs
SCIM Directory Sync to auto-provision, update, and deactivate users when they join, change roles, or leave (full Joiner / Mover / Leaver lifecycle)
IdP group to role mapping (e.g. Entra AD groups → Manager, Contributor, custom roles), so role changes flow in automatically
Works with public portals, so internal team SSO doesn't require making your roadmap private
- Post type
- 💡 New feature
Log in to comment and vote
Comments5
Jun 25
PinnedHey everyone!
Enterprise SSO and Directory Sync is now live and ready for use!
It’s currently feature-gated, so if anyone wants access to this, please reach out to us in the live chat and we’ll enable it for you.
Lindo George
Apr 30
•Merged request
•1 vote
Entra ID (Azure AD) SSO for Public organization team members
I want to be able to use the native Entra ID (Azure AD) SSO integration for my internal team members even when my organization is set to 'Public'.
Currently, this option only appears when the organization is 'Private', but we need our roadmap to remain publicly accessible to external users while enforcing SSO for our internal staff.
juba.saadi
Apr 30
•Merged request
•2 votes
Native Auth0 / Okta integration for SSO
Enable Featurebase to natively integrate with Auth0 as a B2B IAM solution, allowing customers to easily connect their existing authentication systems without needing to handle JWT generation manually.
Bruno from Featurebase
Apr 30
•Merged request
•6 votes
SAML 2.0 support
Support SAML SSO for larger companies.
inlumi Infrastructure Support
Apr 30
•Merged request
•2 votes
[SSO Team Member roles] Programmatic Assignment of Team Member Roles via SSO/API
I would like to be able to assign specific team member roles (e.g., Manager, Contributor, custom roles) programmatically via the JWT payload during SSO login or through an API.
Currently, the "type": "admin" field in the JWT payload only differentiates team members from end-users, and specific roles must be set manually in the GUI.
This feature would be very useful for organizations using Azure AD groups or similar systems to manage user roles.