# Descope > Identity and access management (IAM) platform that helps organizations add authentication, access control, and identity management to their customer apps, partner apps, AI agents, and MCP servers. Descope provides a no / low code, developer-first CIAM platform that helps organizations implement frictionless, secure identity journeys. The platform supports all modern authentication methods including passkeys, magic links, social logins, single sign-on (SSO), authenticator apps, Google One Tap, one-time passcodes (OTP), and traditional passwords. Organizations choose Descope because its drag & drop user journey workflows and multi-tenant, augmentation-friendly architecture help them implement and modify authentication journeys quickly without touching their codebase. Descope offers SDKs for all major frameworks and programming languages, making integration seamless regardless of your tech stack. Key Descope use cases include: - B2C CIAM: Consumer apps can simplify onboarding, improve conversions, and enhance account security with capabilities like passwordless auth, anonymous user tracking, A/B testing, native mobile auth, adaptive MFA, step-up authentication, and integrations with ecommerce platforms like Shopify, WordPress, and WooCommerce. - B2B CIAM: Business apps can meet enterprise requirements around SSO, SCIM, delegated administration, fine-grained authorization, and audit trails. - Augmentation: Organizations can add MFA, SSO, and MCP / AI agent authentication without changing their existing identity infrastructure. - Identity federation: Organizations with fragmented, hierarchical identity systems can unify authentication across multiple applications and identity providers while catering to each business unit's unique branding, auth, and access control requirements. - Fraud / account takeover prevention: Organizations facing credential-based attacks can add risk-based, phishing-resistant MFA with a variety of native risk factors as well as integrations with third-party connectors like reCAPTCHA, Forter, and Fingerprint. - AI agent authentication: Organizations building AI agents can connect them with third-party tools while offloading token management and storage. - MCP server authorization: Organizations building MCP servers can secure them with OAuth, consent management, Dynamic Client Registration (DCR) hardening controls, scope-based access control, and policy-based governance. ## Learning Center ### [What Is DPoP (Demonstrating Proof of Possession)?](https://www.descope.com/learn/post/dpop) *Full content: [https://www.descope.com/learn/post/dpop.md](https://www.descope.com/learn/post/dpop.md)* Demonstrating Proof of Possession (DPoP) is an [OAuth 2.0]() extension that binds access and refresh tokens to a key pair held by the client that requested them. Defined in [RFC 9449](), DPoP limits what a token is worth to anyone who copies it. A standard bearer token works for whoever presents it, but a DPoP-bound token only works when the request also carries a fresh signature from the client’s private key, which always stays with the client. Short lifetimes keep tokens from working for longer than needed, and minimal scopes limit their reach. DPoP narrows who can use them. That makes it especially relevant to AI agents, which often hold tokens for long-running tasks and can expose them through tool calls, tool results, and logs. ## At a glance - DPoP binds an OAuth access token to the public key of the client that requested it, recorded in the token as a key thumbprint. - To use a DPoP-bound token, the client sends a newly signed proof with every request, tied to that request’s HTTP method and URL. - A copied DPoP-bound token can’t be used without the client’s private key, while a bearer token works for anyone who holds it. - For AI agents, DPoP lets the signing key stay outside the model’s context, so a token that leaks through a tool call, tool result, or log can’t be used. - DPoP works at the application layer with ordinary key pairs, while mTLS-bound tokens depend on client certificates and the TLS connection. ## DPoP vs. bearer tokens: what is proof of possession? By default, OAuth access tokens are bearer tokens. Possession, meaning having a copy of the token’s value, is the only requirement for their use. As a result, a token copied from a log, a compromised device, or an [intercepted request]() can be used by anyone until it expires. Setting tight expiration and [refresh token rotation]() windows can limit its blast radius, but they don’t change *who *can use the token. **For how bearer tokens relate to the JSON Web Token (JWT) format, see **[**JWT vs. Bearer Token**]()**.** Proof-of-possession tokens add a second requirement: along with the token itself, the presenter must demonstrate control of a key the token is bound to. OAuth has two standard methods for showing this, DPoP and [mTLS certificate-bound tokens](). For both methods, the “possession” part in “proof of possession” ends up meaning something much narrower than “possessing” a bearer token. The presenter must prove they possess the key (which is never sent, but used to sign the proof), so a copy of what is sent (the token and a single-use proof) won’t satisfy the requirement. ## How DPoP works A DPoP exchange involves three parties: the client, the authorization server that issues tokens, and the resource server that accepts them. ![How DPoP Works Diagram]() 1. The client generates an asymmetric key pair and keeps the private key. 2. The client requests a token from the authorization server and includes a DPoP proof signed with its private key. 3. The authorization server verifies the proof and records a thumbprint of the client’s public key in the token. 4. The authorization server returns an access token bound to that key. 5. Before calling the resource server, the client signs a new proof. 6. The client sends the access token and the new proof together. 7. The resource server verifies the proof and confirms that its key matches the one the token is bound to. 8. If both checks pass, the resource server returns the protected resource. ### What is a DPoP proof? A DPoP proof is a short [JWT]() the client creates and signs with its private key. The decoded header of a proof for a token request looks like this: ~~~javascript { "typ": "dpop+jwt", "alg": "ES256", "jwk": { "kty": "EC", "crv": "P-256", "x": "l8tFrhx-34tV3hRICRDY9zCkDlpBhF42UQUfWVAWBFs", "y": "9VE4jf_Ok_o64zbTTlcuNJajHmt6v9TDVrU0CdvGRDA" } } ~~~ The header carries `typ` (marking the JWT as a DPoP proof), an asymmetric signing algorithm in `alg`, and the client’s public key in `jwk`, written in the [JSON Web Key format](). Its payload looks like this: ~~~javascript { "jti": "-BwC3ESc6acc2lTc", "htm": "POST", "htu": "https://auth.example.com/token", "iat": 1793390400 } ~~~ The [payload’s claims]() carry a unique identifier in `jti`, the HTTP method in `htm`, the target in `htu`, and the creation time in `iat`. Signing the proof shows that the client holds the private key, and the method and URL tie that proof to a single request.  ### Getting a bound token The client sends the proof in a `DPoP` header with its token request. In the authorization code flow, that request may also carry a [Proof Key for Code Exchange (PKCE)]() verifier: PKCE proves the client redeeming the code is the one that started the flow, and the DPoP proof binds the tokens the request returns to the client’s key. The authorization server checks the proof’s signature against the embedded public key. It then computes a thumbprint of that key and records it in the issued [access token]() as the `jkt` member of a `cnf` (confirmation) claim: ~~~javascript { "sub": "user_123", "scope": "orders:read", "cnf": { "jkt": "0ZcOCORZNYy-DWpqq30jZyJGHTN0d2HglBV3uiguA4I" } } ~~~ Every OAuth token response includes a `token_type`, which is ordinarily `Bearer`. For a bound token, the authorization server sets it to `DPoP`, which tells the client the binding took effect and that the token must be presented with DPoP proofs. An authorization server that doesn’t support DPoP ignores the proof and returns an ordinary bearer token.  ### Using the token Each request to a protected resource carries the token in the `Authorization` header under the `DPoP` scheme, in place of `Bearer`, along with a new proof: ~~~html GET /orders HTTP/1.1 Host: api.example.com Authorization: DPoP eyJhbGciOiJFUzI1NiIsImtpZCI6... DPoP: eyJ0eXAiOiJkcG9wK2p3dCIsImFsZyI6IkVTMjU2Ii... ~~~ This proof also includes `ath`, a hash of the access token, which ties the proof to that specific token. The resource server verifies the proof by checking that: 1. The signature matches the proof’s public key. 2. The key’s thumbprint matches the token’s `cnf.jkt`. 3. The method and URL match the request. 4. The proof is recent. 5. Its `jti` hasn’t been used before. 6. The `ath` value matches a hash of the access token presented. Because the client signs its own proofs, anything with brief access to the private key could sign proofs ahead of time for later use. To prevent that, a server can issue a [nonce]() (“number used once”) in a `DPoP-Nonce` response header and require the client’s next proof to include it. This means a proof can’t be created before the server issues the nonce. ### The key pair Because the private key is what makes a bound token usable, protecting a bound token comes down to keeping the key inside the client. Browser apps are common DPoP clients, where the Web Crypto API can generate a private key marked non-extractable. Scripts can sign with it but can’t export it. Each token stays bound to the key it was issued for, and the binding can’t be moved. A public client, such as a browser or mobile app that can’t keep a client secret, has its [refresh token]() bound to the same key. That means losing the key requires running a new authorization flow. A confidential client’s refresh token isn’t bound because the client already authenticates itself at the token endpoint, so it can move to a new key at refresh.  ## Why DPoP matters for AI agents AI agents typically use OAuth tokens to reach APIs and MCP servers, either on a user’s behalf or as themselves. An agent working through a long task may hold several tokens at once and present each of them many times. Depending on how the agent is built, those tokens can also end up in tool call arguments, tool results, and the traces and logs that document them. For bearer tokens, this significantly widens the ways in which they can leak. An agent that follows instructions hidden in a tool description or a fetched document (as in [tool poisoning attacks]()) can be steered into repeating the token in its context. If that’s a bearer token, repeating it hands over access.  DPoP separates the token from the ability to use it. The proof is signed by the code that sends the HTTP request, so the private key can stay out of the model’s context. If a token leaks, it leaks without the key that makes it usable, and a resource server that checks for DPoP refuses it. When an agent uses [OAuth token exchange]() to get a narrower token for a downstream service, it can send a DPoP proof with the request. This binds the new token to the agent’s own key, so each token in the chain works only for the party holding it. ## DPoP compared with bearer and mTLS-bound tokens | Dimension | Bearer token | DPoP-bound token | mTLS certificate-bound token | | --- | --- | --- | --- | | Token is bound to | Nothing | The client’s public key | The client’s TLS certificate | | Proof sent with each request | None | A signed JWT in the DPoP header | The TLS handshake using the client certificate | | A copied token | Works until it expires | Fails without the client’s private key | Fails without the certificate’s private key | | What the client needs | The token | A key pair it generates itself | A certificate and a direct TLS connection to the resource server | Because a DPoP proof travels inside the HTTP request, the binding remains even when TLS terminates at a proxy or load balancer in front of the resource server, which complicates certificate binding. Clients also generate their own keys, without a certificate authority. That makes DPoP practical for browser apps, mobile apps, and AI agents, in scenarios where provisioning client certificates is difficult.  ## DPoP with Descope DPoP covers one part of a wider problem in agentic identity governance: making sure the party presenting a token is the one it was issued to. Neighboring standards mostly cover the things that happen around it. For example, client authentication methods like [SPIFFE](), private_key_jwt, and mTLS prove who a client is when it requests a token. Delegation standards such as OAuth token exchange and [Cross-App Access (XAA)]() carry a user’s access from one app or agent to the next, and the [Personal Agent Protocol (Poppy)]() extends delegated access to consumer websites. DPoP can apply across all of these, keeping each issued token bound to the key of the client that holds it.  Descope supports DPoP in the Agentic Identity Hub, alongside SPIFFE, `private_key_jwt`, and mTLS client authentication. For consumer sites, [Descope Envoy]() makes websites Poppy-compliant, and the [Poppy JavaScript SDK]() handles DPoP proofs and bound tokens for the personal agents that connect to them.  To get started, visit the [Agentic Identity Hub docs]() and sign up for a [Free Forever Descope account]().  ## FAQs about Demonstrating Proof of Possession (DPoP) --- ### [What Is Personal Agent Protocol (Poppy)?](https://www.descope.com/learn/post/personal-agent-protocol) *Full content: [https://www.descope.com/learn/post/personal-agent-protocol.md](https://www.descope.com/learn/post/personal-agent-protocol.md)* Personal Agent Protocol, nicknamed Poppy, is an [open standard]() that gives personal agents their own way in while still acting on behalf of the user. Why “Poppy?” Poppy’s designers and the dev community have agreed the nickname is more distinctive than a conventional acronym (i.e., “PAP”). Developed by Sierra and Meta, Poppy defines how an agent finds out how to work with a business, how it identifies itself, how it gets the user’s approval, and how it interacts with the company’s own AI agent, website, or APIs. This guide covers what Poppy is, how it works, and where it lives in the broader agentic ecosystem. The Poppy pattern will look familiar to anyone who knows [OAuth]() and the [Model Context Protocol (MCP)](), with a session layer and a format for agent-to-agent conversations added on top. ## At a glance - Poppy gives agents an alternative to the password form: the agent identifies itself and works within the access the user approved. - Users decide what access their agent gets, and companies decide what agents can do. - It’s built almost entirely on OAuth, and agents identify themselves the same way MCP clients do. - One session covers the company’s website, its APIs, and conversations with its own AI agent. - Version 1.0 arrived in November 2026. Design partners include OpenAI, Walmart, and United Airlines, and payments, push notifications, and attachments are still open topics. ## What is Poppy, and why does it matter? Poppy (sometimes erroneously referred to as “PAP”) is an open protocol that lets personal agents sign in to a user’s account safely, limiting what they can do there to what the user and the company hosting the account agree to. Poppy fills in the space between the extremes of blocking all agents and letting agents sign in as users. An insurer, for example, could let any agent compare quotes, let a signed-in agent with read access view the user’s policy, and allow coverage changes only for agents the user granted write access to. The user, in turn, could approve read access and nothing more. The reason Poppy is especially meaningful now is the rise of personal agents like Instinct and Meta’s Muse, which allow people to send their AI assistant to book flights, schedule appointments, and shop for car insurance. On most sites, those agents get access in the same way a person would, asking the customer for a password and a one-time code and logging in as that customer. The site sees an ordinary login and has no way to tell the agent from the person it works for. This approach is counter to generally agreed-upon [agent credential best practices](), which favor short-lived, scoped tokens over shared passwords. Before personal agents like Instinct and Muse arrived, much of the thinking assumed businesses would build for agents first, with an MCP server, [UCP]() or ACP support, or a connector for each agent platform. Few B2C businesses can build and maintain all of those, and many have a working login but no public API. Because every Poppy channel is optional, a business can start with its website and existing login (with an OAuth [authorization server]() in front of it) and still give agents an identified, delegated way in. Poppy uses MCP as one of its API types; what it’s positioned to replace is the password form. Adopting it takes work from both agent builders and businesses: - Agent builders add Poppy support to their agents once, and it then works with any company that publishes a discovery document. - Businesses publish a discovery document, connect their existing OAuth authorization server, and choose which channels to open. That means updating their authorization server for Poppy (CIMD clients and, if they choose, DPoP) and verifying the agent’s session header at their APIs, rather than building an MCP server or a connector for each agent platform. Poppy [reached version 1.0]() on November 13, 2026, after five weeks of design partners testing the drafts against real websites, APIs, and agents. Shopify enabled it for every merchant on its platform, Muse now looks for Poppy first on every site it visits, and 60 new design partners (Descope among them) brought the total past 100. Version 1.0 also adds extensions that build on the core protocol without changing it, including a commerce extension co-authored by Shopify that connects Poppy to UCP. ## How Poppy works Nearly every piece of Poppy is an existing OAuth or MCP building block: | **Poppy component** | **Built on** | | --- | --- | | Discovery document | OAuth protected resource and authorization server metadata | | Agent identity | Client ID Metadata Document, as used by MCP | | Session header | A JWT the agent signs for each request | | Account access | OAuth access and refresh tokens, optionally bound to the agent’s key with DPoP | | Direct Sign-In (preferred) | Authorization code flow with PKCE | | Device Sign-In | Device authorization grant | | Mediated Sign-In | A transitional extension grant | | Company APIs | OpenAPI or a remote MCP server | ### Discovery and agent identity A company that supports Poppy publishes a discovery document at `/.well-known/poppy.json` (the standard path agents check first) listing its OAuth issuer, the sign-in types and scopes it offers, and the channels agents can use. The agent confirms the issuer through the domain’s protected resource metadata, and the issuer lists the domain in its own metadata, so one domain can’t claim another company’s issuer. Agents identify themselves the way MCP clients do, with a [Client ID Metadata Document (CIMD)](). The client ID is an HTTPS URL serving the agent’s name, logo, redirect URIs, and public signing keys, so no pre-registration is needed. Companies can still require registration, keep allowlists, and revoke an agent that misuses the protocol. ### Sessions and sign-in Everything an agent does at a company happens in a [session](), so a question asked as a guest and an order change made after sign-in count as one visit. The agent names the session on every request with a `Poppy-Session` header, a JWT it signs itself, so starting a session needs nothing from the company’s authorization server. Sessions start signed out: the company knows which agent is asking and can recognize a returning user through a per-company User ID, but not who that user is. Because the agent gives each user a different ID at every company and never derives it from personal data, companies can’t match records to find a shared customer. When a task needs the user’s account, the user signs in once, through a sign-in type the company offers: - **Direct Sign-In:** The user signs in on the company’s own page and approves the requested access, using the [OAuth authorization code flow with PKCE](). It’s the preferred type. - **Device Sign-In:** The agent shows the user a short code and link, and the user approves on any device, using the [OAuth device authorization grant](). - **Mediated Sign-In:** The agent submits credentials the user gave it. Version 1.0 moved it to a transitional extension for companies that don’t offer Direct or Device Sign-In yet. The user grants scopes the company defines, such as `orders:read` or `orders:write`. The resulting refresh token lets later sessions start signed in until the user signs out or disconnects the agent from their account settings. Companies can bind access tokens to a key the agent holds through [DPoP](), so a copied token is useless on its own. Tokens for an MCP server are restricted to that server, and a company whose MCP server doesn’t accept DPoP issues [bearer tokens]() for it. The same session carries across the company’s website, APIs, and conversations with its AI agent. That means a cart that began in the browser is still there when the agent switches to the API, and access the user approved still applies on that channel. In a conversation, either side (user or company) can [bring in a person](): the user’s personal agent can ask for a human at the company, and the company can request the user by adding a `user_requested` event to the conversation. ### The Poppy flow A typical interaction with Poppy runs through five steps: 1. **Discovery:** The agent fetches the company’s `poppy.json`, finds the issuer through the domain’s protected resource metadata, and confirms that the issuer lists the company’s domain. 2. **Signed-out work:** The agent browses, calls APIs, or messages the company’s agent, signing a `Poppy-Session` header for each request. The first request starts the session. 3. **Sign-in:** When a request needs the user’s account, the company’s response names the scopes it needs, and the user signs in. 4. **Signed-in work:** The agent sends an access token along with the session header, and the company enforces the granted scopes on every channel. 5. **Sign-out:** The agent revokes the refresh token, and the session continues signed out. ![Fig: A Poppy session from discovery through Direct Sign-In and a signed-in request.]() ## Poppy vs. MCP, PACT, and other agent protocols Poppy is one of several recent efforts to standardize how agents identify themselves and act for users, alongside MCP, Decagon’s [PACT](), and Visa’s [Trusted Agent Protocol](). | **Protocol** | **Built on** | **Focus** | | --- | --- | --- | | Poppy (Sierra and Meta) | OAuth, CIMD, DPoP, OpenAPI, and MCP | Discovery, sign-in, and one session across a company’s website, APIs, and agent | | MCP | JSON-RPC, with OAuth-based authorization | How an agent calls tools and data on a server | | PACT (Decagon) | Agent2Agent (A2A) and OAuth 2.0 | Proving whom an agent represents and what the customer authorized, through the business’s agent | | Trusted Agent Protocol (Visa) | HTTP Message Signatures, aligned with Web Bot Auth | Cryptographic agent identity so merchants can tell legitimate agents from bots | Poppy and MCP work at different layers: - MCP defines how an agent calls a company’s tools and data - Poppy lists a remote MCP server as one of two API types a company can offer A company’s MCP server can accept Poppy session headers and access tokens, while MCP clients that don’t support Poppy can still sign in through [MCP’s own authorization flow](). PACT overlaps with Poppy the most because both use OAuth to show a business who a personal agent represents and what the customer approved. PACT, however, routes that exchange through the business’s own agent over [Google’s Agent2Agent (A2A) protocol](). Poppy is more comprehensive, covering the company’s website and APIs. Visa, which leads the Trusted Agent Protocol, is also a Poppy design partner. Checkout is where Poppy’s coverage ends, for now. Commerce protocols like UCP and [ACP]() handle checkout and payment, while Poppy’s spec lists payments, including how Poppy would work with existing payment protocols, as an [open (and unresolved) topic](). ## Keeping up with agent protocols New agent protocols are arriving every few weeks, but each one still needs an authorization server that can recognize the agent, sign in the customer, and issue a scoped, delegated token. Descope’s [Agentic Identity Hub]() provides that layer, with support for CIMD, the device authorization flow, and [CIBA](), so teams can keep up with new agents and protocols without building the scaffolding themselves. Poppy has two sides to implement. For companies, [Descope Envoy]() makes a site Poppy compliant without building an authorization server, and runs alongside the existing login whether or not it’s on Descope. For agent builders, the open source [Poppy JavaScript SDK]() handles discovery, sessions, sign-in, and DPoP-bound API calls in a zero-dependency TypeScript package. [The B2C Developer’s Guide to Delegated Agent Access]() shows the pattern on a typical B2C site. To get started, create a [Free Forever account]() or join [AuthTown](), Descope’s developer community, to talk through MCP, Poppy and whatever comes next. ## FAQs about Poppy --- ### [Enterprise SSO: A Comprehensive Guide ](https://www.descope.com/learn/post/enterprise-sso) *Full content: [https://www.descope.com/learn/post/enterprise-sso.md](https://www.descope.com/learn/post/enterprise-sso.md)* Employees at large organizations work across many apps, and every separate login is another password to remember, reset, and protect. Enterprise [single sign-on]() (SSO) replaces those logins with one: employees authenticate once through their organization’s identity provider (IdP), and every connected app trusts that sign-in. That gives IT and security teams one place to enforce multi-factor authentication (MFA) and one place to grant or remove access. ![Let's spill the tea on SSO]() ## At a glance - Enterprise SSO lets employees sign in once through their organization’s identity provider and open approved apps without logging in again. - The app hands the login to the identity provider, which authenticates the user and returns a SAML assertion or an OpenID Connect (OIDC) ID token. - A complete enterprise SSO setup includes SAML and OIDC support, directory sync through SCIM, MFA enforced at the identity provider, and admin tools for configuring and testing connections. - Enterprise IT teams require SSO from SaaS vendors because it gives them one security policy and one place to grant and revoke access. - Because SSO centralizes login, the identity provider account becomes a high-value target, so organizations typically pair SSO with phishing-resistant MFA. ## Understanding enterprise SSO Enterprise SSO is a user authentication process that allows employees to access multiple applications or systems with a single set of credentials. What sets it apart from general SSO is its fit for large organizations with complex IT environments. As a central authentication point, it covers enterprise resources whether they’re cloud-based, on-premises, or hybrid. ### The importance of SSO in large organizations In large organizations with diverse departments like finance, marketing, and engineering, employees work across many software tools. Without SSO, each tool typically requires its own credentials, which creates several problems: - **Fragmented access control:** Employees have to remember multiple sets of credentials, which drives frequent password reset requests to IT support.- **Inconsistent security measures:** Some apps might require complex passwords changed monthly, while others may lack stringent policies. Attackers only need the weakest one.- **Decreased productivity:** Logging in to system after system interrupts work throughout the day. Enterprise SSO addresses all three by moving authentication to one place, under one set of policies. ### Example of enterprise SSO Consider Alex, a project manager at Acme Corp, a multinational enterprise. Acme uses Salesforce for CRM, Slack for internal communication, and Adobe Creative Cloud for marketing, among other applications. Before SSO, Alex logged in to each one separately. After Acme implements enterprise SSO: 1. **Single login: **Alex logs in once in the morning with her credentials and multi-factor authentication (MFA), and that session covers her apps for the day. 2. **Seamless access: **Throughout the day, Alex moves between applications without logging in again. 3. **Mobile accessibility:** Away from the office, Alex approves budget requests from her phone through the same SSO sign-in. This simplified narrative showcases how enterprise SSO can dramatically alter the daily experience for employees, eliminating repetitive logins and fostering a more efficient and secure workflow. **Read more: **[**The Developer's Guide to Implementing Single Sign-On**]()**.** ## How enterprise SSO works SSO depends on trust set up in advance. When an organization connects an app to its IdP, the two exchange configuration (SAML metadata or OIDC client details), including the certificates or keys the app uses to verify what the IdP sends back. After that, a typical login works like this: 1. The user opens the app, known in SSO as the service provider (SP). 2. The app determines which organization the user belongs to, a step called home realm discovery. It usually does this from the user’s email domain, but it can also use an organization-specific login URL or identifier. 3. The app redirects the user to that organization’s IdP with an authentication request. 4. The user authenticates at the IdP, often with MFA, under whatever policies the organization has set. 5. The IdP sends the user back to the app. With [SAML](), the browser carries a signed assertion to the app. With [OIDC](), the app receives an authorization code and exchanges it with the IdP for an ID token. 6. The app verifies the response, matches it to a user account (creating one on first login if just-in-time provisioning is enabled), maps the user’s IdP groups to roles in the app, and starts its own session. Because the user now has a session at the IdP, the next connected app they open completes the same exchange without a new login prompt. Logins can also start from the IdP’s app dashboard (IdP-initiated SSO), where the user picks the app and the IdP starts the exchange. ## What an enterprise SSO solution includes | Component | What it does | | --- | --- | | [Identity provider]() | Verifies users; examples include Okta, Microsoft Entra ID, or Google Workspace | | Service provider | The app the user signs in to | | SAML 2.0 and OIDC | Protocols that carry the login between the two | | Directory integration and [SCIM]() | Syncs accounts, groups, and roles, and removes access when a user is deprovisioned | | MFA and access policies | Enforced once, at the IdP | | Admin setup and testing | Connection setup, attribute and group mapping, domain verification | SaaS vendors also need a separate SSO connection for each customer organization, and some customers use more than one identity provider. For example, Descope supports [multiple IdPs per tenant]() and lets each customer’s admins configure their own connection through the [SSO Setup Suite](). ## The core benefits of enterprise SSO The [benefits of SSO]() in enterprise use cases include: - **Enhanced security:** SSO reduces the number of passwords in use and centralizes authentication at the IdP. That leaves fewer credentials to [phish]() or reuse, and one place to enforce MFA and monitor sign-ins. - **User experience:** Employees log in once instead of signing in to each app separately throughout the day. - **Increased productivity:** SSO removes repeated logins for employees and much of the credential management work for IT and support teams. - **Cost-efficient IT:** Password resets are a routine help desk request, and fewer passwords mean fewer resets. Centralized provisioning also shows which users hold which app accounts, which helps companies drop unused software licenses. ## Enterprise SSO implementation considerations Because enterprise SSO centralizes login and account management, it also creates a single point of failure: a compromised IdP account can open every connected app. That risk, along with integration and scale, shapes how organizations roll it out. ### Cybersecurity assurance best practices Enterprise SSO applies uniform security settings across every connected app, as long as the IdP itself is well protected. Key elements include: - [**MFA**](): SSO is typically paired with strong authentication at the IdP, such as [phishing-resistant MFA]() or [biometric authentication](). - **Continuous monitoring**: Monitoring IdP sign-ins and SSO configuration changes helps teams catch suspicious activity quickly. - **Employee training**: Staff need to protect their IdP credentials and recognize phishing attempts that imitate the company’s login page. **Read more:** [SSO vs MFA: Choosing the Right Authentication Approach]()  ### Integration with existing infrastructure An SSO rollout also has to fit the systems already in place: - **System assessment:** A review of the current IT setup surfaces compatibility or integration issues before rollout. - **API compatibility:** The SSO solution’s APIs, like the [Descope REST API](), need to exchange data with the enterprise applications and services it connects to. - **Legacy system integration**: Older systems that don’t support SAML or OIDC may need a proxy or custom adapter to join the SSO setup. - **Customization needs**: Authentication flows and access controls often need to be adapted to the organization’s security requirements. ### Scalability and performance An SSO solution also has to keep performing as the organization adds users, devices, and apps. Load testing before rollout and monitoring login latency afterward catch bottlenecks before they affect employees. ## Why enterprise customers require SSO from SaaS vendors Enterprise IT teams want every app to sign in through the company’s identity provider because it gives them: - **One policy:** MFA and access rules apply to every app. - **One place to grant access:** New hires get app access through the IdP. - **One place to remove access:** Deprovisioning a departing employee at the IdP, often automatically through SCIM, removes their access to every connected app. - **A simpler security review:** SSO support is a standard question in procurement. SSO usually comes up alongside other [enterprise readiness]() requirements, such as SCIM provisioning, uptime service-level agreements (SLAs), and audit logs. The [B2B Enterprise Readiness Checklist]() covers the full list. ## Get your app enterprise-ready with Descope For B2B app builders selling to large enterprises, SSO support is a prerequisite. Building it in-house means implementing and troubleshooting [*SAML*]() and [*OpenID Connect*]() for every customer’s identity provider. Descope’s visual workflows and SDKs [*add SSO*]() to an app with support for SAML and OIDC, both IdP-initiated and SP-initiated. Each customer is configured as its own tenant, and the [SSO Setup Suite]() lets a customer’s IT admin configure SSO and SCIM, map attributes and groups, and test the connection themselves, with guides for 15+ identity providers. [Notch](), for example, added SSO to its existing authentication flow in minutes and onboarded an enterprise customer the next day. [Sign up]() for a Free Forever account with Descope to drag-and-drop your SSO. Have questions about our platform? [Book time]() with our auth experts. ![SAML SSO Flow]() ## FAQs about enterprise SSO --- ### [What Is Authorization and How Does It Work?](https://www.descope.com/learn/post/authorization) *Full content: [https://www.descope.com/learn/post/authorization.md](https://www.descope.com/learn/post/authorization.md)* Every app with more than one kind of user has to decide who can do what: which records a user can read, which settings an admin can change, and which actions a service can take. That decision is authorization. It runs after authentication, which confirms who a user is, and it applies to people, devices, and software. Authorization mistakes are among the most common security flaws in web applications, whether the app belongs to a startup or an enterprise. ## At a glance - Authorization decides what an authenticated user, device, or service can do and which resources it can reach. - Authentication confirms who you are, while authorization decides what you can access once you’re in. - In identity and access management (IAM), authorization is set through roles, attributes, or relationships, as in role-based (RBAC), attribute-based (ABAC), and relationship-based (ReBAC) access control. - After login, roles and permissions often travel with the user’s session token, such as a JSON Web Token (JWT), and the app checks them before allowing an action. ## What is authorization? Authorization in cybersecurity refers to the process of granting or denying access to resources based on the identity and permission level of a user or device (collectively referred to as an entity). In [identity and access management (IAM)](), authentication proves who someone is, while authorization controls what they can do. The authorization process implements access controls that determine the exact activities an entity is allowed to perform on a specific resource. Authorization may be granted to entities on a case-by-case basis or according to a predetermined model, such as[ role-based access control](), covered below.  Authorization is a core part of cybersecurity, protecting the confidentiality, integrity, and availability of data and resources within an IT environment. It ensures that only authorized users can access those resources and act on them, whether the threat is an internal mistake or an external attack. Properly set authorization also contains the damage when something goes wrong by limiting each entity to the least amount of data it needs to do its job. For example, Jane is an employee at XYZ Corporation. She logs in to the company’s document management system. Once logged in, Jane has access to edit and create documents in the Sales folder because she is part of the sales team. However, she cannot access the HR folder as she doesn’t have the necessary permissions. [Authorization 101 For Developers | RBAC, ReBAC, and ABAC]() ## Authorization vs. authentication Authorization works in tandem with[ authentication](). Before a user is granted access, they must first confirm their identity through an[ authentication method](), such as a[ username and password](),[ social login](), or[ biometrics]().  Voting in an election illustrates the distinction: - Checking in at the polling station, where poll workers confirm a voter’s identity against the voter rolls, *authenticates *the individual. - The voter’s registration then determines what they’re *authorized *to do. Depending on criteria such as political party affiliation or location, some voters may hold additional authorizations, such as voting in a party’s primary or voting by mail. | | **Authentication** | **Authorization** | | --- | --- | --- | | **Definition** | Verifying the identity of a user, system, or process. | Granting or denying access to resources based on the authenticated user's permissions. | | **Purpose** | Confirming the user is who they claim to be. | Determining what actions or resources a user is allowed to access. | | **Focus** | Identity verification. | Access control. | | **Process** | Usually involves verifying credentials (e.g., username/password, biometrics). | Involves checking if the authenticated user has the necessary permissions for the requested action/resource. | | **Goal** | Ensuring only authorized users gain access. | Restricting access to specific functionalities or data based on permissions. | | **Examples** | Logging into an email account with a username and password. | A user with 'admin' privileges being able to configure system settings. | **Learn more:** [Authentication vs Authorization]() ## How does authorization work? Authorization grants or denies access based on the user’s permission level. For example, an employee may have read-only access to specific files, while a manager may have read-write access. An access control system typically manages authorization, enforcing the organization’s policies and rules through the following steps: - **Initial authentication:** First, users must confirm their identities, typically by entering a username and password or using a[ passwordless method](). - **Authorization request:** Once the user is authenticated, they can request access to a particular resource. This request includes user details, such as a username, and relevant attributes, such as role or group affiliation. - **Access control evaluation:** The access control system receives the authorization request and checks whether the user can access the requested resource. This typically involves checking policies or rules defining who can access resources under what conditions. - **Authorization decision:** Based on the access control policies, the system makes a decision, either granting or denying the user’s request. If the user is granted permission, they can access the resource. If access is denied, the user is informed that they do not have permission to access the resource. - **Activity logging:** Following the authorization decision, the system records all relevant information, such as the time of access, the user’s identity, and activity. This information can be used for auditing and compliance purposes and for detecting and investigating security incidents. - **Revoking permissions:** Access permissions can be withdrawn at any time, either automatically (based on predefined policies) or manually (by an administrator). When access is revoked, the user can no longer access the resource. The revocation is logged for auditing and investigation. ### How apps check authorization after login After a user logs in, the app receives a session token, often a [JWT](). The token can carry the user’s roles and permissions as claims, so the app’s backend can validate it and check those claims on each request without a separate lookup. For example, Descope includes a user’s roles and permissions at both the project and tenant levels in the session JWT. Claims work well for broad checks, like whether a user is an admin. They’re a poor fit for [fine-grained checks](), such as whether a user owns a specific document, because a token can’t list every resource a user can reach, and its claims stay fixed until the token is refreshed. For those checks, the app queries an authorization service at request time. ## Types of authorization Most authorization is granted through one of three main access control models: - Role-based - Relationship-based - Attribute-based Attribute-based models are the broadest way to grant authorization since anything can theoretically be considered an attribute. Roles can be viewed as a subset of attributes, and relationships fall somewhere in between. ![A visualization of the different types of authorization]() ### Role-Based Access Control (RBAC) [RBAC]() is a method of authorization that assigns users to specific roles based on their job responsibilities. Each role has a set of permissions that determine what actions the user can perform. For example, a bookkeeper in an accounting department may have read-only access to financial reports, while a senior accountant may have read-write access. ### Attribute-Based Access Control (ABAC) [ABAC]() determines user authorizations by the attributes associated with their identity or account. These attributes may include their job title (as with RBAC) but also other factors such as location, department, team lead, shift, current projects, etc. As a result, ABAC is more granular than RBAC, allowing for more precise control over user access. **Learn more:**[ RBAC vs. ABAC: What’s the Difference?]() ### Relationship-Based Access Control (ReBAC) [ReBAC]() determines authorization based on relationships between resources and identities (or users). Some of these relationships include: - **Data ownership:** For example, after you create a post on LinkedIn, you can edit and delete it. However, you can’t edit or delete the posts of others. You have these permissions for the posts you create since you are the “owner” of these posts. - **Parent-child relationships:** For example, if you have “edit” permissions for a folder, you automatically have “edit” permissions on all the files within that folder, since the folder and files have a parent-child hierarchy. - **User groups:** Rather than individually assigning permissions to roles, you can place users in groups and assign permissions to the whole group. This approach avoids ballooning roles with individual permissions as organizations grow in size. ![ReBAC examples]() **Learn more:**[ RBAC vs ReBAC: Which Is Right for You?]()  ### Other access control models Two older [access control models](): - Mandatory Access Control (MAC): a central authority assigns security labels to data based on its sensitivity, and users can access only the data their clearance allows. Users can’t change these rules. - Discretionary Access Control (DAC): the opposite of MAC, DAC leaves authorization decisions to individual discretion. The resource owner most commonly has the deciding vote. ## Real-world examples of authorization in software Authorization models deploy in countless configurations across diverse scenarios, from consumer-facing apps to B2B platforms.  - **Authorization in operating systems:** Operating systems often restrict access to sensitive files and settings. For example, a user may be required to enter an administrator password to install software or modify system settings. - **Authorization in web applications:** Web applications use authorization to restrict access to certain pages or features. For example, a user may need to be logged in and have a certain level of permission to view customer data or place an order. - **Authorization in databases:** Databases use authorization to restrict access to sensitive data. For example, a user may only be able to view data from a specific table or have read-only access to certain fields. - **Authorization in cloud environments:** Cloud environments use authorization to restrict access to virtual machines (VM), storage, and other resources. For instance, a user may be assigned the “VM Operator” role, which allows them to start, stop, and restart VMs. Another user may be assigned the “VM Administrator” role, which grants them complete control over the VMs. - **Authorization in Internet of Things (IoT) devices:** Authorization is a critical mechanism used to secure and control access to sensitive settings or data on connected devices. For example, the owner of a smart home security camera may be able to change its settings and share access, while other household members can only view the live feed. - **Authorization in B2B SaaS apps:** A user can be an admin in one customer’s[ tenant]() and a regular member in another. These roles are scoped per tenant, which is RBAC, so the same person gets different permissions depending on the tenant they’re working in. - **Authorization in document apps:** The person who creates a file can delete it, while collaborators can only edit it. Access follows the relationship between each user and the document, which is ReBAC. - **Authorization in feature and region gating:** An app can open a feature only for a certain subscription tier, or block a request from a country it doesn’t serve. The decision depends on attributes of the user or request, which is ABAC. ## Common authorization challenges Broken access control holds the #1 position in the[ OWASP Top 10:2025](), and OWASP reports that 100% of the applications tested were found to have some form of it. Common challenges include the following:  - **Lack of understanding:** Authorization depends on complex models that require active management. Organizations that don’t understand these models can end up with misconfigurations, security vulnerabilities, and authorizations that were improperly granted or never revoked (i.e., “permission bloat”). - **Weak authentication:** Weak passwords and[ inadequate authentication]() methods can make it easy for attackers to[ take over legitimate accounts](), inherit their authorizations, and further infiltrate the environment. - **Insufficient monitoring:** Organizations are always changing, as users join, change roles, and leave. Over time, keeping track of who has which authorizations gets harder, and without the right monitoring, organizations will struggle to detect unauthorized access or changes to authorization settings. - **Human error:** People are responsible for security configurations and, in some cases, data entry. Their mistakes can cause misconfigurations, data leaks, or incorrect provisioning. ## Choosing the best authorization approach for your organization The right authorization model depends on an organization’s security needs, scale, and operational complexity. There are three main approaches: - [**Coarse-Grained Authorization**]()**:** This approach provides a high-level control mechanism. It’s typically easier to implement and manage. Access is often based on predefined roles or groups within the organization, making it suitable for smaller companies or less complex systems where broad access levels are sufficient. - [**Fine-Grained Authorization**]()**:** Here, control is much more detailed. Access can be tailored to the individual level, allowing for specific permissions to be granted for particular resources or actions. It suits dynamic and large-scale environments, where access policies need to reflect detailed business rules and compliance requirements. - **Hybrid Authorization:** A combination of both, this approach balances ease of management with tailored access. It might involve setting coarse-grained roles with some fine-grained rules for sensitive operations, providing flexibility and control where needed. When deciding on the best authorization model for your organization, take into consideration factors such as: - Sensitivity of controlled data - Necessity of compliance with regulations - Complexity of user roles within your system - Potential need for scalability Fine-grained authorization is often the choice for organizations that need precise access control and expect their requirements to change. | **Criteria** | **Fine-Grained Authorization** | **Coarse-Grained Authorization** | | --- | --- | --- | | **Granularity** | Offers a high level of granularity, allowing for precise control over individual actions or data elements. | Provides a broader, more generalized control, often based on roles or high-level permissions. | | **Use Cases** | Ideal for scenarios requiring detailed control, such as financial transactions, healthcare records, or intellectual property access. | Suited for situations where simplicity and efficiency are prioritized, such as general employee access levels or public-facing information. | | **Flexibility** | Offers a high degree of flexibility in defining specific access rights for different users or roles. | Provides less flexibility as permissions are predefined based on roles, limiting customization for individual users. | | **User Experience** | Offers a more tailored user experience with users having precisely the permissions they need for their roles. | Provides a simplified user experience by grouping users into roles, reducing the need for individual permission management. | | **Security** | Enhances security by limiting access to only necessary actions or data, reducing the risk of unauthorized activities. | Maintains security through predefined roles but may have a slightly higher risk of over-permissioned users. | ## Fine-grained authorization with Descope Adding authorization to a B2B app can be complex and time-consuming. Thinking about tenants, roles, relationships, and permissions diverts developers from other business-critical initiatives. Descope helps developers build secure authentication and user journeys for their apps. Descope’s[ drag-and-drop workflows](), SDKs, and APIs abstract away the complexity of authentication so developers can spend time building their core product.[ B2B app]() builders can also use Descope to add[ RBAC](),[ ReBAC](), and[ ABAC]() to their app easily, with roles created at the project level or for an individual tenant. Learn more in the[ authorization docs]().  [Sign up for a “Free Forever” Descope account]() to get started, or[ schedule time with our auth experts]() if you have any questions.  ![Descope FGA overview]() ## FAQs about authorization --- ### [What Is CIAM: All You Need to Know](https://www.descope.com/learn/post/ciam) *Full content: [https://www.descope.com/learn/post/ciam.md](https://www.descope.com/learn/post/ciam.md)* How customers sign up, log in, and trust a business with their data affects both security and revenue. Login friction alone has a measurable cost: in the FIDO Alliance’s [State of Passkeys 2026]() report, 47% of consumers said they’re likely to abandon a purchase or sign-in when they can’t remember a password. Customer identity and access management (CIAM) is the category of tools built to manage that tradeoff, offering features like streamlined logins, data privacy controls, and advanced authentication options while protecting customer accounts from attacks. ## At a glance - Customer identity and access management (CIAM) manages how external users, such as customers and business partners, sign up, log in, and access an application. - A CIAM platform handles registration, authentication, authorization, and self-service account management for those users. - Common CIAM sign-up and login methods include passkeys, magic links, one-time passwords (OTPs), social login, and passwords. - Core CIAM security capabilities include adaptive multi-factor authentication (MFA), bot detection, and session and token management. - Workforce identity and access management (IAM) serves employees, while CIAM serves customers and has to balance security with user experience. ## What is CIAM? Customer identity and access management (CIAM) is a framework that manages the registration, authentication, and access control of an organization’s external identities. It prioritizes both data security and user experience for people outside the internal workforce, such as customers, suppliers, business partners, and other end users not employed by the organization. CIAM tools help organizations provide secure, seamless authentication and user journeys for their customers while reducing the workload for engineering and IT teams. For end users, CIAM typically manifests in familiar processes like signing up, registering, and verifying their identity during logins. For organizations and developers, however, CIAM involves a variety of user identity-related tasks, including: - **Collecting user information:** Names, phone numbers, emails, and any relevant documentation. - **Secure data storage:** Ensuring personal information is kept in a safe repository. - **Managing login procedures:** Enforcing [multi-factor authentication (MFA)]() or other [authentication methods](). - **Monitoring login activity:** Watching for signs of attack, such as bot traffic, credential stuffing, or logins from unfamiliar devices. - **Controlling user access:** Determining which features or services are available to different users. - **Delegating management:** Allowing users to handle certain aspects of their identity, like password resets or privacy settings. CIAM platforms vary in scope, but most cover an app’s core authentication, user management, and account security needs. Some run on-premises, though most are delivered in the cloud as [identity as a service (IDaaS)](). ### CIAM vs. Identity and Access Management (IAM) Much like CIAM, identity and access management (IAM) is a set of tools that verifies identities and controls access to digital platforms. Both solutions perform similar functions, including: - **Protecting sensitive information:** Ensuring only authorized users have access. - **Verifying identities:** Confirming users are who they claim to be, whether through passwords, passkeys, or federated login. - **Managing access levels:** Granting permissions based on a user’s role or authorization level. Despite these overlapping functions, a few key distinctions exist between CIAM and IAM. Simply put, IAM solutions are primarily used for employees and internal stakeholders, whereas CIAM is designed for customers and external stakeholders. For a full breakdown of use cases and how to choose, see [IAM vs. CIAM](). | | **CIAM** | **IAM** | | --- | --- | --- | | **Users** | CIAM is generally used to manage an organization’s customer base and other external stakeholders. | IAM solutions control access permissions for employees, contractors, and other internal stakeholders. | | **Priorities** | CIAM solutions balance security with user experience (UX) to appeal to a larger audience that can choose which systems they use. | IAM solutions generally aren’t public-facing; they prioritize security over functionality, intuitiveness, and user experience (UX). | | **Use Cases** | Popular CIAM use cases include customer authentication, customer single sign-on (SSO), and adaptive MFA. | Popular IAM use cases include employee SSO and user provisioning in HR systems. | ## How does CIAM work? CIAM solutions offer a range of tools for security, identity verification, and authentication, including: - Customer registration and profile creation - Support for a variety of authentication protocols and methods - Self-service account management - Fine-grained access management and authorization - Data access governance - Directory services - Federated authentication and [single sign-on (SSO)]() - Preference and consent management The specific CIAM capabilities an app employs will depend on its purpose and design. For example, ridesharing platforms may use CIAM to: - Simplify rider and driver registration by verifying identification or sending a code to their mobile number. - Securely store sensitive user data in a trusted [identity provider (IdP)]() database. - Enforce security measures like risk-based MFA, trusted device checks, and session timeouts. - Control user access to features, enabling tiered subscription services. - Analyze customer behavior to optimize the onboarding and login experience. - Allow users to manage their accounts, including updating phone numbers or passwords. ### How sign-up and login work From the customer’s side, sign-up and login typically follow these steps: 1. The customer picks a sign-up method, such as a passkey, social login, magic link, OTP, or password. 2. The CIAM platform verifies the identifier, such as an email address or phone number, and creates a profile. 3. The platform collects more profile data over time through [progressive profiling](), which gathers user data gradually instead of all at once during sign-up. 4. Risk checks, such as bot detection and device signals, run in the background, and the platform asks for [step-up MFA]() only when a login looks risky. 5. The platform issues and manages a session. 6. Returning users log in with the same method, or through SSO across apps. Every CIAM platform provides three central capabilities: - [**Authentication**](): Verifies that users are who they claim to be, whether by checking a password, a passkey signature, a one-time code, or a token from a social login provider. - [**Authorization**](): Grants users the appropriate level of platform access based on the permissions assigned to their accounts. - **Identity management**: Encompasses a variety of capabilities, such as user provisioning (e.g., through System for Cross-domain Identity Management, or SCIM), tenant management, token and session management, and delegated administration. ![CIAM core capabilities]() ## Key CIAM features and security capabilities | **Capability** | **What it does** | **Security or UX payoff** | | --- | --- | --- | | Registration and progressive profiling | Builds profiles, gathers data gradually | Shorter sign-up forms | | Authentication methods | Passkeys, magic links, OTPs, social login, passwords | Less password friction; passkeys also resist phishing | | SSO and federation | Security Assertion Markup Language (SAML), OpenID Connect (OIDC), and federated login | One login across apps, enterprise readiness | | Adaptive MFA and step-up | Extra checks only for risky logins | Strong security, low friction | | Bot and fraud protection | Detects bots and anomalous logins | Cuts account takeover and credential stuffing | | Session and token management | Refresh token rotation and reuse detection | Secure sessions after login | | Authorization | Role-based (RBAC), relationship-based (ReBAC), and attribute-based (ABAC) access control | Users see only what they’re entitled to | | Self-service, consent, and preferences | Users manage accounts and consent | Lighter support load | For example, Descope includes built-in [risk signals]() such as bot detection and impossible travel, which a login flow can use to [require MFA]() only when a login looks risky. ## Business benefits of CIAM CIAM’s main business benefits include: - **Improved user adoption and conversion.** CIAM tools enable personalized, frictionless experiences with features like progressive profiling, consent and preference management, self-service admin, and passwordless login. These capabilities help organizations engage customers more effectively, increasing both user acquisition and retention. - **Enhanced protection against identity attacks.** CIAM solutions offer advanced security features, including [adaptive authentication](), secure session management, [bot protection](), and [biometric authentication](). These measures work together to mitigate the risks of [account takeover](), [credential stuffing](), and other identity-based attacks, providing customers with a higher level of trust. - **Increased engineering productivity and focus.** By outsourcing identity management to a trusted [CIAM provider](), businesses can significantly reduce the workload for engineering teams. This shift allows developers to focus on more critical areas, as CIAM solutions handle session management, credential storage, password resets, and the implementation of MFA. - **B2B enterprise readiness.** CIAM platforms offer vital features like [SAML and OIDC SSO](), [federated authentication](), tenant management, and [user provisioning](). These capabilities allow B2B companies to scale and expand their offerings, enabling them to move upmarket and serve enterprise customers more effectively. ## Common use cases of CIAM CIAM requirements differ by industry. Some of the most common use cases include the following. ### Ecommerce and retail In retail, CIAM supports a fast checkout by letting returning customers log in with whichever method they prefer. That helps reduce cart abandonment and increases customer satisfaction. The profile data CIAM collects also feeds personalized recommendations, which supports retention and repeat purchases. **Read more:** [Authentication in Ecommerce: Best Methods & CIAM Tips]() ### Online banking and financial services Financial services face high fraud pressure and strict regulation. Through MFA and identity verification, CIAM helps prevent fraud and account takeover, and it supports compliance with rules that require strong authentication for customers, such as the EU’s PSD2 [strong customer authentication]() requirement for online banking and payments. CIAM’s support for SSO and federated authentication also lets customers move between financial tools and accounts without logging in again. **Read more:** [Customer IAM in Banking: Considerations & Best Practices]() ### Healthcare In healthcare, CIAM helps secure patient data while enabling convenient access to medical records, appointment scheduling, and telehealth services. Under privacy rules like HIPAA in the U.S., CIAM helps restrict sensitive information to authorized individuals. Self-service options also let patients update their profiles and manage their preferences, which reduces administrative work for healthcare providers. **Read more: **[Healthcare Identity and Access Management Best Practices]() ### Travel and hospitality Travel platforms and hospitality businesses use CIAM to create personalized user experiences by leveraging data like travel preferences, booking history, and loyalty program details. CIAM supports seamless logins across different devices and applications, whether booking flights, managing reservations, or earning loyalty points. It also enables customer segmentation, allowing businesses to offer tailored promotions and services that increase engagement and conversion rates. ### B2B platforms and SaaS B2B platforms and SaaS businesses use CIAM to manage user access across multiple customer organizations, often called tenants. It helps implement secure, scalable access controls with features like RBAC and federated identity management. CIAM simplifies onboarding for enterprise clients by allowing customization of user roles, access permissions, and integrations with other enterprise systems. Read more: [A Primer on B2B Authentication With Descope]() ### Government and public services Government agencies and public service organizations use CIAM to provide citizens with secure, convenient access to services such as tax filing, social security, and health benefits. Identity verification at sign-up confirms who a citizen is, and strong authentication, including passwordless methods, protects the account afterward. SSO across services also means citizens don’t need a separate login for each agency portal. ## How to choose the right CIAM solution Choosing the right CIAM solution for your app requires careful evaluation to ensure it meets both your current and future identity management needs. Here are the key criteria to help you evaluate potential CIAM providers. ### Breadth and depth of auth method support As your organization grows, your identity needs will evolve too. CIAM providers that support a wide range of authentication methods and implementation approaches leave more options open as those needs change. Look for providers that offer: - Support for popular authentication methods like [passkeys](), [magic links](), [OTPs](), [social login](), [authenticator apps](), and [passwords](). - Compatibility with standard, interoperable protocols like [SAML](), [OpenID Connect](), [WebAuthn](), and Federated Credential Management (FedCM). - Support for different authorization models ([RBAC](), [ReBAC](), [ABAC]()). - Integration with both custom and off-the-shelf apps. ### Low-code customizability Customer authentication is rarely one-size-fits-all. A good CIAM solution will allow you to easily modify user journeys and authentication flows to meet your app's specific needs. Key features to look for include:  - Customizable user journeys, preferably via an intuitive, low-code visual interface. - Flexible user models with custom attributes and granular access control. - The ability to A/B test and measure login flows and user journeys to optimize the experience. - Easy customization of user-facing screens and the ability to implement [progressive profiling](). ### Extensible ecosystem Customer identity impacts nearly every aspect of your business. A CIAM solution should integrate with third-party services to keep customer identity synchronized across tools and departments. Look for: - Integrations with existing tools in the fraud prevention, identity verification, customer relationship management (CRM), and customer data platform (CDP) space. - A flexible integration framework that supports adding more tools as your needs grow. - The ability to add custom and in-house integrations (e.g., HTTP, SMTP, audit logs). - Low-effort integration processes, allowing for easy setup, testing, and swapping tools when needed. ### Reliability, security, and support Problems with customer sign-up or login lead directly to lost business, and breaches of customer data are costly. Factors to evaluate include: - Historical availability, service-level agreement (SLA) performance, and response times. - Session and token management practices, such as refresh token rotation and reuse detection. - The largest customer the CIAM solution serves, which can indicate scalability. - Implementation flexibility for developers with multiple abstraction layers (UI, SDK, API). - Key certifications like SOC 2 Type 2 and ISO 27001 to ensure industry-standard security practices. - Availability of active and passive support, as well as assistance with migration to new systems. - Customer reviews and ratings on trusted platforms like G2 to gauge overall satisfaction and performance. ## Hassle-free CIAM solutions with Descope If you are evaluating CIAM solutions for your organization, Descope can help. Our [drag & drop CIAM platform]() helps thousands of organizations improve user onboarding, protect accounts against account takeover, and unify identities across customer-facing apps with little or no code. [Sign up]() for a Free Forever Descope account to get started! If you have questions, [book a demo]() with our auth experts. ![Fig: Drag-and-drop magic links with Descope]() ## FAQs about customer identity and access management (CIAM) --- ## Blog ### [Customer and Agentic Identity Tips for HealthTech Apps](https://www.descope.com/blog/post/healthtech-identity-tips) Learn seven identity tips for healthtech companies scaling into the enterprise, from SSO and access to SMART on FHIR, AI agents, and modeling family identities. *Full content: [https://www.descope.com/blog/post/healthtech-identity-tips.md](https://www.descope.com/blog/post/healthtech-identity-tips.md)* Your healthtech service may have started with a simple identity need — giving patients or members a secure way to sign up and log in. As you move upmarket, that login experience quickly becomes more complex. Hospitals expect enterprise SSO and automated provisioning. Different users need different access levels. Security teams look for stronger authentication and auditable controls for protected health information (PHI). EHR integrations add SMART on FHIR requirements. AI agents also have their own identity and permission needs. Increasingly, those agents include personal agents like Instinct and Muse that patients and members bring with them. Identity stakes are especially high in healthcare, which has had the most expensive data breaches for 14 consecutive years,[ averaging $7.42 million per breach in 2025](). For healthtech companies moving toward a multi-tenant enterprise platform, the challenge is preparing for these identity requirements before each new customer onboarding becomes another engineering project. These tips can help you build for what comes next for your healthcare technology application. ![Identity Tips for HealthTech]() ## At a glance - Healthtech identity becomes more complex as products scale from a single patient portal to a multi-tenant enterprise platform serving providers, payers, employers, partners, and AI agents. - The tips covered here are planning for multi-persona identity, setting up self-service SSO and SCIM, moving beyond passwords and SMS OTP, building access control for PHI, making SMART on FHIR a configurable flow, establishing agent identity early, and modeling guardian and dependent relationships. - Each tip pairs a challenge healthtech teams commonly face while scaling with a practical solution so identity is fixed with purpose rather than patched deal by deal or launch by launch. - Descope brings these capabilities together in one platform with capabilities such as enterprise SSO and SCIM, adaptive authentication, fine-grained access control, SMART on FHIR support, agentic identity for MCP, and Family Accounts. ## Plan for multi-persona identity in advance ### Challenge Most healthtech apps don’t stay single-persona for long. A patient or member portal may expand to clinicians, caregivers, administrators, employers, and other users, each with different authentication and access needs. For instance, a patient signing in from a phone might use a [passkey]() or [magic link](), while a clinician may require [enterprise SSO]() and [MFA](). Caregivers, in turn, may need permission to act for dependents, and administrators may need broader organizational access. If your identity architecture supports only one user type, each new persona becomes another engineering project. Users may have multiple accounts, and teams struggle to maintain consistent access controls. ### Solution Plan for different user types early so your identity architecture grows with your product. Consider who needs access today and how those needs could change as you add customers and services. - **Map your user types:** Identify current and future authentication and access requirements. - **Create a shared identity layer:** Keep identity consistent across applications and portals. - **Adapt each experience:** Apply authentication, branding, and permissions based on context. - **Model user relationships:** Connect caregivers, patients, clinicians, and organizations appropriately. With these foundations in place, you can add new personas without creating separate identity systems or rebuilding your application. **Also read: **[Descope Per-Tenant Identity Isolation for B2B Platforms]() ## Set up self-service SSO and SCIM ### Challenge Onboarding a hospital, health system, PBM, or large employer can introduce identity requirements your product has not faced before. Enterprise IT teams may expect [SAML]() or [OIDC]() SSO,[ SCIM provisioning](),[ tenant-level roles](), delegated administration, and audit logs. If developers must configure identity for every new customer, onboarding can quickly become a bottleneck. Deployments take longer, engineers get pulled from product work, and support demands increase as customer requirements change. ### Solution Make enterprise identity onboarding self-service so customer IT teams can configure and manage their environment through a guided, repeatable experience. - **Guide SSO setup:** Walk admins through configuring SAML or OIDC connections. - **Automate SCIM provisioning:** Provision and deprovision users as access changes. - **Validate configurations:** Test and identify setup issues before connections go live. - **Delegate administration:** Let customers manage users, roles, access, and identity settings. Self-service helps enterprise customers manage their identity needs while keeping your engineering workload from growing with every new account. ![SSO Setup Suite IdP selection]() **Also read:** [Descope SSO Setup Suite]() and [Descope Admin Portal]() ## Move beyond passwords and SMS OTP ### Challenge Healthtech apps must protect sensitive data and accounts while keeping access simple for patients and clinicians. Passwords complicate this balance because they can be phished, reused, or exposed in attacks. Adding [SMS OTP]() to every login creates friction and does not always protect against modern threats. More authentication steps can frustrate patients trying to access care and interrupt clinicians during routine work. Too much friction may even encourage users to find workarounds that introduce new security risks. ### Solution Adjust authentication based on risk. Modern methods simplify everyday access, while adaptive controls add stronger verification when needed. - **Reduce password reliance:** Use passkeys and magic links for simpler, more secure authentication. - **Evaluate risk signals:** Consider device, behavior, network context, and [fraud indicators](). - **Use**[ adaptive MFA]()**:** Trigger additional verification for unusual or higher-risk activity. - **Protect sensitive actions:** Apply[ step-up authentication]() when users access PHI or perform higher-risk actions. For example, a clinician logging in from a trusted device can work without MFA, or accessing health records triggers an additional authentication step. This strengthens security and keeps routine access simple. ## Build access control for protected health information ### Challenge In healthcare, a user's role often does not determine all the information they should access. For example, a clinician may need records for patients on their care team, while a billing specialist may only need information tied to a specific facility. Access depends on both the user's role and their relationship to the patient or organization. As a result, traditional[ role-based access control (RBAC)]() struggles with this complexity. Teams often use custom permissions, making access harder to manage and audit and increasing the risk of inappropriate access to[ protected health information (PHI)](). ### Solution Design authorization around the context of each request. Combining RBAC with [attribute-based access control (ABAC)]() and [relationship-based access control (ReBAC)]() lets teams account for roles, attributes, and healthcare relationships. - **Define access by role:** Use RBAC to establish baseline permissions. - **Next, add contextual attributes:** Use ABAC to consider factors such as facility or organization. - **Model healthcare relationships:** Use ReBAC to define relationships among patients, authorized providers, care teams, and data resources. - **Keep permissions current:** Adjust access as patient, provider, or organizational relationships change. This approach helps teams apply least-privilege access to PHI and manage authorization more easily as the application grows. **Also read: **[Healthcare Identity and Access Management Best Practices]() ## Make SMART on FHIR a configurable identity flow ### Challenge Connecting a healthtech app to an electronic health record (EHR) introduces specialized identity requirements.[ SMART on FHIR]() builds on standards like[ OAuth 2.0]() and OIDC, while adding healthcare-specific requirements for scopes, authorization, and consent. Teams without deep OAuth or SMART on FHIR expertise will need to build redirects, token validation, consent flows, and authorization logic themselves. This adds code to maintain and can cause issues during EHR certification or customer rollout. ### Solution Create a consistent identity foundation for SMART on FHIR and configure flows for individual EHR and customer requirements. - **Standardize core protocols:** Use a consistent OAuth 2.0 and OIDC foundation. - **Configure healthcare requirements:** Add[ PKCE](), granular scopes, consent, and identity claims. - **Adapt each integration:** Configure flows for different EHR and customer requirements. - **Simplify ongoing changes:** Update flows as interoperability requirements evolve. This approach reduces custom authentication code and provides security teams a consistent implementation to review. Teams can reuse the same foundation as they add EHR integrations and enterprise customers. **Also read: **[How to Build SMART on FHIR-Compatible Apps With Descope]() ## Establish agent identity foundations early ### Challenge Agentic AI is becoming a core part of healthtech products, including clinical copilots, scheduling assistants, and agents connecting with healthcare systems through the [Model Context Protocol (MCP)](). During development, teams may rely on service accounts, long-lived API keys, or shared tokens. These identity anti-patterns can create security and governance issues as agents move into production. Without clearly defined [agent identities](), teams may struggle to determine which agent took an action, who authorized it, and what it can access. These issues can arise during enterprise security reviews and delay AI features that are otherwise ready for production. ### Solution Give AI agents their own identities as they move toward production. Define what each agent can access, record its activity, and link delegated actions to the appropriate user. - **Establish agent identities:** Give each agent a distinct identity, owner / delegating user information, clearly defined scopes and access permissions, and an audit history. - **Scope MCP access:** Limit agents to the tools and resources they need when accessing MCP servers. - **Govern delegated actions:** Control actions performed on a user's behalf through authorization and consent. - **Support enterprise agents:** Use[ agent SSO]() to securely connect customer agents. - **Accept personal agents on their own terms: **Give personal agents their own delegated sign-in alongside a user’s existing login, supporting protocols such as [Poppy]() with granular permissions and out-of-band approval (via [CIBA]()) for sensitive actions. These controls help teams monitor agent activity, modify or revoke access, and give security teams greater visibility into how AI interacts with healthcare systems. ![Agentic Identity Management with the Descope Agentic Identity Hub]() **Also read: **[MCP Server Security Best Practices to Prevent Risk]() ## Model guardian and dependent relationships ### Challenge Healthcare often involves someone acting on another person's behalf. Parents may manage care for children, multiple guardians may need access to the same dependent, and adults may help elderly parents with their healthcare. Many healthtech applications assume one account belongs to one individual. Shared family accounts weaken accountability because it is hard to determine who viewed information or took an action. Custom guardian logic can preserve separate accounts but adds engineering work and makes permissions harder to manage as family relationships change. ### Solution Build guardian and dependent relationships into your identity model so both caregivers and dependent users have distinct identities and appropriate access. - **Define dependent profiles:** Give dependents their own identity profiles even when they don't authenticate themselves. - **Separate guardian identities:** Give each guardian their own account and audit history. - **Define relationship-based permissions:** Set access based on each guardian's relationship to the dependent. - **Add approval workflows:** Require guardian approval for sensitive actions when appropriate. This approach supports multiple guardians with different permissions while keeping actions attributable to the person who performed them. It also provides clearer access controls and audit trails as caregiving relationships evolve. ## Identity tips for healthtech: at a glance | **Tip** | **Challenge** | **Solution** | | --- | --- | --- | | Plan for multi-persona identity in advance | New user types get bolted onto a single-persona identity architecture as products grow. Each addition becomes its own engineering project and leaves users with fragmented accounts. | Map every current and future persona early and build a shared identity layer that adapts authentication, branding, and permissions by context. | | Set up self-service SSO and SCIM | Enterprise IT expects to configure SAML/OIDC SSO and SCIM themselves, but manual onboarding turns every deal into an engineering project. | Give customer IT teams guided, self-service SSO and SCIM setup with built-in validation and delegated administration. | | Move beyond passwords and SMS OTP | Passwords and SMS OTP are easy to steal, and high-friction MFA at every login frustrates patients and clinicians. | Default to passkeys and magic links, then apply adaptive, risk-based step-up only when a login looks unusual. | | Build access control for protected health information | Roles alone don't capture who should see PHI, and homegrown fixes turn into brittle, hard-to-audit permission code. | Combine RBAC, ABAC, and ReBAC so access follows a person's real relationship to the patient, facility, or care team. | | Make SMART on FHIR a configurable identity flow | EHR integrations add healthcare-specific OAuth requirements that catch teams without deep OAuth expertise off guard. | Deliver SMART on FHIR as a configurable flow on a standard OAuth 2.0/OIDC base instead of custom-building it per integration. | | Establish agent identity early | AI agents using long-lived API keys or shared tokens won’t pass an enterprise customer’s security review and risk the company falling out of compliance. Patients' own personal agents also have nowhere safe to sign in. | Give every agent its own identity with scoped access to MCP servers and APIs, delegated consent, and agent SSO for enterprise customers. Support identity for personal agents with delegated sign-in, granular permissions, and approval controls. | | Model guardian and dependent relationships | Shared family logins erase the audit trail, and custom guardian workarounds add to technical debt and engineering workload. | Give dependents and guardians their own identities, with support for delegated impersonation and approval flows. | ## Descope for healthtech identity Making a healthtech application enterprise-ready introduces new identity requirements across the product. Descope unifies these capabilities in one platform, providing healthtech developers with abstraction layers like [visual workflows](), SDKs, and an [MCP server]() to easily build and modify identity journeys. **Enterprise-ready identity (CIAM):** Support different user populations through a shared identity layer. Descope provides [SAML and OIDC SSO](), [SCIM provisioning](), delegated administration via embeddable widgets and a hosted Admin Portal, [identity orchestration](), and audit trails to support enterprise onboarding and security requirements. **Self-service SSO and tenant management:** Descope’s tenant-aware architecture supports complex B2B2X identity relationships that healthtech apps often grow into. Self-service SSO and SCIM let customer IT teams configure connections, while delegated administration gives control over users and access within their organization. **Authentication and account security:** Passwordless methods like passkeys and magic links simplify authentication. Adaptive controls use contextual signals to trigger extra verification when risk rises, protecting accounts while limiting friction. **Access control for healthtech:** Descope combines RBAC, ABAC, and ReBAC to provide fine-grained authorization. Healthtech teams can define access based on roles, attributes, and relationships, helping apply least-privilege principles to PHI. **SMART on FHIR and healthcare interoperability:** Descope supports OAuth 2.0, OIDC, PKCE, granular scopes, and consent through configurable identity flows. This provides a consistent foundation for SMART on FHIR integrations and reduces specialized authentication work for EHR connectivity. **Agentic identity and MCP:** Descope’s[ Agentic Identity Hub]() gives AI agents distinct identities with controlled access and auditable activity. Teams can delegate agent access to their product APIs and MCP servers, secure downstream credentials, and support enterprise agents through Cross-App Access (XAA). For patients’ personal agents, [Descope Envoy]() gives those agents a delegated sign-in alongside a patient’s existing personal login, with granular permissions and human approvals for sensitive actions. [**Family Accounts**]()**:** Descope’s relational identity framework supports dependent profiles alongside separate identities for parents, caregivers, and guardians. Family-scoped roles and attributes define individual permissions, helping applications support complex caregiving relationships while maintaining accountability and clear audit trails. ## Descope healthtech customer stories ### Collabrios Health Formed by merging three companies (RTZ Systems, PeerPlace Networks, and Tabula Rasa's PACE EMR division), [Collabrios Health]() inherited a patchwork of legacy identity deployments that slowed customer onboarding and drained engineering time. They chose Descope for tenant-aware authentication, deep SSO support, and self-service SSO and SCIM that lets customer admins configure their own connections. The result is a "single front door" identity layer serving tens of thousands of EHR users across multiple government and healthcare tenants. ### b.well Connected Health [b.well]() needed a scalable identity system for external apps, partners, and services, with multi-region reliability and support for up to 1,500 requests per second. They migrated from Amazon Cognito to Descope in phases, starting with machine-to-machine authentication and then adding user authentication with Descope Flows. This gave b.well a flexible identity foundation for partners, services, and users, without needing a disruptive one-time migration. ## Build identity for where your healthtech business is going Identity requirements tend to grow as a healthtech business grows. What begins as a straightforward login experience can become much more complex as you add enterprise customers, support new healthcare use cases, and adopt AI agents and MCP servers. Planning for that evolution early can keep identity from becoming a recurring engineering bottleneck. Descope gives healthtech teams an identity foundation they can expand as those requirements change. Self-service SSO can simplify enterprise onboarding, while fine-grained authorization helps protect access to PHI. Family Accounts supports guardians and dependents, while its Agentic Identity Hub assigns AI agents distinct identities and controls access to backend systems. Want to see how it works? [Sign up]() for a free Descope account or[ request a demo]() to see how Descope can support your healthtech identity strategy. ## FAQs on healthtech identity --- ### [Modern Authentication Tips for Community Health Centers](https://www.descope.com/blog/post/authentication-community-health-centers) Community Health Centers serve patients with limited connectivity, shared devices, and low digital literacy. Learn how modern authentication improves security and reduces care barriers. *Full content: [https://www.descope.com/blog/post/authentication-community-health-centers.md](https://www.descope.com/blog/post/authentication-community-health-centers.md)* Community Health Centers (CHCs) are working to improve digital access as they expand healthcare services, now reaching over [31 million patients in underserved communities]() across the United States. With the adoption of patient portals, telehealth, online scheduling, and digital intake, identity and authentication systems have become key to how patients get care. CHC IT leaders are focused on making these services simple for patients and keeping their data safe. At the same time, CHCs serve patients who have very different levels of digital access. - Limited or unreliable internet connectivity - Shared or public devices across households - Lower familiarity with digital tools - Authentication systems that assume consistent access and personal devices - Increased risk of patients failing to complete login or abandoning digital services These challenges make it hard for traditional authentication methods to work well in CHC settings. Because of this, CHCs need to find new ways to balance security and accessibility so patients can get the care they need. ## At a glance - Community Health Centers (CHCs) must make patient portals, telehealth, and other digital services accessible to people with limited connectivity, shared devices, or low digital literacy. - Identity best practices include passwordless and mobile-friendly login, adaptive MFA, secure shared-device experiences, and simpler identity management across healthcare applications. - As personal AI agents begin helping patients navigate care, CHCs also need consent-based authorization, limited permissions, and auditable access on behalf of patients. - Descope supports these needs through visual authentication workflows, enterprise SSO, SMART on FHIR support, and agent access controls with Agentic Identity Hub and Descope Envoy. ## CHC authentication challenges ### Patients Identity systems aim to keep patient information safe, but in CHCs, they can sometimes make it harder for people to get care. Most authentication models are made for consumer apps, where users have their own devices, steady internet, and are comfortable with technology. Many CHC patients face a different situation. For many CHCs, the challenges often look like: - **Shared devices:** Multiple family members may use the same device, creating confusion around account access and raising potential privacy concerns. - **Password fatigue:** Patients may forget credentials or struggle with frequent resets, leading to frustration and account lockouts. - **Low digital literacy:** Complex login flows and multi-step authentication can make it difficult for some patients to successfully sign in. - **Connectivity issues:** Unreliable internet or limited data can interrupt login processes before patients complete authentication. As a result, some patients become frustrated with digital healthcare services before they even reach the appointment page, patient portal, or telehealth session they wanted to use. For CHCs trying to improve digital access, authentication needs to be secure but also fit the real needs of their communities. Personal agents may also help patients navigate digital care, from finding appointments to accessing health information. This introduces the challenge of allowing an agent to act on a patient’s behalf without sharing credentials or granting unrestricted access. **Also Read:** [Healthcare Identity and Access Management Best Practices]() ### IT teams Authentication challenges impact not only patients but also the internal teams responsible for keeping digital systems running. Community Health Centers often operate with small IT departments that must support multiple systems across clinics, telehealth services, and patient-facing applications. When authentication is fragmented or difficult to manage, IT teams can spend disproportionate time troubleshooting login issues rather than advancing digital health initiatives. This complexity grows as CHCs expand system integrations. Many use [SMART on FHIR]() to connect EHR platforms with patient apps, telehealth, and other digital tools. Although these integrations enhance care delivery, they also create additional identity and authorization challenges that are difficult to manage with limited resources. As personal agents begin interacting with healthcare applications, IT teams will also need to manage agent identities, patient consent, scoped permissions, and auditable access to sensitive data. Key challenges IT teams must manage include: - **High volume of login issues:** Frequent password resets and account recovery requests create an ongoing support burden. - **Fragmented identity systems:** Separate authentication management across portals, telehealth, and other applications adds complexity. - **Complex integrations:** IT teams must support OAuth flows, token exchanges, and authorization controls across EHR-connected applications. - **Inconsistent identity management:** Ensuring reliable authentication across multiple systems, users, and external applications is time-consuming and prone to errors. The result is growing operational overhead for IT teams that are already resource-constrained. CHCs must simplify identity management so teams can focus less on authentication and more on supporting care delivery and expanding digital services. ## Identity best practices for CHCs CHCs need to keep patient information safe and also make it simple for patients to get care online. As CHCs add more patient portals, telehealth, and digital tools, authentication is where security and easy access have to work hand in hand. Effective identity approaches focus on: - Keeping strong security controls in place, such as following [HIPAA rules](), using [granular access control](), and protecting against unauthorized access. - Making things easier for patients by relying less on passwords and making logins simpler, so fewer people give up trying to access care. - Using [risk-based MFA and security controls](), so extra verification is only needed for sensitive actions or when something unusual happens. - Designing systems for real-world use, like making sure they work well on phones, can be used on shared devices, and are easy for people with different levels of digital skills. - Making sure patients, staff, and partners across different clinics and programs can all access systems securely. - Supporting patient-authorized personal agents with limited, revocable permissions, clear consent, and audit trails that distinguish the agent from the patient. To put these ideas into action, CHCs should give clear setup instructions, help people use digital services, and check their authentication steps often to keep them secure and user-friendly. When CHCs balance strong security with easy-to-use design, they can grow their digital care options and keep trust, meet rules, and work efficiently. **Also Read: **[**How Collabrios Health Implemented Tenant-Aware Auth & SSO With Descope**]() ## Where Descope can help CHCs often need to modernize authentication without adding more complexity for already stretched IT teams. Implementing stronger security controls, improving patient access, and integrating identity across healthcare systems can quickly become difficult to manage with limited resources. Platforms designed for modern identity orchestration can help CHCs introduce secure authentication while simplifying operations. Descope helps healthcare organizations implement modern authentication in a way that improves access for patients while maintaining strong security and compliance. ![MFA Dark]() With Descope, healthcare organizations can leverage: - [**Passwordless authentication**]()**:** Supporting one-time codes, TOTP (which works without Internet access), magic links, and passkeys to reduce password friction and make it easier for patients to sign in. - [**Adaptive MFA**]()**:** Adding additional verification only when risk is detected, helping protect sensitive systems without introducing unnecessary login steps. - [**Visual authentication workflows**]()**:** Allowing teams to build and modify patient, staff, and partner login journeys without complex custom development. - [**Enterprise SSO**]()** and **[**role-based access management**]()**:** Providing secure access controls for clinicians, administrators, and other healthcare staff across systems. - [**SMART on FHIR support**]()**: **Handling user authentication, consent, and token issuance to enable healthcare applications to securely connect to EHR systems. - [**Flexible integrations**]()**:** Orchestrating data and actions from third-party products like CRMs, fraud tools, audit platforms, and email / SMS solutions with plug & play connectors. - **Tenant-aware B2B2X identity:** Supporting secure collaboration across partner clinics, community organizations, and healthcare applications while isolating access by organization or program. - [**Agentic Identity Hub**]()** and **[**Descope Envoy**](): Descope Agentic Identity Hub helps organizations manage AI agent identity, delegated authorization, and consent. Descope Envoy provides a secure way for personal agents to connect with applications and services. ![Healthcare federation image]() These capabilities help CHCs deliver secure and accessible authentication experiences that reduce barriers to digital healthcare while easing operational burden for internal teams. ## Accessible identity helps close the digital divide As healthcare moves online, authentication must reflect the realities CHCs serve, including shared devices, limited connectivity, and varying digital literacy. Traditional login systems often create barriers instead of access. Modern authentication helps CHCs improve access while maintaining strong security. Flexible, user-friendly identity reduces friction for patients, strengthens protection, and eases IT burden. Descope’s drag & drop [CIAM platform]() supports passwordless auth, mobile-first flows, and federated access across systems. Teams like [Collabrios Health](), [GoodRx](), [SmithRx](), and [Owens & Minor]() use Descope to improve onboarding, security, and reduce engineering effort. If you're evaluating healthcare-focused customer IAM platforms, [check out our docs](). If you'd like a demo, [meet with our auth experts](). Also, if you want to try Descope yourself, [sign up]() for a Free Forever Account and start dragging & dropping your auth today! ## FAQs for community health center auth --- ### [Identity Provider (IdP) Vendors for B2B SaaS: A Comparison](https://www.descope.com/blog/post/idp-vendors-b2b-saas-comparison) An identity provider buyers guide for B2B SaaS: the types of IdP vendors, what to evaluate, and how to choose an IdP for SSO, federation, and enterprise deals. *Full content: [https://www.descope.com/blog/post/idp-vendors-b2b-saas-comparison.md](https://www.descope.com/blog/post/idp-vendors-b2b-saas-comparison.md)* Most [B2B SaaS]() teams start shopping for an identity provider on the day a large customer asks for SSO. The search usually turns up two different categories of identity providers, which is part of why the shortlist takes so long to build. This comparison covers seven IdP vendors that B2B SaaS teams evaluate most often: Descope, Auth0, WorkOS, Frontegg, Amazon Cognito, Microsoft Entra External ID, and Keycloak. It starts with what “identity provider” means when your users belong to customer organizations rather than to you, then sets out the criteria that separate these vendors in practice, and compares each one against these criteria. ## At a glance - A B2B SaaS application is an identity provider to its own users and a service provider to each enterprise customer’s corporate IdP, and it has to do both jobs well. - Tenant model is the criterion to settle first, since a platform with native customer organizations handles SSO, roles, and provisioning very differently from one where you model tenancy yourself. - Self-service SSO setup decides whether enterprise onboarding is a task the customer completes or a standing cost on your engineering team. - Per-connection and per-MAU pricing produce very different bills for B2B products, so a few hundred enterprise tenants can cost more than the user count suggests. - Enterprise buyers are starting to ask how AI agents authenticate into B2B products, and agents need an identity model separate from the one built for human users. ## What “identity provider” means for a B2B SaaS application A B2B SaaS application sits on both sides of the [identity federation]() relationship. Your product is an [identity provider]() to its own users. It holds the accounts, issues the tokens your APIs validate, carries the claims your authorization logic reads, and owns the login experience your customers see. Whichever IdP vendor you use plays this role for you. Your product is also a service provider to each customer’s corporate IdP. An enterprise buyer that runs Okta, Entra, Ping, or Google Workspace expects your application to accept logins from them, honor the groups they send, and provision and deprovision users through SCIM when staff join or leave. The vendors below all do the first job, but they differ considerably on the second, which can be the difference between winning or losing enterprise deals. A platform that treats customer organizations as a first-class concept behaves differently from one where you model tenancy yourself on top of a flat user list. | **Type** | **What you get** | **Vendors here** | **Usually chosen when** | | --- | --- | --- | --- | | Full-stack CIAM | Authentication, the user store, tenancy, and enterprise federation in one platform | Descope, Auth0 | Identity is a continuing product concern rather than a one-time checkbox | | Enterprise feature layer | Enterprise SSO, SCIM, and admin tooling added onto an application, through APIs or drop-in components | Descope, WorkOS, Frontegg | Enterprise readiness is the gap and the rest of authentication is settled | | Cloud-ecosystem-native | Identity as a managed service inside a cloud platform the team already runs on | Amazon Cognito, Microsoft Entra External ID | The cloud standardization decision has already been made elsewhere | | Self-hosted open source | Source and deployment under your control, with operations as your responsibility | Keycloak | Control or data residency requirements outweigh operational cost | ## What to look for in B2B SaaS IdP vendors - **Tenant model:** Check whether customer organizations are a native primitive within the IdP, or whether [multi-tenancy]() is something you assemble from groups, metadata, and across separate user pools. This decision propagates into every other feature. - **Per-tenant enterprise SSO**: Support for [SAML 2.0]() and [OIDC]() is the baseline. The more pertinent question is whether each tenant can have its own connection, its own IdP—and in some cases more than one—without a code change on your side. - **Self-service SSO setup:** Check whether the customer’s IT admin can configure their own SSO connection, or whether your engineers need to run setup calls for every enterprise onboarding. This is the difference between SSO as a feature and SSO as a recurring support cost. - **User provisioning:** Check support for SCIM 2.0, just-in-time provisioning, and whether group and role mappings arrive with the user. - **Authorization scoped to the tenant:** IdP vendors catering to B2B SaaS must have [role-based access control]() that understands a user can hold different roles in different organizations, as well as fine-grained or [relationship-based authorization]() for products where permissions attach to individual resources. - **Delegated administration:** Check for capabilities like a hosted admin portal or embeddable components that let tenant admins manage their own users, roles, and audit logs. - **Compliance and deployment:** Check whether the vendor provides multiple data residency regions, self-hosting options, and add-ons such as FedRAMP if your product needs to serve government organizations or regulated enterprises. - **Agent access:** Enterprise customers are starting to ask how AI agents authenticate into your product and what those agents are allowed to do on a user’s behalf. The identity models built for human users do not transfer to agents, which need their own treatment around delegated access, scoped permissions, and credentials that expire. This is new enough that vendor capabilities vary widely and change quickly, so it is worth checking current state rather than relying on a comparison table. ## IdP vendors for B2B SaaS at a glance | **Vendor** | **Type** | **Tenant model** | **Self-service SSO setup** | **Ideal for** | | --- | --- | --- | --- | --- | | Descope | Full-stack CIAM with visual orchestration | Native tenants with per-tenant config | Yes, via SSO Setup Suite | B2B SaaS teams that need enterprise readiness and consumer-grade auth from one platform | | Auth0 | Established full-stack CIAM | Organizations layered on a core built for B2C | Partial, varies by tier | Teams prioritizing SDK breadth and ecosystem maturity | | WorkOS | Enterprise feature layer | Organizations as a core primitive | Yes, via admin portal | Teams adding enterprise SSO and SCIM to existing auth | | Frontegg | Embedded B2B identity components | Native multi-tenancy | Yes, via embedded admin portal | Teams wanting prebuilt B2B UI quickly | | Amazon Cognito | Cloud-ecosystem-native | User pools, tenancy modeled by the team | No | AWS-standardized teams with straightforward requirements | | Microsoft Entra External ID | Cloud-ecosystem-native | Directory-first | No | Organizations standardized on Microsoft | | Keycloak | Open source, self-hosted | Realms or groups, depending on approach | No | Teams with infrastructure capacity and strict control requirements | ## Descope Descope is a full-stack customer and agentic identity platform built with multi-tenancy as a first-class primitive that meets B2B requirements and consumer authentication needs from the same product. Tenants represent each customer organization and carry their own SSO connections, roles, permissions, and branding, with a single user able to belong to several tenants under different roles in each. Authentication journeys are built in Descope Flows, a visual workflow builder, which means changes to login logic, step-up conditions, or onboarding sequences generally do not require a release. ![Descope Flows homepage]() ### Key capabilities - Native[ tenant management]() with independent SSO, role, and identity provider configuration per customer organization. - The[ SSO Setup Suite](), which lets a customer’s own IT admin configure SAML or OIDC connections and SCIM provisioning without involving your engineering team. - [RBAC]() at project and tenant level, plus[ relationship-based access control]() for resource-level permissions. - Delegated administration through a hosted [admin portal]() and [embeddable widgets]() that run inside your own application. - [Descope Flows]() for building and changing authentication journeys visually, covering passkeys, MFA, step-up, and risk-based conditions - The [Agentic Identity Hub](), a separate identity model for AI agents built on delegated access, scoped permissions, and short-lived credentials - [Multi-region data residency]() across seven regions, with SOC 2 Type 2, ISO 27001, GDPR, and FedRAMP High authorization ![SSO Setup Suite IdP selection]() ### Strengths - Enterprise onboarding moves off the engineering backlog, since tenant admins configure their own SSO and SCIM. - One platform covers both the B2B requirements and consumer-grade authentication methods, so teams selling to businesses and individuals do not run two stacks. - Authentication logic lives in a visual flow rather than application code, which shortens the loop when a customer’s security review asks for a policy change ### Ideal for B2B SaaS teams moving upmarket who need enterprise identity features without dedicating engineers to identity infrastructure. It also suits companies selling to both businesses and individual users, since one platform covers tenant-aware B2B requirements and consumer authentication methods rather than two stacks running in parallel.[ Pricing]() starts with a Free Forever plan covering 7,500 monthly active users and 3 SSO connections, with paid tiers from $249 per month.  ## Auth0 Auth0, also known as Okta Customer Identity Cloud, is a long-established CIAM platform that lands on most B2B shortlists by default.  Its SDK coverage, documentation, and extensibility model through Actions are mature, and most engineering teams will find a published integration path for their stack. However, the platform’s core was designed around individual consumer users, with the Organizations feature added later to serve B2B, so multi-tenant requirements tend to sit on higher tiers and need more configuration than on platforms built as tenant-first. Monthly active user pricing can climb sharply as a B2B product’s seat count grows across its customer base. ![Auth0 Homepage]() ### Key capabilities - Organizations for modeling business customers, with per-organization connections and membership. - Broad SAML and OIDC federation support with a large catalog of social and enterprise connections. - Actions for injecting custom logic at points in the login pipeline. - Extensive SDK and quickstart coverage across languages and frameworks. ### Strengths - Extensive documentation and a large community knowledge base, which shortens troubleshooting. - Familiarity with security reviewers and procurement teams, which can smooth enterprise evaluations. - A mature extensibility model for teams comfortable writing and maintaining custom pipeline logic. ### Ideal for Teams that value ecosystem maturity and SDK breadth above tenant-model fit, and that have engineering capacity to configure and maintain B2B structures on top of the platform. ## WorkOS WorkOS is an enterprise feature layer for B2B SaaS, centered on the specific capabilities that enterprise buyers demand. Enterprise SSO, Directory Sync for SCIM provisioning, and audit logs are the core products, with AuthKit extending into user authentication and prebuilt UI. The admin portal is a strong piece of the offering, giving customer IT admins a self-service path to configure their own connections. The commercial model prices enterprise SSO per connection, which is predictable at low tenant counts but becomes a meaningful line item for products with many enterprise customers. Teams looking for a single platform to cover consumer-grade authentication methods, visual journey orchestration, and fine-grained authorization will generally need to assemble those pieces around WorkOS. ![Fig: WorkOS homepage]() ### Key capabilities - Enterprise SSO across SAML and OIDC with a hosted admin portal for customer-led setup. - Directory Sync for SCIM provisioning from the customer’s identity provider. - Audit logs formatted for enterprise compliance requirements. - AuthKit for user authentication and prebuilt login components. ### Strengths - A short path to a working enterprise SSO integration, which is part of its appeal to early-stage B2B SaaS teams. - The admin portal removes engineering from most enterprise onboarding conversations. - Clear, narrow product scope that is easy to evaluate and easy to explain internally. ### Ideal for B2B SaaS teams that already have authentication they are happy with and need to add enterprise federation and provisioning on top of it, particularly earlier-stage companies with a small number of enterprise tenants. ## Frontegg Frontegg provides embedded identity components aimed specifically at B2B SaaS, with prebuilt login widgets, an admin portal, and multi-tenancy included. The appeal is speed. A team can drop in login, user management, SSO, MFA, and role assignment as components rather than building those surfaces. The tradeoff is that the components are opinionated, and teams that need authentication logic to diverge from the supplied patterns have fewer levers than a visual orchestration model provides. Teams with requirements around fraud prevention or account takeover protection will typically look to add a separate layer. ![Fig: Frontegg homepage]() ### Key capabilities - Embedded admin portal and login components designed for B2B tenancy. - Multi-tenancy with per-tenant SSO, MFA, and role configuration. - Self-service user and role management for customer admins. - RBAC for tenant-scoped permissions. ### Strengths - A quick route to a complete B2B identity surface, including the admin experience. - Multi-tenancy is native rather than modeled on top of a flat user store. - Reduces the amount of identity UI a product team has to design and maintain. ### Ideal for B2B SaaS product teams that want a complete, prebuilt identity experience quickly and are comfortable working within the patterns the components provide. ## Amazon Cognito Amazon Cognito is AWS’s customer identity service, usually adopted because a team has standardized on AWS rather than because of an identity-led evaluation. It handles core authentication at low cost and integrates cleanly with the rest of the AWS stack. For B2B, the structural question is user pools. Separating customer organizations means either many pools or modeling tenancy in attributes, with both approaches pushing complexity into application code. Customizing journeys relies on Lambda triggers, so changes to login logic are engineering work, and there is no built-in self-service path for a customer’s IT admin to configure their own SSO connection. ![Amazon cognito homepage]() ### Key capabilities - User pools and identity pools with SAML and OIDC federation. - Native integration with AWS IAM and the broader AWS service set. - Lambda triggers for customizing points in the authentication lifecycle. - Low per-user cost at high volumes. ### Strengths - Predictable cost at scale for teams already operating in AWS. - Infrastructure and billing stay inside an existing vendor relationship. - Adequate for straightforward authentication requirements without heavy B2B structure. ### Ideal for Teams deeply standardized on AWS with simple tenancy requirements and engineering capacity to build the B2B layer themselves. ## Microsoft Entra External ID Entra External ID is Microsoft’s customer identity offering and the successor path for teams on Azure AD B2C. Organizations already running Microsoft across their stack will find procurement and security review straightforward, and federation with Entra tenants on the customer side is well-trodden. However, the architecture is directory-first and built originally for workforce identity, which adds friction to several common CIAM requirements. Per-tenant branding, journey customization, and the developer experience around custom policies are the challenging areas teams most often cite during evaluation. ![MS Entra External homepage]() ### Key capabilities - Federation across SAML and OIDC, with strong alignment to Microsoft identity sources. - Custom policies for extending authentication journeys. - Conditional access concepts carried over from the workforce product. - Integration with the wider Entra and Azure administrative tooling. ### Strengths - Minimal friction when the buyer and the customer base are both Microsoft-standardized. - Backed by Microsoft’s compliance and regional infrastructure footprint. - Consolidates vendor relationships for organizations already licensing Entra. ### Ideal for Organizations committed to the Microsoft ecosystem whose customer identity requirements stay close to what the directory model handles natively. ## Keycloak Keycloak is an open-source identity and access management project maintained by Red Hat, and teams run it on their own infrastructure. It implements auth standards thoroughly, supports SAML and OIDC federation, and gives a team complete control over where identity data lives and how the system behaves. There is no license cost, which is usually what puts it on the list. The cost moves to engineering instead. Teams running Keycloak in production report meaningful effort around scaling, upgrades, and the admin experience. Realms are the closest fit for modeling tenants, and they get harder to manage as the number of customer organizations grows. ![Keycloak homepage]() ### Key capabilities - Full SAML 2.0 and OIDC support, including identity brokering to external providers. - Realms for isolating configuration, commonly used to model tenants. - Extension points through service provider interfaces and custom authenticators. - Complete control over deployment location and data handling. ### Strengths - No license cost and no vendor dependency on the identity layer. - Deployment anywhere, which satisfies strict residency or air-gapped requirements. - Standards coverage that is thorough enough to handle unusual federation requirements. ### Ideal for Teams with infrastructure engineering capacity, strict control or residency requirements, and tolerance for owning upgrades and operations. ## Choosing between IdP vendors for B2B SaaS Most shortlists get shorter once your requirements are clear. - If enterprise SSO and SCIM are the gap and your existing authentication works, augmentation-friendly layers like Descope or WorkOS address that directly. - If you need B2B structure and consumer-grade authentication methods in one platform, a full-stack CIAM like Descope or Auth0 is a closer fit. - If prebuilt B2B UI is the priority and the supplied patterns match your product, Frontegg and Descope get you there quickly. - If your main constraint is ecosystem standardization, Cognito or Entra External ID will be easier to get approved internally, though you will do more work to adapt them to B2B requirements. - If control over infrastructure matters more than operational cost, Keycloak is the option. Run the pricing model against your actual tenant count before deciding on an IdP vendor. A product with many enterprise customers and moderate user volumes is affected far more by per-connection SSO pricing than by MAU tiers. ## Conclusion The IdP comparison that matters for B2B SaaS comes down to a few structural questions. Are customer organizations a native concept or something you build? Can a customer’s IT admin configure their own SSO connection? Does authorization understand that a user holds different roles in different tenants? Does the pricing model match the shape of your customer base? Descope was built to answer these questions for B2B SaaS applications. Tenants carry their own SSO, roles, and branding, the SSO Setup Suite hands enterprise onboarding to the customer’s own admins, RBAC and relationship-based access control operate at tenant scope, and Descope Flows keeps authentication logic out of application code. For teams whose customers are asking about AI agent access, the Agentic Identity Hub provides a separate identity model for agents. [Sign up for a Free Forever account]() to build a tenant-aware login flow, read the[ B2B use case documentation](), or[ book a demo]() with our auth experts to walk through your tenant model. ## FAQs about IdP vendors for B2B SaaS --- ### [Nine Top Workplaces Awards and What Descopers Told Us About Our Culture](https://www.descope.com/blog/post/top-workplace-awards) Descope won nine 2026 Top Workplaces awards from Energage. Our Head of People and Talent shares what culture means at Descope, in our employees’ own words. *Full content: [https://www.descope.com/blog/post/top-workplace-awards.md](https://www.descope.com/blog/post/top-workplace-awards.md)* Hello Descopers! I’m happy to share that Descope has won nine 2026 Top Workplaces awards from [Energage](). These include a Top Workplaces Industry award for Technology and eight Culture Excellence awards: Leadership, Purpose & Values, Innovation, Professional Development, Work-Life Flexibility, Employee Well-Being, Compensation & Benefits, and Employee Appreciation. You can read the full announcement [here](). What makes these awards special is where they come from. Every Top Workplaces award is based on an anonymous survey of our own employees. Our overall Workplace Experience Score came in at 96%, 11 points above Energage benchmarks. So before anything else, thank you to every Descoper who took the time to answer honestly. This recognition belongs to you. ![Descope SKO 2026]() In this post, I’ll share how I think about culture at Descope, then let our employees do most of the talking. Their words come from two places: our *Meet a Descoper* interview series and the anonymous comments they left in the Top Workplaces survey. I’ve grouped them by the four guiding principles listed on our[ About page](). And if what you read sounds like a place you’d want to work, our[ careers page]() is a good next stop. ## Culture starts at the top Culture is one of those words we throw around a lot in the HR world. I’ve always believed that a company’s DNA starts at the top—from the founders who build the foundation, to the leaders, and eventually to every single employee. At Descope, we have eight founders who are accessible, authentic, and present. They lead with care, humor, and humility, and they care about the people, the business, and everything in between. Nobody is sitting in a golden tower disconnected from everyone else. There’s a real connection between our founders, leaders, and employees, and I think that’s something pretty special. I don’t believe you can manufacture that kind of culture. So many companies try to create it through perks, programs, and initiatives. There’s nothing wrong with those, but they should add to a culture, and they can’t stand in for one. We trust our people, we listen to them, we laugh with them, and we treat them like people who have a life outside of work. To me, culture isn’t what you tell your employees you are. It’s what they experience every single day. Here’s what they told us they experience. ## Build in public Our first principle reads: “We don’t like black boxes and ivory towers.” Internally and with our users, we try to be open about what we do well and where we can do better. For me, this is also where psychological safety lives. We don’t sugarcoat things or tell people what they want to hear, and welcome healthy disagreements. When people feel safe enough to be themselves, even when they disagree, that’s when you build real trust. ![MCP Hackathon Pic]() Our employees noticed: “I am appreciative of how the leadership keeps the company up to date about the business. After every board meeting, the board deck is presented verbatim to the rest of the company.” - *Descope employee, 2026 Top Workplaces survey* “Easy to connect with the founders/execs and learn about the business; at previous roles I felt like a nobody in terms of relationships with people who make the decisions.” - *Descope employee, 2026 Top Workplaces survey* “Managers ask for pushback directly and actually change course when someone makes a good case. Since we talk openly about what’s working and what isn’t, disagreeing feels like part of the job, not a risk.” - *Descope employee, 2026 Top Workplaces survey* “Leadership is open and accessible, so pushing back doesn’t feel risky. Ideas get judged on their merits, not on who said them.” - *Descope employee, 2026 Top Workplaces survey* [Asaf Shen](), one of our developers, put it this way in his Meet a Descoper interview: “Dev teams that are working towards a shared goal need to always be communicating, debating, having healthy conflicts, and trusting each other to move in the same general direction even when we don’t agree completely on the exact approach sometimes.” ## Ship fast and slow We bring products and features to market quickly, but without taking shortcuts on critical aspects like security or reliability. Inside the company, that shows up as ownership. People are trusted to spot a problem and fix it without waiting for permission, and they’re held to a high standard while doing it. ![Drag and drop your view]() “We move fast... I can see the impact that we make with my customers. There’s a lot of ownership here. If I see a better way to do something, I’m trusted to run with it instead of waiting for permission.” - *Descope employee, 2026 Top Workplaces survey* “The pace. We ship quickly, customers notice, and I can see the effect of my work within weeks, not quarters. It also helps that the product is something I can stand behind when I talk to customers.” - *Descope employee, 2026 Top Workplaces survey* “Working with people who are smart and still easy to ask for help. Nobody hides behind titles... I’ve been trusted with real responsibility, and that’s pushed me further than I’d have gone somewhere bigger and slower.” - *Descope employee, 2026 Top Workplaces survey* [Chris Carper](), our Head of Customer Success, described the same freedom: “If something needs to be done and someone has an idea, they have the freedom to implement it.” He saw that customers moving from other authentication providers needed a migration plan, so he built one. In his words, “I took on the project because we didn’t have it and led it to completion because we needed it.” ## Every customer matters Serving customers is why we exist, and our employees feel close to the impact of their work. Senior Solutions Engineer [Steven Barash]() describes “being the voice of the customer back to product” as “a hidden part of the SE role.” When he noticed customers manually tidying messy flows, he mocked up a fix and brought it to the product team, and it’s being implemented at the time of writing. ![Working at SKO optimized]() I’d add that the same principle applies to how we treat each other. Every Descoper is slightly different, with their own life, schedule, and needs, and we try to meet people where they are. “The focus is on outcomes, not hours. As long as I’m delivering, I have the flexibility to structure my day in a way that works for my life.” - *Descope employee, 2026 Top Workplaces survey* “Recognized for my birthday. When food arrangements are made, concern and thought are put into my allergens, etc. I definitely feel like I am one person in the org, not just a cog in the machine or a face in the crowd.” - *Descope employee, 2026 Top Workplaces survey* “Off-boarding an employee was handled with grace and compassion.” - *Descope employee, 2026 Top Workplaces survey* That last one means a lot to me. How a company treats people on the way out says as much about its culture as how it treats them on the way in. ## Embrace the espresso Our mission is ambitious, and we intend to have fun along the way. You’ll meet high-energy people here who enjoy solving big problems. (We also really like coffee.) ![Coffee]() “I get to work with some really funny, smart, and hardworking people, on a global and diverse cross-functional team. People treat each other like family, and there’s deep trust built into each day we work together.” - *Descope employee, 2026 Top Workplaces survey* “The people are incredibly fun to work with and it feels like everyone is on the same team. For a 100+ remotely distributed company, that is very hard to find.” - *Descope employee, 2026 Top Workplaces survey* “In various official and unofficial ways. Hackathons, spontaneous ideas, permission to work on side projects, etc.” - *Descope employee, 2026 Top Workplaces survey, on how Descope encourages new ideas* [Itai Hanski]() summed it up in his interview: “I love how work and fun truly happen side-by-side here.” ## Where we’re still growing Are we perfect? Definitely not, and I don’t think we should pretend to be. The survey gave us clear feedback here too. Descopers asked for more structure, including a more regular cadence for performance feedback and more processes documented instead of passed along as tribal knowledge. Some also described the growing pains that come with working at a startup. ![Slavik Vision Pro]() That’s a natural part of progressing as a company, and we’re working on it. Processes can be built and structures can be improved. The connection, trust, and care we have for our people are much harder to build, and even harder to bring back once they’re gone. As we grow, my job is to make sure we keep them. ## Join us Thank you again to every Descoper who took the survey, and to the founders and leaders who make this culture real every day. These nine awards are a reflection of you. If you’d like to experience it for yourself, check out our open roles on the[ careers page](). --- ### [This Holiday Season's Busiest Shoppers Might Not Be Human](https://www.descope.com/blog/post/ai-shopping-agents-holiday-season) Retailers should prepare to accept AI shopping agents this holiday season. See how to verify agents, get customer approval, and prevent chargeback disputes. *Full content: [https://www.descope.com/blog/post/ai-shopping-agents-holiday-season.md](https://www.descope.com/blog/post/ai-shopping-agents-holiday-season.md)* I can't stand shopping on a normal day. The idea of shopping in person during the holiday rush sounds horrendous. No deal could possibly sway me to head out to the malls. The crowded parking lots. The lines out the door. The hordes of people. Hard pass. I will admit, online shopping is much better but also has its challenges. The dozen or more browser tabs I end up opening just to figure out whether a "deal" is actually a deal still feels like homework and too much screentime. That's exactly why personal AI agents caught my attention. The idea of telling an agent "find gifts for my list under $100 each and check with me before you buy" and then getting on with my day sounds like the version of holiday shopping I've always wanted. I don't think I'm alone, either. There are a lot of people like me who would happily hand the gruntwork out to an agent. Meta Muse has already [reportedly passed 5 million downloads just 22 days after launch](). AI agents are projected to power $3–5 trillion in commerce transactions by 2030. These early numbers suggest plenty of people agree. But when you talk with retail and eCommerce teams, you keep hearing the same question: *"What do we do when these agents show up at our login page?"* Here’s what I’ve come to realize, and why I believe this holiday season is when retailers need to stop seeing this as a problem for the future. ## Two bad options at the door To meet the oncoming increase in agentic usage, retail teams are quickly doing one of two things today. I understand why. Neither is ideal; they're just the most expedient and frictionless for the retailer when a sign-in page built for humans meets a shopper that isn't one. ![Shopping agents two buttons]() **Option one:** block the agent. It might seem like the safe choice. But the customer won’t stop shopping just because their agent can’t get in. The agent will just go to a competitor that allows it, and you lose the sale during your busiest season. Even worse, you’ve shown that customer’s agent your store isn’t worth trying again. **Option two:** let the agent sign in as the customer. This might feel like a win because the order goes through. But now your systems can’t tell the difference between the agent and the person. Every search, cart, and checkout looks like it came from the customer. That works until something goes wrong. ## The January hangover: "I didn't order that" Picture the second week of January. Returns are piling up, credit card statements have arrived, and a customer calls your support line: "I didn't order that." Maybe the customer didn’t place the order. Maybe their agent did exactly what it was told, and the customer forgot. Or maybe the agent misunderstood the request. Or maybe it wasn’t their agent at all. The problem is your logs can’t tell which is which, because the agent signed in as the customer. To your systems, they look the same. Letting agents sign in as users doesn't just create one bad support call. It creates chargebacks you can't contest, frustrating support conversations, and stresses fraud models trained on inaccurate signals. Every agent order that looks human makes it more difficult to spot the orders that aren't legitimate. The solution is to record delegation clearly. Every token and log entry should show the customer *and* the agent as separate identities. When that January call comes in, your team can see exactly who did what and who approved it. The support conversation then changes from "we'll look into it" to "here's what happened." ## A better front door for agent shoppers Choosing between blocking agents or pretending they're human is not the answer. The best option is to let agents in as themselves but on behalf of humans. When it comes to retailers being prepared and secure for agent-ready sign-in needs, here are are four pillars: - **Identify. **Every agent names itself, so you know which agent is at the door before you give it a session. - **Consent.** The customer has consented to each agent that acts on their behalf. - **Scope.** A shopping agent can browse the catalog and place orders, while payment methods and account settings may be off limits. - **Governance.** You can block any agent or revoke its access without signing the customer out or locking up their account. Imagine it’s the holiday shopping season. It's 11 p.m. in mid-December, the last shipping cutoff before Christmas is tomorrow, and a customer's agent finds the gift sold out for weeks back in stock. Instead of checking out on its own, the agent holds the item and sends the product, price, and delivery date to the customer's phone. The customer taps “approve” on their own device, outside the agent's session, and goes to bed knowing the gift will arrive on time. Take the scenario further. If the order ships and the customer later questions it, you have a clean record of who asked, who approved, and who checked out. That's the scenario every retailer should get ready for this season: the agent finds the gift, the customer stays in control, and the retailer keeps both the sale and the paper trail. ## Keep the sale and the audit trail This is why I'm excited about what we’ve built with [Descope Envoy](). It gives personal agents their own front door without asking you to rip out your existing auth stack. It's built on standards the industry already trusts (OAuth 2.1, [CIBA](), [Device Code](), and RAR), and it supports [Poppy](), the new Personal Agent Protocol that gives agents a standard way to discover your site and start a session. In other words, you're not betting on a proprietary approach. You're getting ahead of where the whole industry is heading. [Descope Envoy Launch]() The retailers who come out ahead won't be the ones that block agents, and they won't be the ones that look the other way either. They'll be the ones that can answer three questions about every agentic order: which agent placed it, who it was acting for, and what permission it had. If you're not sure your store can answer those yet, we at [Descope would love to talk](). There's still time before the January hangover. --- ## Customer Stories ### [Different Customer Story | Descope](https://www.descope.com/customers/different) Learn how Different built enterprise-ready identity on Descope so its lean team could focus on building an AI marketing system. *Full content: [https://www.descope.com/customers/different.md](https://www.descope.com/customers/different.md)* [*Different*]()* is an AI marketing system that lets lean B2B teams run demand generation at the scale of much larger organizations. Selling to businesses with strict requirements meant Different needed enterprise-grade identity from the start, while building a novel product with a vast surface area. Here’s how Descope helped them do both.* --- ## About Different Marketing teams use Different to plan B2B campaigns across channels, with Different building the emails, ads, and landing pages that run those campaigns. The company’s promise is that a marketing team of five can do the work of 50.  Different was built AI-native from day one, with no assumptions about how marketing workflows traditionally run. That puts the product at the center of customers’ campaigns and marketing data. For the B2B companies Different works with, that level of access raises the bar on security. Abhinav Yajurvedi, Co-founder and CTO at Different, said: > "Organizations are very sensitive about the security posture of the products they bring into their business, especially in the AI era. Before you even enter the product, you touch identity, so it was one of the first things we had to get right." ## The challenge of enterprise identity with a lean team The engineering team at Different had already written some identity abstraction of their own and weighed open-source options. Two requirements materialized that made standing up in-house [B2B CIAM]() hard to justify: - **Enterprise SSO for every customer:** Customers of Different sign in through their own identity providers (IdPs), and supporting each one in-house would mean building and maintaining a growing list of integrations - **Authorization with room to grow:** Different needed roles and permissions that could start simple, then expand as the product took on more complex use cases Abhinav Yajurvedi, Co-founder and CTO at Different, said: > "When we were starting out, the team was small and the surface area of the product was huge. Identity is critical, but it sits outside the core of what we build, so we wanted a partner who could own it while we focused on the product." ## The Descope experience Different evaluated several identity providers before choosing Descope. Their decision-making philosophy was the same as it was for any other part of their stack: favor responsive, developer-first companies that are easy to build with and open to feedback. As an agile, AI-forward organization, they prioritized an identity partner that could match their pace of innovation and offer rapid support. The integration took about a month, with Descope's support team available throughout. The Different login page runs on [Descope Flows](), and prebuilt [user widgets]() and [admin widgets]() gave Different a working identity experience without needing to build core elements from scratch. Because the login experience lives in a Flow, Different can easily change identity journeys in a visual editor without touching application code or redeploying.  **Read more: **[Choosing the Right Descope UI Integration Option]() Today, users of Different sign in with [enterprise SSO]() through their organization's identity provider or with [social login](), so there are no passwords to manage. New SSO connections go through the [SSO Setup Suite](), which walks through the configuration for any identity provider, maps attributes, and tests the connection before it goes live. The Different team can pre-configure part of a connection and hand the rest to the customer’s IT admin, with no coordination calls. Different plans to begin using the Suite’s fully self-service option in the future. Each Different customer is its own tenant, and inside it, Descope handles [role-based access control (RBAC)](), with super admin, admin, and user roles today, and an abstraction designed to take on more complex roles as they’re needed. Descope's [user impersonation]() allows the Different team to easily diagnose hard-to-reproduce auth issues by seeing exactly what that customer sees, gated behind authorization checks and an approval step. Since the successful integration, Different has explored everything from [relationship-based access control (ReBAC)]() to [Model Context Protocol (MCP)]() identity flows. Each time, Descope's team has been on hand to support them. ## Enterprise-ready identity from day one With Descope handling identity, Different’s engineers don’t have to second-guess whether their auth system will stand up to an enterprise customer’s security review. Their time is focused on refining their AI marketing offering. Abhinav Yajurvedi, Co-founder and CTO at Different, said: > “Identity is one of the most underrated parts of any product. It’s a solved problem, but you have to solve it again for every new business, and each one brings its own nuance. Having a partner flexible enough to take on our requirements while taking away the tension around security is a huge relief.” As an AI-native company, Different is already exploring what comes next, from [agentic identity]() to [finer-grained access](), as the product grows into a full AI marketing system. Descope provides the tools to cover their next auth leap, and has already laid the groundwork for consistent iteration: access keys share the same JWTs and RBAC policies as user sessions, so Different test users and other non-human identities follow the same rules as everyone else. Different promises marketers that a small team can do the work of a much larger one. With Descope addressing their identity challenges, the Different engineering team gets to work the same way. --- Descope is a flexible [drag & drop customer and agentic identity platform]() that helps organizations easily add authentication, authorization, and identity management to their apps, AI agents, and MCP servers. Customers use us for initiatives such as [passwordless authentication](), [SSO](), [identity federation](), [strong MFA](), [fraud prevention](), and [agentic identity](). To get started with Descope, [sign up for a Free Forever account](). If you have questions about our platform, [book time with our auth experts](). --- ### [Limy Customer Story | Descope](https://www.descope.com/customers/limy) Learn how Limy built with Descope from day one: startup-friendly pricing for multi-tenancy and passwordless login, with MCP auth live in under a week. *Full content: [https://www.descope.com/customers/limy.md](https://www.descope.com/customers/limy.md)* **[*Limy*]()* helps brands turn AI search into a measurable growth channel for pipeline, customers, and revenue, and lets its users query that data from AI assistants like Claude and ChatGPT. Here’s how building on Descope from day one gave Limy a single identity model for both users and agents, with MCP auth in production in under a week.* --- ## About Limy Limy addresses the reality that AI agents are becoming the new interface between brands and their customers, a shift known as business-to-agent (B2A). When a prospect asks an AI assistant for a recommendation, the assistant decides which brands are shown, in ways traditional search engine optimization (SEO) tooling wasn't built to measure. Limy helps brands understand how they appear in AI search, identify and prioritize the improvements that matter most, and measure the business impact of those changes. The Limy platform shows brands how agents like ChatGPT, Claude, Gemini, and Perplexity crawl their sites and cite their content, and uses those insights to guide improvements. It then connects AI search visits to tracked actions and conversions, including pipeline and revenue where supported. Limy’s customers are enterprise brands and the agencies that manage several brands at once. A single Limy user may work across many different accounts for companies that may even compete with each other. Keeping each brand’s data isolated is fundamental to the product, especially within the [Model Context Protocol (MCP)]() server that allows users to query Limy from their own AI clients. ## The challenge of choosing identity on day one Limy chose Descope just as they were bringing their product to market, with two requirements clear at the outset:  - Each customer organization would get its own discrete account, with firm boundaries between each - The Limy MCP server would eventually let users authorize AI agents to act on their behalf, so the same boundaries would have to hold for agents, too While Descope’s [Free Forever Plan]() provides 10 monthly active tenants free of charge, Limy needed larger-scale [multi-tenancy]() at a startup-friendly price. Descope’s [Startup Program]() was the perfect fit: one year of the Pro tier, free of charge, while Limy built their customer base. Limy stuck with Descope and moved to a paid plan, and then clients began asking for [single sign-on (SSO)]().  Arad Gonen, Software and DevOps Engineer at Limy, said: > "We're starting to explore SSO because our new enterprise customers require it, and Descope makes that really easy. You get a self-service link you can send to a client, they configure [SAML]() on their own, and it simply works. I've worked with other auth providers in the past, and it wasn't that easy." ## The Descope experience Limy had the first login flow working within a couple of days, built from [Descope’s SDK](), [docs](), and [tutorials]() without any hands-on help. Limy went [passwordless]() from the start, so users sign in with a [magic link](), [one-time password (OTP)](), or Google account via [social login](). That leaves Limy with zero [passwords]() to store or reset, and it gives their users one less password to worry about. Descope issues the session tokens behind Limy’s web app and secures access to the Limy API. ![Limy Login Page]() Each Limy client is its own Descope tenant with its own users, with a [role-based authorization (RBAC)]() policy applied inside each one. Descope’s [prebuilt admin widgets]() handle tenant user management out of the box, and (after experimenting with the prebuilt options) Limy used the Descope SDK to build the same experience in its own design language. **Read more: **[Choosing the Right Descope UI Integration Option]() With user login and multi-tenancy configured with Descope, the next step was securing the Limy MCP server. The [Agentic Identity Hub]() allows Limy to point Descope at its MCP server’s URL and metadata, and Descope acts as the [OAuth authorization server]() required by [the MCP auth specification](). The authentication piece took the Limy team roughly half an hour, and (after a two-day proof of concept period and a couple more days of tuning), the MCP server was in production in under a week. Arad Gonen, Software and DevOps Engineer at Limy, said: > "It was really a no-brainer to use Descope’s agentic identity features. We configured the authentication part of our MCP server with Descope, and it was just 30 minutes before it was working.” Because an agent gets its access through the user who authorizes it, the boundaries Limy set for humans extend to the agents acting for them. A marketer who connects Claude is redirected to Descope to sign in, and the accounts that user can access carry through the MCP server into Limy’s API. An agent can reach the accounts its user can access, and it can’t touch anything in another brand’s account. The Limy MCP server is read-only for now; making each user’s full per-tenant roles available through it, along with write actions, is next. AI clients register using [Client ID Metadata Documents (CIMD)](), the approach the MCP spec now favors, in which each client identifies itself with a URL pointing to metadata it publishes. Nobody has to create credentials by hand before connecting, and because Descope supports CIMD alongside [Dynamic Client Registration (DCR)]() and pre-registration, Limy can accommodate clients with legacy requirements. ## Room to grow, minus the paywalls Whenever Limy has needed a new identity capability, whether it’s enterprise enablers like SSO or core AI scaffolding like MCP auth, their team found it already available in Descope without a premium markup. Building on this comprehensive foundation has given Limy: - **MCP auth in production at startup speed:** Configuring authentication took half an hour, and the rest came within a few more days. MCP was always a part of Limy’s vision, and Descope is how they handle [MCP identity orchestration](). - **One set of boundaries for both users and agents:** Users are bound by the tenant they’re logged in to and the role they have; agents are scoped to the user’s account, so Limy never has to [design a separate access model for them](). - **Self-service SSO for clients that need it: **As Limy prepares SSO for its first clients, they look forward to using the [SSO Setup Suite](). This powerful self-service workflow lets Limy’s tenants [configure their own SSO connections](), allowing the Limy team to focus on core engineering priorities. Arad Gonen, Software and DevOps Engineer at Limy, said: > "Overall, the experience with Descope has been one of the best I've had with any SaaS platform. Everything is available, and you can grow with your plan. You don't need to talk to sales to enable SSO or add more tenants. It just works." The next steps for Limy are adding write actions to the MCP server, bringing more agentic features into the platform. Descope will handle authorization for the agents that arrive, shaping their paths even as static roles evolve into [fine-grained relationships](), with first-class [agentic identities]() governed by the same boundaries as their human users. --- Descope is a flexible [drag & drop customer and agentic identity platform]() that helps organizations easily add authentication, authorization, and identity management to their apps, AI agents, and MCP servers. Customers use us for initiatives such as [passwordless authentication](), [SSO](), [identity federation](), [strong MFA](), [fraud prevention](), and [agentic identity](). To get started with Descope, [sign up for a Free Forever account](). If you have questions about our platform, [book time with our auth experts](). --- ### [REVO Insurance Customer Story | Descope](https://www.descope.com/customers/revo-insurance) Learn why REVO Insurance moved its broker and agent logins off Keycloak to Descope to enable unified auth journeys without writing custom code. *Full content: [https://www.descope.com/customers/revo-insurance.md](https://www.descope.com/customers/revo-insurance.md)* **[*REVO Insurance*]()* is one of Italy’s most innovative and technology-forward insurers, covering specialty business risks for small and medium companies. With their developers focused on refining their own core products, an identity surface spanning two systems became too much work to maintain. Here's how Descope helped REVO move its broker and agent logins off Keycloak, add a simple and secure MFA layer for customer verification, provide a single portal for accessing all applications, and put a lean team in control without having to write a single line of code.* --- ## About REVO Insurance REVO Insurance is an Italian insurer built around specialty lines of coverage, addressing risks that don't fit traditional policies. Its primary customers are small-to-medium businesses and professionals with non-standard, niche, or specific commercial risks (like agriculture, surety bonds, marine, aviation, and financial lines) rather than mass-market personal insurance. REVO sells through a network of brokers and agents, and they run more of their own underwriting and claims on in-house technology than most insurers of a similar size. That distinct model shapes REVO’s unique identity needs, especially when it comes to *who* is logging in with one of their channels. These users include two main groups: - Direct employees of REVO Insurance - Brokers and agents who sell REVO policies REVO wanted to add stronger auth for their employees while simplifying and modernizing their agent logins. The team that owned identity was skilled yet lean, which meant the solution needed to address the engineering burden without adding extra complexity. ## The maintenance challenge with open-source identity REVO ran employee login on Microsoft Entra and put[ Keycloak]() federation in front of the access its brokers and agents used to reach REVO's internal applications. The Keycloak side posed challenges across three fronts: - Using the open-source solution resulted in a federation setup that was expensive to run. - Any changes, fixes, or upgrades leaned heavily on DevOps work handled by a team with other priorities. - It was hard to introduce new functionality, protocols, and integrations with other tools. That was a high cost for a team that valued agility. Because of Keycloak’s DIY nature, even a small change could mean pulling in developers with non-identity priorities and waiting until they had the cycles to address it.[ Descope research]() shows this is a common challenge across all organizations: 46% postponed CIAM improvements to deal with other pressures, while 37% delayed engineering roadmaps to address auth gaps. Fabio Spagnuolo, IT Security Operations Manager at REVO Insurance, said: > "Even the most capable engineering team has bandwidth limits. We needed to be able to elevate security, add new options and build or change a login flow quickly, without pulling developer focus from our core product.[ Descope Flows]() made that possible." ## The Descope experience Descope offered REVO the flexibility their experienced engineers valued while saving precious cycles that would’ve been spent manually writing auth logic. REVO’s Descope deployment would also augment their employee Entra logins within the same solution, consolidating internal and external broker auth. - **Moving broker login off Keycloak.** Descope fully replaced the Keycloak federation the brokers and agents used to reach REVO's applications. A one-time scripted migration moved the users over in a single pass, carrying their custom attributes, application assignments, and roles, while preserving existing custom attributes and the underlying attribute-based access control (ABAC) and  [role-based access control (RBAC)]() models. - **A portal the security team runs.** Brokers and agents now sign in and land in Descope's[ Applications Portal Widget](), which REVO customized heavily to match its own branding. They replaced access screens REVO would otherwise have had to build and maintain. REVO configures the portal and the login flows behind it without needing to write code. Descope shipped features to meet REVO’s specific needs, including support for multiple domains on a single project, and portal access for users outside standard tenant structure. Building in Descope Flows also let REVO move logic that used to run as external calls directly into the login journey, allowing them to iterate in-house. ## Strong identity without dev overhead REVO's Descope implementation delivers a solution with less overhead, more agility, and MFA augmentation included under the same roof: - **Less to maintain:**[ Moving off Keycloak]() eliminated the DevOps upkeep, freeing their team to focus on refining rather than catching up with identity needs. - **A more agile identity solution:** With no-code Flows and the portal widget, REVO quickly builds and adjusts login journeys and access screens instead of waiting on borrowed engineering time. Fabio Spagnuolo, IT Security Operations Manager at REVO Insurance, said: > "Even small changes to our identity setup used to take more time and effort than we wanted. Descope lets us tweak the screens our agents land on, and the flows behind them, in an afternoon." --- Descope is a flexible [drag & drop customer and agentic identity platform]() that helps organizations easily add authentication, authorization, and identity management to their apps, AI agents, and MCP servers. Customers use us for initiatives such as [passwordless authentication](), [SSO](), [identity federation](), [strong MFA](), [fraud prevention](), and [agentic identity](). To get started with Descope, [sign up for a Free Forever account](). If you have questions about our platform, [book time with our auth experts](). --- ### [ProductNow Customer Story | Descope](https://www.descope.com/customers/productnow) Learn how ProductNow migrated to Descope, secured its MCP server for AI clients like ChatGPT, and reached production in three days. *Full content: [https://www.descope.com/customers/productnow.md](https://www.descope.com/customers/productnow.md)* **[*ProductNow*]()* builds a context engine for enterprise AI, turning the disparate details scattered across a company's different channels into one governed source of truth. As ProductNow moved upmarket, its identity provider ballooned from a simple renewal into a blocker. Here's how Descope helped ProductNow migrate, secure its MCP server, and enter production within three days.* --- ## About ProductNow ProductNow's platform continuously pulls context from the systems a company runs, resolves conflicts, and serves the results to agents so they can take governed actions. That focus on agentic context places ProductNow firmly in one of the most contested layers of the AI marketplace. Context engines have become a discrete category in this space, with time-to-market quickly becoming a major differentiator. For small teams like ProductNow, outperforming large competitors means both being the better option and getting there faster. Teams can use ProductNow from Slack and Microsoft Teams, or from AI clients like ChatGPT, Cursor, and Claude Code through its [MCP (Model Context Protocol)]() server. The company sells to enterprises with SOC 2 Type II compliance, tenant isolation, and a strict no-train policy already in place. All of these are table stakes for the kind of customers ProductNow works with, and enterprise-grade auth is no exception. ## The challenge of keeping upmarket momentum ProductNow's MCP server is open to any AI client that supports remote servers and OAuth. That made identity a core part of how far they could reach. If they couldn't meet enterprise identity demands, they couldn't land enterprise customers. They identified two of these enterprise-grade requirements as they began evaluating new auth solutions: - **MCP auth that keeps up with the spec: **Every client that connects to ProductNow's MCP server has to register with an authorization server and get scoped tokens before it can call a tool. The MCP authorization spec has been moving quickly, most recently toward [Client ID Metadata Documents (CIMD)]() for client registration, and ProductNow needed an auth provider whose MCP support would keep pace with it. - **Enterprise SSO ready before a deal stalled: **Enterprise customers expect [single sign-on (SSO)](), and ProductNow wanted its SSO implementation ready for its first connections without building and maintaining integrations ad hoc for every identity provider a customer might want. ProductNow's contract with its previous provider came up for renewal, which led the team to look for alternatives. At the same time, a provider-side issue blocked an integration with one of ProductNow's clients, which turned a "see what's out there" evaluation into a drive for migration. ProductNow set two parameters for making the switch to a new auth vendor: keep the budget startup-friendly, and make the move simple. Kadhir Manickam, CTO at ProductNow, said: > "When your identity provider gets in the way of a client integration, that's a risk to your momentum. We needed to move fast, and we needed MCP auth to work from day one. That's when migration stopped being a curiosity and turned into a priority." ## The Descope experience ProductNow joined Descope's [Startup Plan](), which includes a free year of the Pro tier, and started on the migration path as soon as it was approved. Descope shared its migration resources up front, including [Descope Skills](), installable instruction packs that give AI coding agents provider-specific migration knowledge, from mapping an existing setup to Descope equivalents through planning a cutover. ProductNow was live in its development environment the next night and in production three days after writing its first line of migration code. ProductNow's [MCP server]() is how AI clients work inside the context engine. Its tools let an agent search for evidence, file new decisions or notes where they belong, and manage documents. Every call runs as the signed-in ProductNow user, under the same workspace and document permissions that person has in the app. A user can only read documents they can view in ProductNow, and company brain search only returns evidence from documents the user can access. Unauthenticated MCP requests receive a `401 Unauthorized` response with a `WWW-Authenticate` header pointing to the MCP server's [protected resource metadata]() at a well-known URL. Descope acts as the authorization server for that MCP server through the [Agentic Identity Hub](). Descope authenticates the user, handles consent, and issues access tokens tied to that user, so ProductNow's server only has to validate the token and apply the permissions it already enforces. Because Descope supports [CIMD, DCR, and pre-registration]() at the same time, ProductNow can onboard each new client with whichever method it supports, without writing custom OAuth code for each one. For example, ChatGPT connects using [CIMD](), where the client's ID is an HTTPS URL pointing to metadata the client publishes itself. Clients that don't support CIMD yet can use DCR, and ProductNow can register clients manually in advance if needed. Kadhir Manickam, CTO at ProductNow, said: > "The whole process from the first line of code to production happened in three days, with 1.5 people working on it. Migration was simple enough that we never had to stop building the product to get it done." ## Enterprise-grade identity at startup speed ProductNow's Descope implementation covers both fronts that drove the switch: - **Production in three days: **ProductNow went from its first line of migration code to a full production rollout in three days, with one and a half engineers on the project. - **User-scoped MCP auth: **Every call to ProductNow's MCP server carries a Descope-issued token tied to the signed-in user, however the client registered. - **Enterprise SSO ahead of demand: **When enterprise customers ask for SSO, the [SSO Setup Suite]() lets their IT admins configure connections themselves, without ProductNow building an integration for each identity provider. Kadhir Manickam, CTO at ProductNow, said: > "When an agent searches or edits our customers' context from ChatGPT or Cursor, it has to act on behalf of one specific person, with exactly that person's access. Descope gave us that from day one, without slowing down the team building the product." As ProductNow brings on enterprise customers and more AI clients connect to its MCP server, Descope handles the [enterprise-ready]() and [agentic identity]() layer underneath, so a small team can keep its focus on the context engine. --- Descope is a flexible [drag & drop customer and agentic identity platform]() that helps organizations easily add authentication, authorization, and identity management to their apps, AI agents, and MCP servers. Customers use us for initiatives such as [passwordless authentication](), [SSO](), [identity federation](), [strong MFA](), [fraud prevention](), and [agentic identity](). To get started with Descope, [sign up for a Free Forever account](). If you have questions about our platform, [book time with our auth experts](). --- ### [Collectors Customer Story | Descope](https://www.descope.com/customers/collectors) See how Collectors unified consumer brand login, partner federation, and admin SSO for millions users on one Descope identity orchestration layer. *Full content: [https://www.descope.com/customers/collectors.md](https://www.descope.com/customers/collectors.md)* **[*Collectors*]()*, the parent company of PSA, PCGS, SGC, and Beckett, needed to unify identity across three distinct login scenarios (consumer brand auth, a co-managed partner product, and internal admin access) under a single platform. Their incumbent solution couldn't provide the federation flexibility, JWT customization, or integration depth they required. Learn how Descope gave Collectors' identity team the control and extensibility they needed to consolidate authentication for millions of users across brands and partners.* --- ## About Collectors Collectors is the global leader in third-party grading and certification for collectibles. Its portfolio includes [PSA]() (trading cards, memorabilia, and video games), [PCGS]() (coins and currency), [SGC]() (vintage and pre-war cards), [Beckett]() (grading, price guides, and publications), and [CardLadder]() (analytics).  With over a quarter million monthly active users, 30,000 daily active users, and nearly 8 million machine-to-machine credential exchanges across 5.7 million user records, Collectors operates identity infrastructure at a scale where fragmentation can quickly create UX friction. ## Three login experiences, one identity challenge Collectors' identity requirements were somewhat atypical: the company had three different authentication use cases with different trust models, user populations, and technical constraints. - **Internal admin access** required corporate SSO for employees accessing administrative tools. On its own, this was straightforward [SAML-based SSO](). But running it alongside two other login patterns on a platform that treated each as a separate configuration environment created operational fragmentation for a lean identity team. - **Consumer brand login** served the primary user base across PSA, PCGS, and other Collectors properties. Sub-brands needed to federate to a central, self-hosted authentication page with Collectors' own branding, privacy policies, and footer. The incumbent platform made this federation rigid, and routing users across brands while maintaining consistent session behavior required workarounds that added overhead without adding flexibility. - **A co-managed partner product** introduced a different trust model. Partner users needed to authenticate through the partner's own identity provider via OAuth, with Collectors acting as an intermediary. The incumbent platform had no clean abstraction for this kind of multi-party federation. The core challenge was architectural: Collectors needed an authentication provider that could handle all three use cases within a unified identity model. Dan Van Tran, CTO at Collectors, said: > "Our consumer federation, partner federation, and admin SSO grew up separately, so each one was its own world to maintain. We wanted one unified place to run them without giving up our work on claims and scopes. Descope fit all three experiences into the same auth model, letting us keep the control we’d built.” ## The Descope experience Collectors needed a solution that could replicate the JWT claim patterns and scope controls they'd built previously while extending into areas where their former provider had set limitations. They evaluated alternatives against federation flexibility, JWT template depth, connector-based integration architecture, M2M scope control, and engineering responsiveness. Descope addressed all of these requirements. Collectors rolled out Descope across each of their three use cases: admin SSO, consumer brand authentication, and partner federation. Each use case exercised different parts of Descope's solution, but all three ran through the same flow-based orchestration layer: - The SAML-based admin SSO flow authenticates employees through Collectors' corporate identity provider, applies specific audience info and custom admin scope claim, and completes. Once the redirect model and frontend integration were set up, the team moved quickly to production. - User records were imported from the incumbent alongside Collectors' internal database. During the transition, a [just-in-time (JIT)]() password sync captured credentials as users logged in through the incumbent and wrote them to Descope. These accounts were then ready at cutover without a forced password reset. MFA enrollment data was also preserved from the legacy provider, and Collectors implemented a new MFA pattern: users select their method (SMS OTP or voice call OTP) at registration, stored as a custom attribute and enforced at sign-in through the flow. - Partner users authenticate through the partner's custom identity provider, with Descope acting as the intermediary. The flow initiates an OAuth exchange with the partner's identity provider, then a proxy connector call to Collectors' backend API creates or validates the user, maps custom attributes across both systems, and handles edge cases like suspended user redirects and error audit events. Descope's[ connector]() system ties the identity layer into Collectors' broader infrastructure: [Twilio]() for SMS and voice OTP delivery, Mimecast (via [SMTP connector]()) for transactional email, [AWS S3]() for audit log streaming, [webhook-driven event handling]() for MFA verification, and the proxy API that powers user creation in the partner federation flow. Authentication flows across all three use cases support English, French Canadian, and Japanese. Account lockout emails, OTP messages, and user-facing screens are localized per user locale, extended by Descope's [Google Cloud Translation connector](). The migration also surfaced requirements that drove new platform capabilities, feature requests pushed to production before the migration completed rather than as a future roadmap. Descope shipped PKCE support for custom OAuth providers, public/private key JWT authentication for external identity provider integration, .NET SDK enhancements, JIT session migration support for Okta CIS, and localization changes. Smit Gujarathi, VP of Marketplace Engineering at Collectors, said: > "Partner federation could have been a service we owned and maintained forever. With Descope Flows, it’s a simple matter of configuration. In case we did run into an unexpected requirement, the Descope team built the feature while we were still in the middle of the project. That’s not your typical auth vendor." ## Simplifying the identity surface for six million users Leveraging Descope’s flexible orchestration and federation capabilities, Collectors replaced a fragmented identity stack with a single orchestration layer that handles consumer federation, partner authentication, admin SSO, and millions of monthly M2M exchanges. As they continue enriching their identity experiences with Descope, they plan to add more integrations, introduce [native mobile applications](), and enhance token management.  Dan Van Tran, CTO at Collectors, said: > "Identity used to be three separate engineering efforts for us, and now it's one. What matters most looking ahead is agility: we can add integrations, test different flows, and refine token management without rebuilding the foundations every time we want to try something new." For organizations managing identity across multiple brands, partners, and user populations, Descope provides the flow-based architecture and robust integrations to consolidate without compromising, and without spending months and countless dev cycles to end up with never-ending maintenance. --- Descope is a flexible [customer and agentic platform]() that helps organizations easily add authentication, authorization, and identity management to their apps, AI agents, and MCP servers. Customers use us for initiatives such as [passwordless authentication](), [SSO](), [identity federation](), [strong MFA](), [fraud prevention](), and [agentic identity](). To get started with Descope, [sign up for a Free Forever account](). If you have questions about our platform, [book time with our auth experts](). --- ## Press Releases ### [Descope Wins Nine 2026 Top Workplaces Awards](https://www.descope.com/press-release/top-workplace-2026) Energage recognizes Descope with a Top Workplaces Industry award for Technology and eight Culture Excellence awards, based on a 96% overall Workplace Experience Score. *Full content: [https://www.descope.com/press-release/top-workplace-2026.md](https://www.descope.com/press-release/top-workplace-2026.md)* **Los Altos, CA, November 18, 2026** – [Descope](), a developer-friendly customer and agentic identity platform, today announced it has won nine 2026 Top Workplaces awards from [Energage](), a purpose-driven organization that develops solutions to build Top Workplaces. The Top Workplaces program has a 19-year history of surveying and celebrating people-first organizations nationally and across 60 regional markets. Descope received a Top Workplaces Industry award for Technology. Industry awards celebrate organizations that have built people-first workplace cultures within their sector and mark them as an employer of choice for people seeking jobs in that industry. Descope also won eight Top Workplaces Culture Excellence awards, which recognize organizations that excel in specific areas of workplace culture: - **Leadership:** Leaders inspire confidence in employees and in the direction of the company, and understand the customer needs that front-line employees hear every day. - **Purpose & Values:** The company’s mission and values are part of its culture, and teams work effectively to put them into practice. - **Innovation:** Innovation is part of the culture, with new ideas coming from employees across the company. - **Professional Development:** The company helps employees develop their careers and grow professionally. - **Work-Life Flexibility:** Employees have options in how and where they work, and managers care about their concerns. - **Employee Well-Being:** Employee health and wellness are central to the workplace culture. - **Compensation & Benefits:** Employees receive material rewards along with appreciation for their work. - **Employee Appreciation:** The company shows gratitude for employees’ efforts, and employees are motivated to give their best at work. Top Workplaces awards are based on feedback from a research-backed employee engagement survey. Descope received an overall Workplace Experience Score of 96%, 11 points above Energage benchmarks. The score averages employee responses across all core statements in the survey. Details about how Descope builds a great workplace culture are available on[ Top Workplaces](). “These awards come from anonymous feedback from our own team, which makes them mean more to me than most recognition we receive,” said Slavik Markovich, Co-Founder and CEO of Descope. “Since we started Descope, we have tried to give people ownership early and be open with them about where the company is headed. Thank you to everyone at Descope who took the survey and who makes this a place people want to work.” “I’ve always believed that a company’s DNA starts at the top,” said Yodan Rotholz, Head of People and Talent at Descope. “At Descope, we have eight founders who are accessible, authentic, and present, and nobody is sitting in a golden tower disconnected from everyone else. That said, we’re not perfect and don’t pretend to be. There’s room to add more structure as we grow. Processes can be built, but the connection, trust, and care we have for our people are much harder to build, and our job is to keep them.”  “Earning a Top Workplaces award is a badge of honor for companies, especially because it comes authentically from their employees,” said Eric Rubino, Energage CEO. “That’s something to be proud of. In today’s market, leaders must ensure they’re allowing employees to have a voice and be heard. That’s paramount. Top Workplaces do this, and it pays dividends.” Descope is hiring. Open roles are listed at[ descope.com/careers](). ### About Descope Descope is a developer-friendly customer and agentic identity platform. Organizations use our visual workflows, SDKs, APIs, and MCP server to easily create and customize identity journeys for their customers, partners, and AI agents. Thousands of organizations use Descope to streamline customer and agent onboarding, prevent account takeover, and securely adopt AI agents and MCP servers with built-in identity controls. Learn more at[ www.descope.com](). ### About Energage Energage is a purpose-driven company that helps organizations turn employee feedback into useful business intelligence and credible employer recognition through Top Workplaces. Built on 20 years of culture research and the results from 30 million employees surveyed across more than 80,000 organizations, Energage delivers the most accurate competitive benchmark available. With access to a unique combination of patented analytic tools and expert guidance, Energage customers lead the competition with an engaged workforce and an opportunity to gain recognition for their people-first approach to culture. For more information or to nominate your organization, visit[ energage.com]() or[ topworkplaces.com](). #### Media Contact Christine Penwell Offleash for Descope descope@offleashpr.com --- ### [Descope Recognized as a CRN® Stellar Startup for the Second Year in a Row](https://www.descope.com/press-release/crn-stellar-startup-2026) Recognition in the Security category for Descope follows a year of new channel partnerships, analyst recognition, and customer and agentic identity launches. *Full content: [https://www.descope.com/press-release/crn-stellar-startup-2026.md](https://www.descope.com/press-release/crn-stellar-startup-2026.md)* **Los Altos, CA, November 10, 2026** – [Descope](), a developer-friendly customer and agentic identity platform, announced today that CRN®, a brand of The Channel Company, has included Descope on its 2026 Stellar Startups list in the Security category. This prestigious list highlights fast-rising technology vendors that are driving innovation and fostering growth in the IT channel with groundbreaking products. This is the second consecutive year Descope has been named to the list. Companies recognized as Stellar Startups must be six years old or younger, and they are selected across categories that include artificial intelligence, business applications, cloud, data center, data platforms and analytics, edge computing/Internet of Things, networking/unified communications, security and storage. Descope gives organizations a no/low code way to build and secure identity journeys for their customers, partners, and AI agents. Security teams use Descope Flows, a drag-and-drop workflow editor, to add passwordless authentication, phishing-resistant MFA, and fraud prevention controls at the right point in each journey without disrupting the user experience. The [Agentic Identity Hub]() gives AI agents and MCP servers their own identities, with an agent directory, least-privilege access enforced at runtime, and human approval of sensitive agent actions. Over the past year, Descope expanded how partners and public sector buyers can bring its platform to their clients. Descope[ partnered with IDMWORKS](), an identity and access management consultancy with more than 2,500 IAM implementations, to deliver strategic guidance, implementation, and managed services. Descope also became a[ supplier on the UK government’s G-Cloud 15 framework](), so eligible UK public sector organizations can procure Descope without running a full tender. In October 2026, Descope was recognized as the only Visionary in the[ 2026 Gartner® Magic Quadrant™ for Customer Identity and Access Management (CIAM)](). This annual list serves as an invaluable resource for solution providers making business-critical strategic decisions and exploring new technologies and services to add their portfolios to give them a competitive advantage and drive success. “Channel partners are often the first call when an enterprise rethinks customer identity or starts putting AI agents in front of its users,” said Rishi Bhargava, Co-Founder of Descope. “Being named a CRN Stellar Startup for a second year tells us that partners see Descope as a platform they can build an identity practice around. We will keep working with systems integrators, resellers, and consultancies to bring flexible, modern customer and agentic identity to their clients.” “We’re proud to recognize the innovative companies featured on this year’s Stellar Startups list,” said Jennifer Follett, Vice President, U.S. Content, Executive Editor at CRN, The Channel Company. “These organizations are redefining what’s possible in the IT channel by bringing fresh ideas, transformative technologies and a strong commitment to partner success. We look forward to seeing the impact they continue to make across the industry.” Coverage of the 2026 CRN Stellar Startups list is available at[ crn.com/StellarStartups](). **About Descope** Descope is a developer-friendly customer and agentic identity platform. Organizations use our visual workflows, SDKs, APIs, and MCP server to easily create and customize identity journeys for their customers, partners, and AI agents. 1000+ organizations use Descope to streamline customer and agent onboarding, prevent account takeover, and securely adopt AI agents and MCP servers with built-in identity controls. Learn more at[www.descope.com](). **About The Channel Company** The Channel Company (TCC) is the global leader in channel growth for the world’s top technology brands. We accelerate success across strategic channels for tech vendors, solution providers and end users with premier media brands, integrated marketing and event services, strategic consulting, and exclusive market and audience insights. TCC is a portfolio company of investment funds managed by EagleTree Capital, a New York City-based private equity firm. For more information, visit thechannelco.com. © 2026 The Channel Company, Inc. CRN is a registered trademark of The Channel Company, Inc. All rights reserved. **Media Contacts** Christine Penwell Offleash for Descope [descope@offleashpr.com]() Kristin DaSilva The Channel Company [kdasilva@thechannelcompany.com]() --- ### [Descope Unveils Envoy, an Identity-Aware Way For Personal AI Agents to Act on People’s Behalf](https://www.descope.com/press-release/envoy) Personal Agent Protocol support, granular agent permissions, and out-of-band user approval let consumer businesses accept personal agents alongside the customer identity stack they already run *Full content: [https://www.descope.com/press-release/envoy.md](https://www.descope.com/press-release/envoy.md)* **Los Altos, CA, November 4, 2026 –** [Descope](), a developer-friendly customer and agentic identity platform, today announced [Envoy](), a set of capabilities that gives personal AI agents a delegated sign-in path alongside a consumer app’s existing authentication flows. Consumer companies can now accept agents as first-class users—with their own identities, permissions, and approval flows—without rebuilding their identity stack. [GoFundMe](), [You.com](), [GoodRx](), and [Composio]() are among several launch and design partners for Envoy who will work alongside Descope to improve Envoy in the months to come. Personal agents have reached consumer scale in record time. Meta’s Muse passed[ 5 million downloads]() by the end of September, growing faster in its early months than ChatGPT, Grok, or Claude. The commerce rails underneath are being adopted quickly as well: OpenAI’s Instant Checkout runs for roughly 900 million weekly active users, and Shopify is activating agentic storefronts for more than a million merchants. Shoppers are now asking an AI assistant to find a product, confirm the size, and place the order. When that agent arrives at a company’s website, the company currently has two sub-optimal options: - **Block the agent.** Amazon blocked Muse in September, and[ JPMorgan Chase blocked outside agents]() including Muse and Instinct from directly accessing customer accounts in October. Blocking is a reasonable short-term response for companies with existing brand recognition, but it becomes harder to sustain as more customers route their shopping, travel, and account management through an agent. Businesses that aren’t Amazon or JPMorgan risk giving up revenue to competitors that found a way to accept agents. - **Let the agent sign in as the customer.** The agent collects the customer’s password and one-time code, signs in, and the site sees what looks like an ordinary human login. Nothing in the session records that an agent was involved, which means the business is dealing with impersonation rather than delegation. When an order goes wrong or a fraud rule gets enforced, the logs will point at the human customer, and the business will likely have to absorb the cost through disputed orders, returns, and support volume. A standard is taking shape for how delegated access for personal agents should work. Meta and Sierra published[ Personal Agent Protocol]() (Poppy) draft 0.1 in October, which gives a business a way to publish what its agent-facing endpoints are, verify the identity of the agent making the request, and issue a session that is cryptographically bound to that agent for the length of the interaction.  Envoy gives consumer site developers an abstraction layer to support agents alongside human users without taking on the burden of implementing Poppy or keeping up with the specification as it evolves. Capabilities in Envoy include: - **Personal Agent Protocol support,** which lets businesses accept agent traffic without implementing the Poppy protocol draft themselves. Descope handles discovery, agent identification through [Client ID Metadata Documents]() with no pre-registration required, session tokens bound to the agent’s key with Demonstrated Proof of Possession (DPoP), and all three Poppy sign-in types. - **Granular agent permissions,** which let businesses define exactly what an agent may and may not do on a customer’s account using Rich Authorization Requests (RAR). For example, a shopping agent can browse the catalog and place orders while remaining unable to touch account settings or payment methods, with the duration of any elevated access set by the business. - **Out-of-band approval for sensitive actions,** using [Client-Initiated Backchannel Authentication (CIBA)](). For example, an agent that finds a flight overnight can hold the fare and send an approval request showing the airline, the times, and the total, which the customer can approve from their phone the next morning. - **Delegation instead of impersonation,** which keeps the customer and the acting agent distinct in every token and log entry. This distinction means that a company can revoke an agent’s access without signing the customer out. - **Augmentation instead of replacement,** which lets Envoy run alongside the customer identity stack a company already has. “Every login page on the internet was built on the assumption that a person is on the other side, but that assumption no longer holds true,” said Slavik Markovich, Co-Founder and CEO of Descope. “Consumer apps can either block agents or let them sign in as humans, but neither approach works in the long term. We believe the Personal Agent Protocol is doing for consumer agents what MCP did for enterprise tools, and are excited to announce Envoy to give consumer apps an easy, standards-based way to accept agent logins.” “Every donation on GoFundMe is an act of trust, so when an agent acts for someone, we need to know exactly who is giving and who is acting for them,” said Arnie Katz, Chief Product and Technology Officer of GoFundMe. “Envoy will keep the person and the agent distinct in every session, limit what an agent can do, and ask the user to approve donations from their phone. We’re proud to be working with Descope to help build that future responsibly, on open standards and in service of our customers.” “More and more, people will ask a personal agent to find the lowest price on a prescription, compare pharmacies, and line up savings before they reach the counter. That’s where consumer healthcare is headed, and we want GoodRx to be ready for it,” said Nitin Shingate, CTO of GoodRx. “Descope has been a trusted partner for us, and expanding that partnership to support AI agents lets us welcome them as first-class users. Agents get clear, limited permissions for pricing information, and our users stay in control of their actions.” Alongside Envoy, Descope has also published a [Poppy SDK]() for AI agent builders. This zero-dependency Typescript SDK enables any AI agent to easily become compatible with the Personal Agent Protocol, with Descope handling discovery, client metadata document generation, session management, DPoP API calls, and other elements required by the spec. Together, Envoy and the Poppy SDK help both consumer apps and AI agents adopt patterns for secure, delegated access.  Envoy builds on the[ Descope Agentic Identity Hub](), which handles authentication and access control for 1000+ MCP servers and millions of monthly agentic transactions. Learn more about Envoy by visiting [this page]() or reading our [launch blog](). ### About Descope Descope is a developer-friendly customer and agentic identity platform. Organizations use our visual workflows, SDKs, APIs, and MCP server to easily create and customize identity journeys for their customers, partners, and AI agents. Thousands of organizations use Descope to streamline customer and agent onboarding, prevent account takeover, and securely adopt AI agents and MCP servers with built-in identity controls. Learn more at[ www.descope.com](). #### Media Contact Christine Penwell Offleash for Descope descope@offleashpr.com --- ### [Descope the Only Visionary in 2026 Gartner Magic Quadrant for CIAM](https://www.descope.com/press-release/2026-gartner-magic-quadrant-ciam) Descope is the only Visionary in the first Gartner Magic Quadrant dedicated to CIAM, covering identity for customers, partners, and AI agents. *Full content: [https://www.descope.com/press-release/2026-gartner-magic-quadrant-ciam.md](https://www.descope.com/press-release/2026-gartner-magic-quadrant-ciam.md)* **Los Altos, CA, November 2, 2026** –[ Descope](), a developer-friendly customer and agentic identity platform, today announced it has been recognized as a Visionary in the 2026 Gartner Magic Quadrant for Customer Identity and Access Management (CIAM). Descope is the only vendor positioned in the Visionaries quadrant. Last year, Descope was included as an[ Honorable Mention in the 2025 Gartner Magic Quadrant for Access Management](). ![Figure 1 Magic Quadrant for Customer Identity and Access Management]() In our view, previous editions of the Gartner Magic Quadrant evaluated workforce and customer access management together under the Access Management name. We believe the new report evaluates vendors on the identity needs of customers, partners, and machine identities, including AI agents, separately from workforce access management. In our view, this scope matches how Descope has built its platform from the start. Organizations use[ Descope Flows](), a drag-and-drop workflow editor, to design registration, authentication, and authorization journeys for consumers, business customers, and partners. The [Agentic Identity Hub]() applies the same identity controls to AI agents and MCP servers, with support for human approval of agent actions through CIBA and enterprise agent access through Cross-App Access (XAA).  “Customer identity has always had different expectations about user experience, flexibility, and self-service administration than workforce identity, and we built Descope around those requirements from day one,” said Slavik Markovich, Co-Founder and CEO of Descope. “Our customers use one platform for their consumers, their business customers and partners, and now the AI agents that act on their users’ behalf. Being the only Visionary in the Magic Quadrant for CIAM is a proud moment for everyone at Descope and in our view a powerful validation of our approach to customer and agentic identity.” Descope launched from stealth in February 2023 and has since then grown to be used by 1000+ organizations from fast-growing startups like [7AI](), Nexthop AI, and [Reco]() to global enterprises like[ GoFundMe](),[ GoodRx](), and[ Databricks](). The Agentic Identity Hub secures 1000+ MCP servers and powers millions of monthly agentic transactions for customers like [WisdomAI](), [Cequence Security](), [You.com](), and [Linktree](). [Download a complimentary copy of the 2026 Gartner Magic Quadrant for Customer Identity and Access Management.]() *Gartner and Magic Quadrant are trademarks of Gartner, Inc., and/or its affiliates.* *Gartner does not endorse any company, vendor, product or service depicted in its publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner publications consist of the opinions of Gartner’s business and technology insights organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this publication, including any warranties of merchantability or fitness for a particular purpose.* *Gartner, Magic Quadrant for Customer Identity and Access Management, Steve Wessels, Brian Guthrie, Michael Kelley, Gautham Mudra, 28 October 2026.* *Gartner, Magic Quadrant for Access Management, Brian Guthrie, Nathan Harris, Yemi Davies, Steve Wessels, 11 November 2025.* *This graphic was published by Gartner, Inc. as part of a larger research document and should be evaluated in the context of the entire document. The Gartner document is available upon request from Descope.* ### About Descope Descope is a developer-friendly customer and agentic identity platform. Organizations use our visual workflows, SDKs, APIs, and MCP server to easily create and customize identity journeys for their customers, partners, and AI agents. Thousands of organizations use Descope to streamline customer and agent onboarding, prevent account takeover, and securely adopt AI agents and MCP servers with built-in identity controls. Learn more at[ www.descope.com](). #### Media Contact Christine Penwell Offleash for Descope descope@offleashpr.com --- ### [Descope Named to Fortune Cyber 60 List for Fourth Consecutive Year](https://www.descope.com/press-release/fortune-cyber-60-2026-2027) The 2026–27 Fortune Cyber 60 recognizes 60 of the most important venture-backed cybersecurity companies, presented by Lightspeed Venture Partners and Amazon Web Services (AWS) in partnership with Fortune. *Full content: [https://www.descope.com/press-release/fortune-cyber-60-2026-2027.md](https://www.descope.com/press-release/fortune-cyber-60-2026-2027.md)* **Los Altos, CA, October 28, 2026** –[ Descope](), a developer-friendly customer and agentic identity platform, today announced it has been named to the 2026–27 Fortune Cyber 60 list in the early growth category. This is the fourth consecutive year Descope has been included. The full list can be found at [https://fortune.com/ranking/cyber/]().  The 2026–27 Fortune Cyber 60 recognizes 60 of the most important venture-backed cybersecurity companies, presented by Lightspeed Venture Partners and Amazon Web Services (AWS) in partnership with Fortune. Now in its fourth year, the list honors companies addressing challenges across AI security, identity and access, data protection, cloud security, and security operations. It includes 20 companies in each of three categories (early stage, early growth, and growth) and recognizes startups that have not completed an IPO, acquisition, or other significant exit. To develop this year’s list, Lightspeed evaluated more than 300 cybersecurity startups, considering annual recurring revenue, current- and prior-year growth, and business operations. The selection process combined validation of company-reported data with proprietary research, consultation with Lightspeed’s CISO network, and analysis of the cybersecurity market. The final list was reviewed and validated by Fortune. Over the past year, Descope: - Released[ Agentic Identity Hub 2.5]() and[ Agentic Identity Hub 3.0](), adding granular access policies, human-in-the-loop approvals with CIBA, MCP gateway integrations, and governance controls for agent onboarding and ownership. The Agentic Identity Hub now handles authentication and access control for more than 1,000 MCP servers. - Added[ Cross-App Access (XAA) support]() so enterprises can govern AI agent access through the identity providers they already use. - Launched[ Family Accounts](), the first release in its relational identity framework, which lets consumer apps model guardian, dependent, and household relationships. - Expanded[ data residency]() to seven regions, adding Singapore, Brazil, and the United Kingdom. - Was named a[ supplier on the UK government’s G-Cloud 15 framework](). - Was named a Sample Vendor for CIAM for AI Agents and Journey-Time Orchestration in the[ Gartner® Hype Cycle™ for Digital Identity, 2026]() and the[ Gartner® Hype Cycle™ for Fraud and Financial Crime Prevention, 2026](). - Was named a[ Leader in the 2025 Frost Radar for Non-Human Identity Solutions](), named to[ Rising in Cyber]() for the third year in a row, and won[ “Multifactor Solution of the Year”]() in the 2026 CyberSecurity Breakthrough Awards. “When we first made this list, most of our conversations with identity teams were about replacing passwords and improving login conversion,” said Slavik Markovich, Co-Founder and CEO of Descope. “This year, more of those teams asked how to let AI agents act for their users without giving every agent a shared API key. We built Descope so customers can answer both questions on the same platform. Being named to the Cyber 60 for a fourth year tells us that approach is working for them.” Over 1000 organizations use Descope, including[ GoFundMe](),[ GoodRx](), and[ Databricks](). ### About Descope Descope is a developer-friendly customer and agentic identity platform. Organizations use our visual workflows, SDKs, APIs, and MCP server to easily create and customize identity journeys for their customers, partners, and AI agents. 1000+ organizations use Descope to streamline customer and agent onboarding, prevent account takeover, and securely adopt AI agents and MCP servers with built-in identity controls. Learn more at[ www.descope.com](). #### Media Contact Christine Penwell Offleash for Descope descope@offleashpr.com ---