Onboarding & First Sign-In
One sign-in through OneAuth — the single controlled entry to the Self-Organizing Workspace.
The user arrives through the single controlled entry — OneAuth — not an app-specific login. This is the gateway that resolves identity, tenant, workspace, roles, and entitlements before any work begins.
OneAuth Entry Points
- Hosted session: User arrives with a delegated host session (e.g., inside a host platform)
- Fresh sign-in: User provides credentials through OneAuth's controlled entry
- Re-entry: Returning user resumes from last meaningful event via continuity threads
What OneAuth Resolves
| Aspect | Description |
|---|---|
| Identity | Verified principal (user or service identity) |
| Tenant | Organization/entity the user belongs to |
| Workspace | Specific work context within the tenant |
| Roles | Permission set defining可执行 actions |
| Entitlements | Granted capabilities and connected apps |
| Policies | Governance rules applicable to this user/tenant |
Entry Flow
- Authenticate — User signs in via OneAuth (host-owned or direct)
- Resolve — Identity → tenant → workspace → roles → entitlements → policies
- Establish — Entry context created; continuity threads preserved from prior sessions
- Proceed — User moves to Stage 2 (Discover) with context already attached
Step 1 — Sign in through OneAuth
The user arrives through the single controlled entry — OneAuth — not an app-specific login.
- User does: authenticates once (or arrives with a delegated host session).
- System does: resolves identity → tenant → workspace → roles → entitlements → policies, and establishes entry context.
- Underneath: if IntegrateWise runs inside a host, OneAuth verifies the delegated identity; the host owns the session either way.
Step 2 — Resolve Context
The entry context is resolved and continuity threads from prior sessions are preserved.
- User does: reviews the resolved identity, tenant, and workspace context.
- System does: checks for any interrupted continuity threads from previous sessions and surfaces the last meaningful event, pending continuation, and owner.
- Underneath: when the user returns, interrupted continuity threads resurface with the last meaningful event, the pending continuation, and the owner — so a paused deployment or half-finished QBR picks up exactly where it stopped.
Step 3 — Proceed to Discovery
With identity and workspace resolved, the user moves to discover what the ecosystem offers.
- User does: reviews the connections and capabilities available to their workspace.
- System does: transitions to Stage 2 — Discover, where the Capability Resolver intersects everything discovered against tenant policy, role, and context — surfacing only what this user can actually do.
- Underneath: Capability Resolver intersects everything discovered against tenant policy, role, and context.
Quick Start from Onboarding
Read the frozen reference
Start with Canonical Reference — the four corrections (D1 is operational not SSOT, Pipeline governs all writes, departmental tables without silos, Twin contextual) are frozen there.
Trace the user arc
User Journey walks Enter → Discover → Connect → Load → Normalize → Activate → Work → Loop with gates and blockers.
Check current risks
Commit Review documents the pending commit risk: 233 typecheck errors / 5 failing test files vs. later "100% green" claims, and why git add . must be split.
Built 2026-08-20 · Nextra 4 · Theme nextra-theme-docs