Identityidentity.authtoolkit.comStatic preview

Account

Project

Environment

identity.authtoolkit.com

User Manual

Workflow-first guide for understanding AuthToolkit Console and moving through setup, keys, test, logs, health, and page help.

User Manual

AuthToolkit Console User Manual

A workflow-first guide for understanding the console, reviewing setup, testing actions, inspecting logs, checking health, and using page help.

This manual documents the workflow, not just features. Start with the required path, then use optional pages when you need deeper review.

Static manual preview. No live API wiring, real credentials, live search, live Knowledge Hub, or product execution is connected.

Required Setup Path

Main path

Home

available

Start the first-run journey.

Navigation

available

See Project, Build, Operate, Products, and utility routes.

Setup Completion

preview_ready

See what is complete, preview-ready, needs review, blocked, or future.

Project Settings

available

Review Project ID, API key previews, scopes, setup snippets, and safety warnings.

Console Settings

preview_ready

Review environments, integrations, product enablement, routes, origins, webhooks, and Commerce awareness.

Key Creation

preview_ready

Preview key type, scopes, expiration, safety confirmations, and one-time reveal behavior.

Test Console

preview_ready

Preview product action request/response with scope and Commerce entitlement checks.

Logs

preview_ready

Inspect trace IDs, decision IDs, audit event IDs, and timeline handoff.

Health

preview_ready

Review readiness, route status, issues, suggested actions, and troubleshooting.

Page Help

preview_ready

Understand page-scoped help and its limits.

Optional Review Steps

Helpful

Complete Surface Review

demo_only

Internal UX review for one-page surface completeness.

Product Modules

demo_only

Review Identity, Verification, Notification, Commerce, Marketing, Analytics, and QR Experience.

Retained Utility Routes

demo_only

Retained, legacy, and utility route continuity.

Knowledge Hub Boundary

future

Understand that the future global helper answers from Knowledge Hub only.

Foundation Pages

Workflow

Home

Open

The front door for the static console preview and active module lineup.

Why it matters: Home frames AuthToolkit as a shared control plane before builders choose a product.

What to do here: Read the platform pattern and open the first-run path.

Required

Open Navigation
Open Setup Completion

Optional

Review product cards
Open Page Help Preview

Static/demo-only. No live API wiring, real credentials, live search, or product execution is connected.

Navigation

Open

The console map for Project, Build, Operate, Products, and utility routes.

Why it matters: Builders can see how surfaces connect instead of guessing where to go.

What to do here: Find the shared setup surfaces and product modules.

Required

Review Project, Build, and Operate groups
Open Setup Completion

Optional

Review retained utility routes

Static/demo-only. No live API wiring, real credentials, live search, or product execution is connected.

Setup Completion

Open

The checklist for what is complete, preview-ready, needs review, and future.

Why it matters: It turns many surfaces into one setup path.

What to do here: Use the checklist to decide what to review before testing.

Required

Review progress summary
Open Project Settings

Optional

Inspect risk notes
Open Complete Surface Review

Static/demo-only. No live API wiring, real credentials, live search, or product execution is connected.

Project Settings

Open

The Supabase-style setup surface for Project ID, API URL, keys, snippets, scopes, entitlements, and test connection.

Why it matters: Builders need one place to know what to copy and what is safe.

What to do here: Review project connection values, key previews, scopes, snippets, and warnings.

Required

Review Project ID
Review API key previews
Read Service Role Key warning

Optional

Open Key Creation Flow
Open Console Settings

Static/demo-only. No live API wiring, real credentials, live search, or product execution is connected.

Console Settings

Open

The project/environment/integration settings preview.

Why it matters: Testing is clearer when builders understand environment, integration, routes, origins, webhooks, and Commerce awareness.

What to do here: Review environments, integrations, product enablement, routes, origins, webhooks, and readiness.

Required

Confirm selected environment
Review integration
Review Commerce awareness

Optional

Review allowed origins
Review webhook previews

Static/demo-only. No live API wiring, real credentials, live search, or product execution is connected.

Key Creation

Open

The static plan for future key creation and one-time reveal.

Why it matters: Builders can understand key type, scopes, expiration, and safety before real credentials exist.

What to do here: Review key type, scopes, expiration, confirmations, and generated preview.

Required

Choose key type conceptually
Review scopes
Read safety confirmations

Optional

Review lifecycle actions

Static/demo-only. No live API wiring, real credentials, live search, or product execution is connected.

Test Console

Open

The shared test surface for product action request/response previews.

Why it matters: Builders can see how key scope and Commerce entitlement affect an action before live execution.

What to do here: Review request preview, response preview, scope checks, entitlement checks, trace IDs, and handoffs.

Required

Review selected scenario
Inspect request and response
Check entitlement

Optional

Open Logs Preview
Open Health Preview

Static/demo-only. No live API wiring, real credentials, live search, or product execution is connected.

Logs

Open

The shared trace and timeline preview.

Why it matters: Logs explain what happened during a test without exposing internals or raw secrets.

What to do here: Inspect trace IDs, decision IDs, audit IDs, request/response summaries, timeline, and Health handoff.

Required

Review trace reference
Read timeline
Check audit summary

Optional

Open Health Preview

Static/demo-only. No live API wiring, real credentials, live search, or product execution is connected.

Health

Open

The shared readiness and troubleshooting preview.

Why it matters: Health shows what is ready, warning, blocked, or demo-only and points to the right owner.

What to do here: Review setup summary, readiness checks, route statuses, issues, and suggested actions.

Required

Review readiness checks
Review issues
Open suggested action

Optional

Use trace handoff
Return to Console Settings

Static/demo-only. No live API wiring, real credentials, live search, or product execution is connected.

Page Help

Open

The scoped helper pattern for explaining the current page only.

Why it matters: Non-coders can ask page-grounded questions without expecting a general chatbot.

What to do here: Review helper scope, suggested questions, answer previews, and Knowledge Hub boundary.

Required

Read page-only boundary
Review disabled widget input

Optional

Review Knowledge Hub fallback

Static/demo-only. No live API wiring, real credentials, live search, or product execution is connected.

Workflow Map

Static

Account

Workspace context for the builder or agency.

Project

The product-facing unit that owns Project ID and setup.

Environment

Development, staging, or production context.

Integration

App or backend connection preview.

Keys / Scopes

API key previews and access scope planning.

Setup

Copy values, snippets, entitlements, warnings, and checklist state.

Test Action

Request/response preview with scope and entitlement checks.

Logs / Trace

Trace, decision, audit, and timeline handoff.

Health

Readiness, route status, issues, and next actions.

Page Help

Page-only help for understanding the surface.

Go Live Later

Future phase after credentials, persistence, APIs, logs, and health are planned.

account → projectCreate context

Account contains projects.

project → environmentSelect runtime

Project setup changes by environment.

environment → integrationConnect app

Integration belongs to an environment.

integration → keys_scopesAuthorize safely

Keys and scopes define technical access.

keys_scopes → setupCopy setup

Setup values explain how to connect later.

setup → test_actionPreview action

Test Console shows the planned request and response.

test_action → logs_traceInspect result

Logs explain trace and audit handoff.

logs_trace → healthReview readiness

Health summarizes route and owner readiness.

health → go_live_laterPlan live phase

Live behavior comes only after boundaries are ready.

page_help → projectSupports every page

Page Help explains current page context only.

How Products Connect

Jobs

Identity

Protect access

Identity/Security owns credentials, scopes, sessions, access checks, identity decisions, and audit events.

KeysTest ConsoleLogsHealth

Commerce

Control plans and usage

Commerce owns entitlement, plan, usage, credits, metering, and commercial access.

Console SettingsTest ConsoleLogsHealth

Verification

Decide verification truth

Verification owns verified status and evidence while Notification only delivers messages.

NotificationLogsHealth

Notification

Deliver messages

Notification delivers email, SMS, push, templates, and delivery logs.

VerificationLogsHealth

Analytics

Understand reporting

Analytics reports from products and service events rather than owning source execution.

LogsProduct events

QR Experience

Add QR experiences

QR Experience can add scan and hosted experience workflows later without QRVerse live integration in this phase.

IdentityCommerceLogsHealth

Marketing

Send campaigns when allowed

Marketing is merchant-owned and depends on Commerce entitlement for campaign actions.

CommerceCustomer/product events

Who This Helps

Audience

Built for non-coders

The manual explains what to do next without requiring internal architecture knowledge.

Built for agencies and vibe coders

Teams can start with one product and grow into setup, testing, logs, health, and help.

Start small, add later

Identity can be the first complete demo module, then Commerce, Analytics, QR Experience, or Marketing can be added.

Workflow sells the platform

The path shows why AuthToolkit matters by connecting setup, keys, testing, observability, and readiness.

Boundaries

Static

Static/demo-only manual

The guide documents the workflow but does not perform live work.

No live credentials

Project Settings and Key Creation use previews only.

No live product execution

Test Console shows static request and response previews only.

Page Help is page-only

The helper explains current page information only.

Future global helper is Knowledge Hub-only

If the answer is not in Knowledge Hub later, it should say it is not there yet.

Commerce owns entitlement

Commerce controls plan, usage, credits, and commercial access.

Identity/Security owns credentials and access checks

Identity/Security owns validation, scopes, sessions, and access decisions.

Suggested Actions

Start with Navigation View Demo Companies Open Setup Completion Review Project Settings Review Console Settings Preview Key Creation Open Test Console Review Controlled Test Action Inspect Controlled Logs Review Controlled Health Inspect Logs Review Health Read Page Help

Start with Navigation

See the console map first.

View Demo Companies

See plain-English workflow examples for fake businesses.

Open Setup Completion

Review the checklist for what is ready or future.

Review Project Settings

Find Project ID, API key previews, snippets, scopes, and warnings.

Review Console Settings

Check environment, integration, routes, origins, webhooks, and Commerce awareness.

Preview Key Creation

Understand key type, scope, expiration, safety, and one-time reveal preview.

Open Test Console

Preview a product action request and response.

Review Controlled Test Action

See how Identity and Commerce decisions combine before product execution exists.

Inspect Controlled Logs

Follow controlled trace handoffs from Test Console into Logs.

Review Controlled Health

Review readiness meaning from controlled Identity and Commerce decisions.

Inspect Logs

Review trace, decision, audit, and timeline handoff.

Review Health

Check readiness, issues, routes, and suggested actions.

Read Page Help

Understand page-scoped help and its limits.