May 2026 Summaries

PropelAuth has introduced two new roles, Developer and Customer Management, to its dashboard to provide targeted access for users based on their job requirements without unnecessary permissions. The Developer role is designed for engineers who need to manage project configurations, such as updating login settings and configuring API keys, but are restricted from altering user or organizational data. In contrast, the Customer Management role is tailored for support and operations teams who handle user and organizational interactions, including account management and SSO configurations, but lack access to project configurations. These new roles complement existing roles like Owner, Admin, Member, and ReadOnly, offering a total of six role options for flexible and secure access management. The new roles are now available for use and can be assigned through the organization's dashboard settings.

Choosing the right authentication platform for a B2B SaaS product is crucial, as it impacts long-term operational efficiency and customer satisfaction. B2B authentication differs from consumer login because it involves modeling organizations, managing roles that vary by organization, and providing enterprise customers with self-service SSO and provisioning. The text evaluates six authentication platforms—PropelAuth, WorkOS, Auth0, Clerk, Kinde, and Descope—each with unique approaches to handling B2B-specific requirements like multi-tenancy, roles, permissions, and enterprise SSO. PropelAuth stands out as the most comprehensive B2B-native option, featuring built-in support for organizations, roles, enterprise SSO, and SCIM, making it particularly suitable for multi-tenant applications sold to businesses. Conversely, platforms like WorkOS and Auth0 offer robust enterprise features but may require additional configuration for a complete B2B solution. Clerk, Kinde, and Descope provide unique features such as strong developer support, combined billing and feature management, and a no-code flow builder, respectively, but each comes with its own trade-offs in terms of depth and integration. For B2B SaaS companies, the choice of platform should consider not only the technical capabilities but also how these align with the company's growth strategy and customer needs.

System for Cross-domain Identity Management (SCIM) is an open standard that streamlines user provisioning and deprovisioning between identity providers (IdPs) like Okta and Microsoft Entra ID, and third-party applications, automating account creation, updates, and removal to reduce IT overhead and maintain synchronized user data. Unlike SAML and OIDC, which handle user authentication, SCIM focuses on provisioning user accounts and operates continuously in the background. PropelAuth integrates SCIM into its organization model, allowing B2B SaaS products to meet enterprise security requirements without code changes, facilitating seamless user management through a configuration process that enables customers to self-configure SCIM using guided setup flows. SCIM becomes crucial for onboarding large numbers of users, ensuring compliance in high-security environments, and maintaining central management of IT-managed SaaS stacks, with PropelAuth supporting all major identity providers and ensuring existing app functionalities remain unaffected by SCIM integration.

PropelAuth has introduced granular permission scopes for backend API keys, allowing precise control over what each key can do within an environment. This means that instead of using a single, all-encompassing credential, users can issue narrowly scoped keys tailored to the specific permissions needed for each service or integration, such as Read Users for a data pipeline or Create Users for an onboarding service. This approach enhances security by following the principle of least privilege, reducing the risk from compromised keys, and making auditing easier by clearly defining each key's access. This feature is particularly significant for teams using AI agents in their B2B SaaS products, as it allows these agents to interact with authentication infrastructure without exceeding their intended capabilities. The new system categorizes permissions into six areas, including Users, Organizations, Authentication, and others, providing flexible control over access. The integration of MCP authentication support adds an additional layer of security, ensuring that AI agents can only perform actions that are explicitly permitted by their associated keys. The process for creating a scoped backend API key involves selecting an environment in the PropelAuth dashboard, choosing a key type, and customizing permissions according to the key's intended use.