Path: Day-0 admin
Audience: customer admins. Time: about 45 minutes. Prerequisite: a tenant invite (there is no public self-serve).
By the end of this path you will have a live tenant with its organization identity set, people invited, security reviewed, one agent shaped, and one governed session run to a recorded outcome. That loop (session, approval, audit) is first value, and it is the definition of done.
Work the steps in order. Each step links the Product page that shows how; this path adds no new reference of its own.
Step 1: orient (5 min)
Section titled “Step 1: orient (5 min)”- Read What is PRESHos Platform end to end.
- Read Core concepts: tenant, hostname (hostname wins),
org_idvscompany_id, environments, sessions, approvals, connectors.
Check: you can complete this sentence: “PRESHai operates ____ for us so our agents can ____ under ____.”
Step 2: land on Day-0 (10 min)
Section titled “Step 2: land on Day-0 (10 min)”- Follow Day-0 for customer admins steps 1 to 4: accept the invite, land on your tenant hostname, wait through
/preparingonly if you see it, complete the onboarding wizard (organization name is required; defer the rest).
Check: signed in at the correct hostname; org name correct in Settings.
Step 3: set the foundation (10 min)
Section titled “Step 3: set the foundation (10 min)”- Confirm the organization identity: Settings: Org (companion: Settings: Org).
- Invite your people: Settings: People (companion: Settings: People).
- Review the security posture: Settings: Security (companion: Settings: Security).
- Assign roles and membership: Settings: Roles (model: Roles & membership).
- Request the connectors you actually need: Integrations / Connectors. Remember code is not connected: only what is provisioned for your tenant counts.
Check: org name correct, at least one colleague invited, security reviewed, roles assigned, connector needs filed as requests.
Step 4: shape one agent (10 min)
Section titled “Step 4: shape one agent (10 min)”- Decide what deserves an agent and what does not: When to build an agent.
- Configure it: Agent config.
- Split off reusable specialists: Subagents.
- Register what it may use, only what the workload needs: MCP registry, Plugin registry, Skill registry, Tool registry, Model registry.
- Confirm the environment it will run in: Environments. If none is visible, stop and ask the PRESHai team.
Check: one agent configured in one visible environment, with a deliberate registry set.
Step 5: reach first value (10 min)
Section titled “Step 5: reach first value (10 min)”- Run Your first session: one small, real goal in the environment from Step 4.
- Let an approval gate fire and decide deliberately: Approving agent actions.
- Review the recorded outcome: Observability and Sessions.
Check (definition of done):
- Signed in at the correct tenant hostname
- Org identity confirmed in Settings
- One governed session completed with a recorded outcome
- At least one approval decision made (or a clear reason none was required)
Known thin spots (honest gaps)
Section titled “Known thin spots (honest gaps)”- First approval in the queue: the decision method is at Approving agent actions; the product reference is the Approvals section.
- Connector bind beyond HubSpot: the only worked binding pass is E2E: HubSpot inbound import. The bind surface itself is at Connector binding. Other connectors follow the same contract (Extend a connector) but have no step-by-step here yet.
- Tenant switch: multi-tenant identity is covered by the My tenants model; the membership list and per-hostname Open links are at Switching tenants.
What next
Section titled “What next”- Say it right from now on: Naming guide.
- Users start at the User sessions path; field builds run through the FDE path.