Docs

Sign-in & accounts

Understand app origins, return URLs, and where tenant boundaries live—especially when DNS, SSO, or procurement reviews ask for specifics.

Sign-in resolves against your configured application host—typically the AskAkin endpoint linked from the header on these pages. Keeping the public web origin and app origin aligned avoids cookie, CORS, and redirect surprises during pilots.

Application base URL

In development you often run this frontend and the app on different ports; in production they should point at stable HTTPS origins defined by your deployment. The product reads PUBLIC_APP_ORIGIN-style configuration where applicable so links from documentation and email land on the right tenant.

In deployments, PUBLIC_APP_ORIGIN (and related env) define the console host so redirects from these pages and email stay consistent.

Tenants and roles

Accounts live inside your organization’s tenant. Administrative actions—inviting users, connecting integrations, adjusting AI policies—require appropriate roles. Exact role names and capabilities evolve with releases; use in-product controls as the source of truth.

Related topics

  • Privacy & security for subprocessors and retention questions.
  • FAQ for common buyer and operator questions.