Skip to main content

Login

The Chat sign-in page. Any unauthenticated visit to a Chat URL redirects here.

What's on the page

  • Email address field
  • Password field
  • Sign In button
  • (Conditional) "You don't have an account? Sign up" link — appears only when outside (external) registration is enabled. For a first-party deployment that switch is /org/system/settings-consumerAllow customer to be registered outside the system; for a partner-integrated deployment it is the tenant contract's outsideRegistration flag (see Registration).
  • Footer note: "A unique chat ID will be generated for your session. ID persists until you log out."
  • Theme toggle (sun / moon) in the corner.

What happens on submit

  1. Credentials are validated. A wrong password fails here regardless of anything else.
  2. Tenant check (partner-integrated deployments). The login surface is bound to a tenant by its request Origin. If the account was registered under a different tenant, login is refused with HTTP 406 — the same email can exist independently at multiple partner sites, and each login only resolves its own tenant's account. First-party logins (no tenant contract) skip this check.
  3. Login policy (partner-integrated deployments). The tenant contract can block a whole registration class (system-registered or outside-registered) from logging in — a blocked class is refused with HTTP 406.
  4. Space clamp. The Spaces carried into the session are clamped to those the tenant currently permits (account spaces ∩ contract spaces) on every login — a Space the tenant has since revoked cannot survive into a new session. See Spaces page.
  5. OTP decision. If OTP is required for this Consumer's class → user is sent to the OTP page; otherwise the user lands directly on / (Spaces page). For partner-integrated deployments the requirement comes from the tenant contract policy (per registration kind); first-party logins fall back to the /org/system/settings-consumer toggles. See OTP.

Who can log in here

Only Consumers. Accounts (admin users for /org) log in via the Organization sign-in, which is a different surface.