{"slug":"strategy/business-strategy/03-user-journeys-and-activation","title":"03 — User Journeys and Activation","section":"strategy","sectionLabel":"Strategy","status":"unclassified","type":"document","path":"strategy/business-strategy/03-user-journeys-and-activation.mdx","bytes":2299,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n**Status:** Canonical journey; implementation and production evidence vary\n\n## Primary onboarding journey\n\n```text\nClerk sign-in\n→ active organisation selected\n→ Gateway verifies user and membership\n→ account and tenant resolved\n→ Integration Manager opens\n→ connector selected\n→ Nango provider authorisation\n→ provider workspace resolved\n→ server-owned connector binding created\n→ schema compatibility validated\n→ initial load and normalisation\n→ Pipeline promotion into Spine\n→ Projection Engine composes Workbench\n→ Twin becomes contextually available\n```\n\nThe browser cannot supply authoritative user, account, tenant, Spine, provider\nworkspace, or schema identifiers.\n\n## Connector activation journey\n\nThe visible stages are:\n\n1. Authentication\n2. Provider workspace resolution\n3. Spine binding\n4. Schema validation\n5. Initial sync\n6. Operational readiness\n\nIf any mandatory evidence is missing or inconsistent, the binding is stale.\nThe user sees the failed stage and a precise repair or reconnect action.\n\n## Returning user\n\nGateway revalidates the Clerk session and active membership, resolves the tenant,\nloads a permission-scoped `SharedWorkbench`, and exposes only operational\nconnectors and capabilities. A projection cache miss may show an explicit\npartial-evidence state; it may not silently show demo data.\n\n## Marketplace or MCP entry\n\nAI-host and MCP distribution are additional Bridge entry points, not separate\nproducts. Each client must use the public OAuth-protected nineteen-tool MCP and\nresolve to the same IntegrateWise user, account, and tenant contracts.\n\nHost reuse of other connected tools is **Unverified** until a host proves one of\nthese modes:\n\n- **HOST_DELEGATED:** the host explicitly delegates a bounded capability.\n- **HOST_ORCHESTRATED:** the host invokes both systems and returns only permitted\n  results.\n- **DIRECT_FALLBACK:** the user authorises the provider directly through\n  IntegrateWise.\n\nIntegrateWise never assumes access to another app's private credentials.\n\n## Activation acceptance\n\nActivation succeeds only when the user can see the correct tenant, an\noperational connection, its schema and sync evidence, the resulting Workbench\nprojection, and the permitted Four Button actions.\n"}