Dashboard architecture
The navigation model, onboarding flow and overview structure for the authenticated product.
Primary navigation
Twelve areas
Each area surfaces a product or a platform-level concern. Where a public page describes the underlying capability, the entry links to it.
- 01OverviewWhat is happening, what requires attention, and what to do next.Read more →
- 02OrganizationsOrganization settings, environments, teams, roles and invitations.Read more →
- 03CustomersCustomer list, unified profiles, segments and support history.
- 04WalletsWallet list, creation, security setup and balances.Read more →
- 05RewardsReward programmes, the rule builder, testing and activation.Read more →
- 06TokensAsset creation, supply, utility and deployment.Read more →
- 07AI StudioBusiness assistant, action review and trust controls.Read more →
- 08AnalyticsGrowth, engagement, retention and AI insights.Read more →
- 09MarketplaceBrowse, review permissions and install extensions.Read more →
- 10DevelopersProjects, API keys, webhooks, event explorer and sandbox.Read more →
- 11SecuritySecurity posture, MFA coverage, sessions and access reviews.Read more →
- 12SettingsOrganization profile, billing, notification preferences and policy.
Utility navigation
Always available
Six controls in the top right, on every screen.
- SearchGlobal search across every entity type.
- NotificationsIn-app delivery of the seven notification categories.
- HelpDocumentation, support and keyboard shortcuts.
- Organization SwitcherMove between organizations without losing context.
- Environment SwitcherSwitch between Sandbox and Production.
- User MenuProfile, sessions, preferences and sign out.
Command palette
Everything reachable from ⌘ K
Navigation and action in one surface, so the sidebar is never the only route to a task.
- Navigate to product
- Search customer
- Create reward
- Create token
- Generate API key
- Invite team member
- View documentation
- Open AI assistant
Overview
The first screen answers three questions
Everything on the overview earns its place by answering one of them.
- What is happening?
- What requires attention?
- What should I do next?
Layout, in order
- 01Organization Header
- 02Key Metrics
- 03Activity Feed
- 04AI Insights
- 05Product Status
- 06Recommended Actions
- 07Recent Events
What it measures
- Active customers
- Wallets created
- Rewards issued
- Rewards redeemed
- Tokens in circulation
- API requests
- AI actions
- Monthly growth
These are metric definitions. No figures appear here — there is no data, and an invented number would be a fabricated metric.
Onboarding
Creating an organization takes six steps
Team setup can be skipped. Every other step is required before an organization exists.
- Step 1
Business Information
Organization name · Legal name · Website · Logo · Country · Time zone · Default currency · Primary language
- Step 2
Business Type
Retail · Gaming · Hospitality · Education · SaaS · Healthcare · Community · Enterprise · Other
- Step 3
Product Selection
Customer Identity · Wallets · Rewards · Business Tokens · AI Studio · Analytics · Developer APIs
- Step 4Optional
Team Setup
Email · Role
- Step 5
Review
Organization details · Selected products · Team invitations · Estimated configuration · Security settings
- Step 6
Create Organization
Once it exists
- Create a wallet
- Launch a reward program
- Connect your application
- Invite your team
Rules
Constraints this architecture holds to
- Navigation reflects the modules an organization has enabled, not every module that exists.
- The active environment — Sandbox or Production — is visible on every screen.
- Search is reachable from every screen, including by keyboard.
- Navigation depth does not exceed three levels.
- Moving between marketing pages and the dashboard does not lose context.
- One concept per screen: each screen has a single primary purpose and one primary action.
Want an account when the console opens?
Access is reviewed before an account is created. Tell us what you plan to run.