Tenant Setup
Create a tenant, define its isolation boundary, and seed the first operator.
A tenant is the unit of isolation in Govula. Every row in every governance table belongs to exactly one tenant, and Postgres row-level security enforces that boundary in the database — not just in application code.
What setup creates
- A tenant record with a stable identifier used in every audit entry.
- RLS policies that prevent cross-tenant reads or writes.
- An initial operator account with elevation capability for first-day actions.
- A seeded Statement of Applicability — see SoA Engine.
After setup
- Run the Activation Flow to take a first verified action.
- Review the Authority Model before inviting more users.
- Configure Environments for promotion paths.
- Check Access Problems if the first operator can't sign in.
You are here · Deploy · step 1
Deployment Hubnext step
Pick a deployment topology for the tenant you just defined.
Stuck? Access Problems
What should I do next?
Activation Flowprimary
continues in "deploy"
Ranked using IA v1 graph + intent map + glossary density (deterministic; no AI inference).