Monday, November 16, 2026
HomeSalesHow single sign-on works in apply

How single sign-on works in apply


CRM single sign-on (CRM SSO) makes use of an id supplier (IdP) to authenticate customers, so workers can sign up to the CRM by means of the identical id system they use for different office instruments. Safety Assertion Markup Language (SAML) and OpenID Join (OIDC) deal with authentication, whereas System for Cross-domain Id Administration (SCIM) handles a separate job: provisioning and deprovisioning consumer accounts. Retaining these roles distinct helps groups cut back lockout and access-governance danger throughout rollout.

Learn more about why HubSpot's CRM platform has all the tools you need to grow  better.

Earlier than going additional, listed here are the important thing phrases:

  • SAML: An XML-based commonplace that lets an IdP ship authentication assertions and attributes to an software.
  • OIDC: An id layer constructed on OAuth 2.0 that lets an software confirm a consumer’s id and obtain id claims.
  • SCIM: A typical for automating user-account provisioning, updates, and deprovisioning between programs.
  • Multi-factor authentication (MFA): Authentication that requires a number of verification elements. When an IdP enforces MFA, that test might be a part of the SSO sign-in move.
  • IdP: The system that authenticates the consumer and sends trusted assertions or tokens to the CRM. Widespread examples embrace Microsoft Entra ID, Okta, OneLogin, and Google.
  • Provisioning and deprovisioning: Creating or updating a consumer’s account and entry once they be part of or change roles, then disabling or eradicating entry once they go away.

SSO centralizes authentication, which is how customers show who they’re. SCIM automates account lifecycle administration, which is how accounts are created, up to date, and retired. SSO and SCIM usually work collectively, however they resolve completely different issues.

Desk of Contents

What’s CRM SSO? Plus, Why CRM SSO Issues

CRM SSO means workers entry the CRM by means of a central id supplier as a substitute of counting on a separate CRM password. The IdP authenticates the consumer, sends a trusted assertion or token, and the CRM grants entry primarily based on mapped roles, teams, and insurance policies.

For workers, CRM SSO can imply fewer credentials and sign-in steps. For IT and safety groups, CRM SSO centralizes authentication coverage and makes sign-in exercise simpler to audit. Once you additionally configure SCIM, the IdP can automate consumer creation, updates, and deactivation within the CRM. These entry controls complement the broader advantages of a CRM system by decreasing authentication friction whereas giving directors extra centralized management.

How CRM SSO Works With SAML, OIDC, and Your IdP

On the authentication layer of a CRM integration, SAML and OIDC resolve the identical core drawback: They let an software depend on an id supplier to authenticate a consumer. They use completely different message codecs and flows, whereas SCIM sits exterior the sign-in move and manages consumer accounts.

SAML vs. OIDC vs. SCIM

SAML 2.0 makes use of XML-based assertions. In a typical internet SSO move, the IdP authenticates the consumer and sends an assertion to the service supplier, which validates it and applies its personal entry guidelines.

OIDC is an id layer on OAuth 2.0. It lets an software confirm the consumer’s id and obtain consumer claims. OIDC is usually used for contemporary internet and cellular authentication flows.

SCIM doesn’t authenticate customers. It manages account lifecycle information by means of provisioning APIs. A product can help SCIM independently of the authentication protocol it makes use of, although some merchandise require SSO to be enabled earlier than you’ll be able to configure SCIM.

CROM sso architecture

CRM SSO Advantages and Dangers to Weigh

CRM SSO can cut back sign-in friction for customers and centralize extra authentication controls for directors. Nonetheless, CRM SSO additionally creates a dependency on the id supplier that groups have to plan round.

CRM SSO Advantages

For customers, the clearest profit is fewer CRM-specific credentials and sign-in prompts. Eradicating that entry friction can help CRM adoption.

For directors, SSO centralizes identity-provider controls similar to MFA and sign-in coverage, making entry governance simpler to coordinate with a broader CRM technique. The CRM can nonetheless have its personal session, authorization, and permission settings, so SSO doesn’t remove application-level controls. When SCIM is configured, it may well additionally automate account provisioning and deactivation, decreasing guide offboarding work.

CRM SSO Threat

SSO creates a dependency on the id supplier. An IdP outage or misconfiguration can block customers from the CRM and different related purposes. Pilot testing reduces that danger by exposing configuration mismatches earlier than SSO is required for the total consumer inhabitants.

Plan a fallback path earlier than go-live. Relying on the CRM, which may imply exempting an emergency administrator account from SSO, documenting tips on how to flip off the SSO requirement, or sustaining one other vendor-supported restoration technique. Check the fallback earlier than an outage.

CRM SSO Setup Steps You Can Comply with At this time

Organising CRM SSO follows a predictable sequence: Put together your IdP and CRM, check the connection, then implement entry insurance policies as soon as the mixing works as anticipated.

CRM SSO checklist

1. Put together your IdP and CRM.

Affirm that your CRM version helps the SSO protocol you propose to make use of and evaluate its administrator, area, and user-management conditions. Outline the CRM’s roles or permission mannequin, then map IdP teams or attributes to the entry every consumer sort wants. In the event you additionally plan to make use of SCIM, evaluate the CRM’s provisioning conditions earlier than constructing these mappings.

2. Trade metadata and check.

For SAML, configure the service supplier and IdP with one another’s required values. Widespread service-provider values embrace an entity ID (viewers) and an Assertion Shopper Service (ACS) URL. Widespread IdP values embrace an issuer or identifier, SSO URL, and signing certificates. Precise fields range by product, so comply with the CRM and IdP documentation fairly than assuming either side use the identical metadata format.

Check with a small pilot group earlier than requiring SSO for everybody. A pilot can floor certificates, URL, declare, and role-mapping issues whereas limiting the affected inhabitants.

3. Map roles and implement MFA.

With authentication working, map IdP teams, roles, or claims to the CRM’s permissions and check every consumer sort. SCIM role-to-permission conduct is product-specific; if the CRM requires actual names or case matching, mirror these values precisely.

Implement MFA by means of the IdP per your group’s safety coverage, and ensure the MFA step works within the SSO move. Additionally check deprovisioning so eradicating or disabling a consumer on the IdP produces the supposed entry change within the CRM.

How HubSpot Helps SSO and SCIM

HubSpot’s SSO setup makes use of SAML 2.0 and requires Tremendous Admin permissions to configure or edit. HubSpot supplies setup steering for Okta, OneLogin, Microsoft Entra ID (previously Azure AD), and Google. Throughout configuration, HubSpot supplies service-provider values such because the Viewers URI and sign-on/ACS values for the IdP, and the administrator provides the IdP’s issuer, SSO URL, certificates, or federation metadata again to HubSpot.

HubSpot account SSO is presently obtainable with Skilled and Enterprise editions of Advertising Hub, Gross sales Hub, Service Hub, Knowledge Hub, Content material Hub, HubSpot Sensible CRM, and Income Hub. After you configure SSO, HubSpot can require it for customers. HubSpot recommends protecting no less than one Tremendous Admin exempt from that requirement in order that, if the IdP is unavailable, the administrator can nonetheless sign up and quickly flip off required SSO.

For SCIM provisioning, HubSpot requires SSO to be enabled earlier than you’ll be able to configure SCIM. The customized SCIM characteristic requires a Skilled or Enterprise account. HubSpot additionally supplies devoted provisioning paths for Google and Okta. Their present documentation lists Advertising Hub, Gross sales Hub, Service Hub, Content material Hub, and Income Hub Skilled and Enterprise. Different IdPs, together with Microsoft Entra ID, PingFederate, OneLogin, and JumpCloud, can use HubSpot’s customized SCIM developer path.

Just a few HubSpot-specific caveats are value planning round:

  • Area verification: SCIM setup requires DNS verification with a TXT document. DNS modifications can take as much as 48 hours to propagate.
  • Permission-set matching: When permission-set position sync is enabled, the IdP position identify should precisely match the HubSpot permission-set identify, together with areas and capitalization.
  • Seat task: Seat conduct varies by SCIM path and pricing mannequin. In HubSpot’s customized SCIM developer move, seats-based accounts should replace the consumer’s seat in HubSpot earlier than assigning permissions by means of the IdP. With Okta on the seats-based pricing mannequin, HubSpot routinely assigns the perfect obtainable seat that helps the synced permission set. Google has its personal seat and permission-set necessities, so comply with the provider-specific setup documentation.
  • Deprovisioning path: Deprovisioning conduct varies by SCIM path. With HubSpot’s customized SCIM integration and Okta, eradicating HubSpot entry or deactivating the consumer within the IdP deactivates that consumer in HubSpot. With Google, eradicating HubSpot entry or deactivating the consumer in Google deletes the consumer in HubSpot. Deleting a consumer in HubSpot doesn’t delete the consumer within the IdP.

Steadily Requested Questions About CRM SSO

Launching a Related CRM With SSO

CRM SSO and SCIM resolve associated however separate issues: SSO centralizes authentication, whereas SCIM automates user-account lifecycle administration. Used collectively, they’ll cut back sign-in friction, automate components of onboarding and offboarding, and centralize extra id controls. A safer rollout begins with a pilot, validates position and permission mapping, enforces MFA on the IdP, assessments deprovisioning, and paperwork a fallback path earlier than SSO turns into necessary.

HubSpot’s SAML-based SSO and SCIM provisioning comply with this identical sample on eligible Skilled and Enterprise subscriptions, with provider-specific setup necessities and provisioning caveats. In case your staff is evaluating a CRM with centralized authentication and provisioning in thoughts, Sensible CRM is a sensible place to begin.

RELATED ARTICLES

Most Popular

Recent Comments