{"title":"Authentication providers","slug":"authentication-providers-overview","url":"https://support.storeconnect.com/articles/authentication-providers-overview","url_markdown":"https://support.storeconnect.com/articles/authentication-providers-overview.md","subtitle":null,"summary":"StoreConnect supports multiple authentication methods for customer and staff login, including native accounts, Google SSO, Microsoft Entra ID, SAML-based providers, and Experience Cloud SSO.","type":"Help_Documentation","video_url":"","keywords":"authentication, SSO, single sign-on, Google login, Entra ID, Azure AD, SAML, OAuth, identity provider","last_modified":"2026-08-21T07:12:35+0000","body_markdown":"StoreConnect supports multiple authentication providers for customer login, allowing you to offer the sign-in experience that fits your audience — from standard email/password for consumer stores to enterprise SSO for B2B portals and staff-facing applications.\n\n## Supported authentication providers\n\n### Native accounts\n\nCustomers create an account with an email address and password. Account creation can be open (any visitor can register) or invitation-only (admin approval required). Suitable for consumer storefronts and general B2C use.\n\n### Google SSO\n\nCustomers sign in with their existing Google account using OAuth. No separate StoreConnect password is required. Suitable for consumer stores and any context where customers are likely to have a Google account.\n\n### Microsoft Entra ID / Azure AD\n\nEnterprise single sign-on via Microsoft's identity platform (formerly Azure Active Directory). Supports SAML 2.0 and OIDC. Customers and staff authenticate with their existing Microsoft organizational credentials.\n\nParticularly suited to:\n- B2B portals where customers are employees of Microsoft-identity organizations\n- Government and public sector deployments using Microsoft as their identity provider\n- Internal-facing stores where staff authenticate via the institution's Microsoft account\n\n### SAML\n\nStandards-based SSO using SAML 2.0, compatible with any SAML-compliant identity provider (Okta, OneLogin, PingFederate, and others). Configure a custom identity provider for stores where your organization manages its own identity infrastructure.\n\n### Experience Cloud SSO\n\nShare an authentication session with a Salesforce Experience Cloud site. Customers logged into an Experience Cloud community are recognized as logged-in in StoreConnect, and vice versa. Suitable for organizations that run both a Salesforce Experience Cloud portal and a StoreConnect storefront and want a seamless single sign-on experience across both.\n\n## Multiple providers per store\n\nMore than one authentication provider can be active on the same store simultaneously. For example, a store might offer both Google SSO and native account creation. The sign-in page presents all active options and the customer chooses.\n\n## Role-based store access\n\nAuthentication providers integrate with StoreConnect's role-based store permissions. After authentication, a user's access to specific stores, products, and pricing is determined by their Salesforce Contact or Account record attributes — not solely by how they authenticated.\n\nFor example, a SAML-authenticated user from a specific organization can automatically be associated with the correct Account record and price book, giving them their account-specific pricing without manual assignment.\n\n## Set this up\n\n- [Configure authentication providers](authentication-providers)\n- [Set up SAML single sign-on](saml-single-sign-on)\n- [Set up Experience Cloud SSO](experience-cloud-login)"}