Login methods
ClarityLoop supports more than one sign-in method, but the important question is simple: which method should this person use for this account and this workspace?
Supported sign-in methods​
ClarityLoop supports:
Email and passwordGoogleMicrosoftSAML SSOfor Professional-plan workspaces
Use the method tied to the account​
In practice, each account is tied to an authentication provider.
- If the account was created with local credentials, use
email and password. - If the account was created through
GoogleorMicrosoft, keep using that provider. - If the workspace requires
SSO, use the SSO path for that workspace.
The login page gives people the relevant options, including Google, Microsoft, email and password, and the SSO path. What matters is choosing the method that matches the account and workspace rules.
Password reset applies only to local accounts​
Password reset is only for people who sign in with email and password.
If someone signs in through Google, Microsoft, or SSO, their password is managed by that identity provider rather than by ClarityLoop.
SSO changes how people enter a workspace​
SSO is configured per workspace, not per person across every workspace they belong to.
That means a person can belong to a mix of workspaces with different sign-in rules. It also means switching into an SSO-protected workspace can trigger an SSO sign-in flow if the user is not already authenticated for it.
FAQs​
Can one workspace offer more than one sign-in method?
Yes. But individual users should still sign in with the method tied to their account or required by the workspace.
What should we tell someone who sees an SSO-required message?
Tell them to use the SSO sign-in option for that workspace.
Can Google, Microsoft, or SSO users reset their password in ClarityLoop?
No. They need to use their identity provider's recovery flow instead.
Where do owners configure SSO?
From the workspace integrations area. See SAML Integration.