Sales Operations System
Users authenticate through the organisation's identity provider rather than a separate CRM password.
Beyond convenience, this is how access is removed reliably. When someone leaves, disabling the directory account should close the CRM too, and without federated sign-in that depends on somebody remembering.
Yes where the platform supports SAML or OpenID Connect against the customer's own identity provider, with documented configuration.
Partial where sign-in is federated to a single consumer provider only, with no way to point it at the organisation's directory or to enforce it account-wide.
No where authentication is by CRM credentials alone.
Multi-factor authentication is a separate control and is not counted here.
Vendor material reachable during this evaluation documents multi-factor authentication for Act! accounts but says nothing about SAML or OpenID Connect single sign-on with an external identity provider.
Single sign-on is supported over SAML against identity providers including Okta, Auth0, Microsoft Entra ID, OneLogin, Google Workspace and JumpCloud. Administrators can run it alongside email and password login or enforce SSO-only access.
The vendor documents out of the box single sign-on with Office 365, G Suite and PayPal, and states that Apptivo can integrate with any SAML authentication system, such as Microsoft ADFS, using SAML 2.0.
Single sign-on is implemented over SAML and configured against the customer's identity provider after a domain has been verified. A Require SSO for sign-in setting forces all access through the identity provider, taking effect at the next login rather than terminating existing sessions. SCIM provisioning and deprovisioning is documented separately, with setup guides for Okta and Microsoft Entra.
No Bigin documentation addresses authentication method. The account setup overview covers organisation details, users, roles and profiles and does not mention sign-on. The user management article and the user management FAQs describe inviting, activating, deactivating and deleting users and transferring the super admin role, with no reference to an identity provider. The integrations and toppings list contains no identity or directory connector.
Sign-in is by magic link sent to an email address or by Google account, and the vendor states that traditional email and password login is not supported. Signing in with a Google account gives federated access through a single identity provider, but no SAML or identity provider configuration is documented, there is no article on configuring an enterprise identity provider, and no setting is described for requiring federated sign-in across a workspace or organisation.
A super administrator can connect the account to a Microsoft 365 or Google Workspace domain so that users sign in with those credentials instead of a Capsule password, and Intuit sign-in is also offered. Enabling it requires every Capsule user's email address to exist in the identity provider's directory. No SAML or generic identity-provider configuration is documented, and the vendor notes that because SSO is offered it cannot mandate two-factor authentication.
Sign-up and log-in through Google is supported. Vendor documentation states that other single sign-on providers such as Okta and Auth0 are not supported, and it describes single sign-on users being able to set a password as an alternative log-in rather than the organisation being able to require single sign-on, so the capability is present but limited to one identity provider and not documented as enforceable.
Copper supports SAML-based single sign-on, with a vendor setup guide for Okta, and also supports Google authentication. Two-factor authentication is available through both.
The vendor's public feature comparison lists single sign-on with the single value Google against every plan, which indicates sign-in through a Google identity and nothing more. No help centre or developer article documents SAML or OpenID Connect configuration against a customer's own identity provider, and no article describes enforcing single sign-on for a workspace. The capability therefore appears present but limited to one provider, on the strength of a comparison table rather than documentation.
Single sign-on is configured at organisation level under Security and supports SAML, OAuth 2.0 and OpenID Connect. Okta and OneLogin are named as compatible SAML identity providers, and a default login method can be set for all users with custom policies for individual accounts or portals.
SAML 2.0 single sign-on is supported, with documented setup for Okta, OneLogin, Microsoft Entra ID, Google and AD FS. Configuration requires super admin permissions, and login methods can be restricted so users must authenticate through SSO.
Insightly supports SAML 2.0 single sign-on with identity providers including Okta, OneLogin, Ping Identity, Google Workspace and Microsoft Entra ID, plus SCIM user provisioning. Licences must still be assigned manually inside Insightly after SCIM provisioning, and SSO is not supported in the mobile application.
Signing in to Keap with a Google account is documented, provided the Keap sign-in address is a Gmail address, and two-factor authentication is documented separately. No SAML 2.0 or enterprise identity provider integration is documented, and the vendor community carries unanswered requests for custom SAML support.
Users are authenticated by Microsoft Entra ID, which the vendor documents as providing single sign-on and multifactor authentication for Power Platform, with all API calls authorised through the Microsoft identity platform using OAuth 2.0. Conditional access controls are documented as an available restriction on top.
SAML single sign-on is supported with catalogue applications for Okta, Entra ID and OneLogin, plus a custom SAML 2.0 route for any other identity provider.
A user can sign in with a Google account instead of a Nimble username and password, provided the Nimble registration address matches the Google address. No SAML or enterprise identity provider integration is documented, and no directory provisioning is described.
Single sign-on uses SAML 2.0 with identity providers including Okta, Microsoft Entra ID and Google Workspace, and is supported in the iOS and Android applications. Directory sync provisions users and refreshes every fifteen minutes with a manual sync option. A custom domain is required, individual users can be exempted, and at least one administrator must remain exempt to avoid lockout. Minimum licence counts apply to both features.
Single sign-on is configured in company settings by supplying identity provider keys and certificates, with vendor setup guides for Microsoft Entra ID and Okta. Security rules can require SSO for account access.
Single sign-on is configured by registering and verifying the customer's domain against their Azure tenant and selecting Office 365 or Azure AD as the sign-in provider, after which administrators can either mandate single sign-on or allow both sign-in methods. Email addresses must match exactly between the CRM and the directory. The vendor states that enabling single sign-on is the only two-factor authentication it provides. Sign-in is also being moved onto Access Evo authentication.
Salesforce supports single sign-on with SAML and OpenID Connect, acting as service provider to an external identity provider, and can also act as an identity provider itself. Preconfigured and custom authentication providers and delegated authentication are documented alongside.
Streak is installed as a browser extension over Gmail and is authorised against the user's Google account. No vendor documentation describing SAML or an identity-provider integration was found, and the security and settings pages do not mention single sign-on.
No vendor page reachable to this evaluation describes single sign-on, SAML or an identity provider integration for Vtiger.
No vendor documentation was reached that states Zoho CRM users can sign in through a third-party identity provider. The vendor's identity product, Zoho Directory, documents custom authentication enabling SAML and JWT single sign-on from any compliant identity provider, with named guides for Okta, Microsoft Entra ID, Google, Auth0, ADFS, JumpCloud, OneLogin, PingOne, CyberArk and miniOrange - but that documentation describes signing in to Zoho Directory itself and does not state that the session extends to Zoho CRM. Zoho Directory is a separate product from Zoho CRM, so on the evidence found this would be "not natively" at best.