Route Map

The main product routes across auth, account, organization, admin, and integration surfaces

Page-aware AI

Ask AI about this page

Get answers grounded in the live Obelisk docs set, with source links, selected-text explainers, and prompts for the next document to read.

Use this page when you want the shortest possible map of the product surface.

How To Read The Product

/auth/*                  account entry
/dashboard               personal home and organization selection
/dashboard/organization  tenant workspace
/dashboard/admin         platform governance
/api/*                   machine-facing or internal surfaces

Browse By Surface

Key account-entry and personal routes:

  • /auth/sign-up
  • /auth/sign-in
  • /auth/verify
  • /auth/forgot-password
  • /auth/reset-password
  • /dashboard
  • /dashboard/onboarding
  • /dashboard/choose-plan
  • /dashboard/organization-invitation/[invitationId]
  • /dashboard/settings
  • /dashboard/preferences
  • /dashboard/activity

Use these routes for sign-in, onboarding, workspace selection, and personal settings.

Main tenant routes under /dashboard/organization:

  • /dashboard/organization
  • /dashboard/organization/activity
  • /dashboard/organization/analytics
  • /dashboard/organization/leads
  • /dashboard/organization/chatbot
  • /dashboard/organization/contract-lab
  • /dashboard/organization/indexer-lab
  • /dashboard/organization/channel-lab
  • /dashboard/organization/integrations
  • /dashboard/organization/api-keys
  • /dashboard/organization/webhooks
  • /dashboard/organization/notifications
  • /dashboard/organization/audit-log
  • /dashboard/organization/support
  • /dashboard/organization/settings

These routes require an active organization in session and redirect back to /dashboard or /dashboard/choose-plan when prerequisites are missing.

Platform admin routes:

  • /dashboard/admin/users
  • /dashboard/admin/organizations
  • /dashboard/admin/notifications
  • /dashboard/admin/app-config
  • /dashboard/admin/platform-alerts
  • /dashboard/admin/platform-alerts/export

These routes require platform role admin.

Current operator-facing integration routes:

  • GET /api/organization/notifications/stream
  • GET /api/public/v1/deployments/indexer
  • POST /api/public/v1/deployments/indexer
  • GET /api/public/v1/deployments/indexer/[id]
  • GET /api/public/v1/deployments/channel
  • POST /api/public/v1/deployments/channel
  • GET /api/public/v1/deployments/channel/[id]

Important internal platform routes also exist, such as Stripe webhooks and internal provisioning or alert endpoints, but they are not primary customer-facing integration surfaces.

Route Gating Rules

Route familyMain gate
/auth/*public
/dashboardsigned-in user
/dashboard/onboardingsigned-in user who has not completed onboarding
/dashboard/choose-plansigned-in user with active organization when billing requires plan selection
/dashboard/organization/*signed-in user, active organization, verified membership
/dashboard/admin/*signed-in user with platform role admin
/api/organization/notifications/streamsigned-in user, active organization, verified membership
/api/public/v1/*valid API key with required scopes

A Useful Mental Model

If you are ever unsure where a workflow belongs, ask:

  1. is this personal account setup?
  2. is this tenant-local work?
  3. is this platform-wide governance?
  4. is this machine-to-machine automation?

That framing usually tells you the right route family immediately.

On this page