Kanshin Docs / Organizations & Realms

Organizations & Realms

Kanshin’s structure rests on two containers: the organization and the realm. Understanding them is the key to everything else, because every user, application, and setting lives inside them.

Organizations (tenants)

An organization — also called a tenant — is your company’s self-contained space in Kanshin. It holds everything: your users, groups, applications, roles, policies, and directory provisioning.

  • Organizations are completely isolated. Data in one organization is invisible and unreachable from another, and this boundary is enforced by the system on every request, not left to careful configuration.
  • Each organization has a name and an immutable slug — a short, lowercase, machine-friendly identifier used internally to keep the organization’s resources separate.
  • An organization has a status (active, suspended, or archived) and a contact email.

Your organization’s details are shown on the Tenant Profile page in Settings, along with your own membership.

Realms (environments)

A realm is an environment inside an organization. Most organizations run at least two — a production realm for live use and a non-production realm (staging or test) for trying changes safely.

Each realm has:

FieldMeaning
NameA human-friendly label
SlugA short identifier, unique within the organization
ProductionWhether this realm is a live, production environment. The console uses this to flag production so you know when a change is about to affect real users
RegionAn optional tag noting where the realm runs (for example us-east-1)

You manage realms from the Realms page under Directory — create them, rename them, mark them production or not, and remove them.

Why realms matter

Realms let you scope configuration to an environment. For example, a role assignment can apply to a single realm rather than the whole organization, and directory-provisioning tokens can be tied to a realm. This means you can grant someone administrative access in staging without giving them the same access in production.