Settings: Org
Settings Org is where the tenant’s identity lives. Get the required parts right during Day-0; revisit the rest deliberately, not accidentally.
Fields
Section titled “Fields”| Field | Required? | Effect | Guidance |
|---|---|---|---|
Organization name (org-name) |
Yes | Display identity across the product and audit | Set carefully on Day-0. Renames later are possible but noisy, since records already written keep history. Use the legal or commonly recognized name. |
| Domain | Optional | Identity and branding context | Add when you know the canonical organizational domain. Do not guess. |
| Branding | Optional | Tenant presentation touches | Cosmetic. Safe to defer; revisit when the tenant is otherwise healthy. |
This wiki deliberately documents only Org, People, and Security under Settings. Agent configuration and the core registries (MCP, plugins, skills, tools, models) live under Agent Ops, not Settings. If your tenant shows additional Settings sections, treat the product UI as the source of truth for those.
Org identity checklist
Section titled “Org identity checklist”- Organization name matches the recognized name (check with your team lead, not just your memory)
- Spelling, capitalization, and suffix (Inc, LLC, and similar) decided once
- Domain added only when canonical and verified
- After any change: sign out and back in to check that the tenant still reads correctly everywhere you look
Why org identity matters
Section titled “Why org identity matters”- Sessions, approvals, and audit entries scope to the org (
org_id). A sloppy org identity makes every downstream record harder to trust. See Core concepts. - Support and provisioning conversations with the PRESHai team key off your tenant hostname and org name. Ambiguity here slows every request.
- Multi-org setups (a provider across end-customer orgs) depend on crisp org boundaries. If that is you, coordinate with Platform ops before renaming anything.