> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neochamber.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Tenants

> One per customer company — the isolation boundary inside your datacenter.

A **tenant** is the isolation boundary inside your datacenter — one per customer
company. Every tenant you create belongs to your operator.

## Create one

Use **Create tenant** on `/admin/tenants`.

## Getting machines to a tenant

Your pooled servers reach a tenant two ways:

<CardGroup cols={2}>
  <Card title="The customer rents them" icon="cart-shopping">
    From your live availability, by GPU model, whole nodes at a time. Assigned
    on the spot.
  </Card>

  <Card title="You reassign one" icon="right-left">
    From the node's detail page, at any time.
  </Card>
</CardGroup>

## Per-tenant settings

**Logs visible to members** (default: on) controls whether that customer's users
can read their own machines' logs. Some contracts call for it off; most do not.

## Isolation

<Note>
  Isolation is enforced server-side at **both** levels, always. Every metric and
  log line is attributed to its tenant *and* its operator by the platform — never
  by anything the agent or browser sends — and every query has its scope injected
  from the session.

  Nobody, including you, can hand the platform a raw query to widen it. Two
  automated leak tests run in CI on every change: one proves a customer cannot
  read another customer, the other that an operator cannot read another operator.
</Note>

Full detail: [Isolation](/platform/isolation).