Platform ops
This section is for the PRESHai operating team, the people who provision tenants and keep the platform healthy. Tenant admins: your manual is Tenant admins. Everyone doing daily agent work: Tenant users.
Sources: rewritten from docs/runbooks/tenant-lifecycle.md and customer-onboarding.md via product-repo access. Routes, roles, and workflow names below are from those sources. Anything beyond them is marked not in pasted sources.
Guides
Section titled “Guides”New-tenant checklist: the concrete Create-tenant sequence. /admin/tenants, CRM-backed org, provision-tenant workflow, readiness, invite, first session.
Provisioning and internals: access model, control plane, the provision-tenant steps, hostnames, aliases, partner admins, object defaults.
Ops runbooks: preparing stalls, hostname and alias issues, onboarding rescue, connector intake, with the real surfaces.
Access: who can do ops
Section titled “Access: who can do ops”Ops work needs both PRESH org-1 membership and the platform_ops role in org 1. Membership alone is not enough.
Surfaces: /admin/tenants (UI) and /api/v1/admin/* (API, guarded by requirePlatformOps).
Org 1 is the PreshAI control plane: it cannot be suspended or deprovisioned. Any tooling that suspends or deprovisions tenants must exclude org 1. Treat a missing exclusion as a bug.