Skip to content
PRESHaiPRESHaiPRESHos Platform

Org

Settings Account Detail is where the tenant identity lives, under the General tab (Branding sits in its own tab). The editable fields are the organization name (with Save) and the time zone. The slug and workspace hostname are read-only identifiers. Verified email domains list each domain with its status. Optional setup items below never block day-one use; complete them when the team is ready.

Get the organization name right during Day-0; revisit the rest deliberately, not accidentally.

  • Organization name is the display identity across the product and audit. Renames later are possible but noisy, since records already written keep history. Use the legal or commonly recognized name.
  • Time zone sets how datetime fields show. Storage stays in UTC; users can override the display zone on their own profile.
  • Slug and workspace hostname identify the tenant. Confirm you are in the right tenant before changing anything: check the hostname first.
  • Verified email domains prove which domains belong to the org. Add them when canonical and verified; do not guess.
Settings Account Detail General tab with organization name, time zone, slug, workspace hostname, and verified email domains

Branding, members, SSO: which page

Section titled “Branding, members, SSO: which page”

Account Detail splits identity across tabs and pages. General (this page) holds the organization name, time zone, slug, hostname, and verified email domains. Branding sits in its own tab on the same surface. Members live in People, not on an Org tab. Single sign-on and directory sync live in Security under the SSO / IDP tab, not in Org.

  • Branding changes are cosmetic and safe to defer past Day-0; org-name changes are not.
  • Membership questions (invite, pending, offboard) go to People.
  • Sign-in questions (SSO, SCIM, group-to-role mapping) go to Security.

Organization tabs

Section titled “Organization tabs”

Each tab on the organization surface has its own short page. General identity (this page) holds the organization name, time zone, slug, hostname, and verified email domains; the rest live here:

  • Org SSO (/settings/organization/sso): how this org authenticates and which provider backs it.
  • Org branding: tenant presentation. Cosmetic, safe to defer.
  • Org members: the org-scoped read view. Admin actions live in People.
  • Org audit: the org-scoped record of what changed, who changed it, and when.
  • Org egress: where this org’s data is allowed to leave to.
  • Org agents: which agents are available to this org.
  • Org data export: bulk export discipline across the egress boundary.

Screenshot captures for these tabs are wired into each page below.

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
  • Time zone matches where the team reads timestamps day to day
  • 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.

What next

Section titled “What next”