Sign-in policies and JIT
Configure bounded admission rules, session hints and explicit just-in-time identity eligibility.
Environment and organization policies are managed through /v1/policies with policies:read or policies:write. The supported kinds are force_sso, session, idp_initiated, jit and expression. Without a configured policy, existing native sign-in behavior is preserved.
Core enforces its admission decisions and returns effective profile hints. Your application owns its sessions: a force-SSO or session-lifetime hint does not replace enforcement in your application. Exclusions apply only to their own force-SSO rule and do not bypass other admission policies.
Plans and exclusions
Section titled “Plans and exclusions”| Kind | Lowest plan |
|---|---|
force_sso |
Pro |
session, idp_initiated, jit |
Business |
expression |
Enterprise |
A force_sso policy lists the email domains it applies to. Its exclusions list (up to 100 entries, Business and above) names exact email addresses that keep their other sign-in methods, for example an emergency owner account. Write each address exactly as your users sign in with it. Exclusions are valid only on force_sso and the profile hint reports an excluded user separately, so your application can show the right sign-in options.
Just-in-time admission defaults to deny
Section titled “Just-in-time admission defaults to deny”A configured JIT policy admits only its explicitly allowed evidence: verified email in an organization-verified domain, configured authenticated IdP groups or configured SCIM groups. An empty JIT policy denies every admission. Applicable admission policies are conjunctive; satisfying one does not override another refusal.
OIDC mailbox-verification provenance matters. A signed SAML email alone does not satisfy the verified-email branch. Custom mapped values do not become verified policy evidence.
SCIM-group admission needs an explicit connection-to-directory binding in the same environment and organization. Choose one match key: exact SCIM externalId by default, or case-insensitive PRECIS userName. There is no email join or fallback to another key. Missing, ambiguous, inactive, deleted or out-of-domain sources refuse SCIM-group admission. An unavailable bounded directory index does not turn this branch into an allow.
Expressions and deny precedence
Section titled “Expressions and deny precedence”Expressions use validated, bounded declarative rules over verified mailbox/domain or authenticated IdP-group evidence. They are not code, templates or regular expressions. Matching denies take precedence over allows, and an evaluation failure refuses admission.
Mailbox and email-domain comparisons ignore case, so changing the casing of an email cannot evade a deny rule. Email syntax validation itself does not establish mailbox ownership. Use the evidence branch required by your policy rather than trusting a submitted email suffix.
Downgrades preserve enforcement
Section titled “Downgrades preserve enforcement”Existing saved policies and role rules remain enforced after a plan downgrade. Creating or editing configuration above the current entitlement returns plan_limit_reached; deleting remains available. A downgrade does not silently remove a condition or relax admission.
See role rules for application role output, IdP-initiated sign-in for confirmation and handoff, and the management reference for exact request shapes.