onboarding-state-machine

Track onboarding progress by defining steps as explicit states within a central registry and persisting progress in a per-tenant store. This enables reliable progress tracking across tenants and users, allowing you to gate features and resume sessions seamlessly.

Yes, you can gate features by applying middleware that checks if all required onboarding steps are complete. The state machine restricts access to features until a tenant finishes the necessary steps, ensuring users only see unlocked capabilities.

An onboarding state machine handles resuming progress by persisting per-tenant step completion in a database. When a user returns, the service interfaces query the progress store to resume the onboarding flow exactly where they left off.

Trigger analytics by emitting domain events when the state machine transitions between onboarding steps. The system fires these events upon step completion or state changes, allowing your analytics platform to capture user progress data.

The best way to define onboarding steps is using a central step registry that distinguishes between required and optional states. This registry interfaces with the persisted progress store to manage per-tenant completion and gate features appropriately.

Yes, you need a database schema for tenants and steps to manage onboarding progress. The state machine requires this persisted store to track explicit states, trigger domain events, and support the gating middleware effectively.