Dashboards & Workflows

SaaSyBase is already structured into an admin control plane and a user self-service dashboard. This page helps you understand what each area already does and where your product-specific work should go.

Admin dashboard overview

The admin dashboard at /admin is the operating system for your SaaS. It is organized into functional groups rather than a flat list of screens.

Group	What is there
Overview	Dashboard home with aggregate stats
Users & Access	Users, organizations, moderation
Finances	Transactions, purchases, subscriptions, coupons, plans
Platform	Theme, pages, blog, email templates, settings
Support & Analytics	Support tickets, notifications, analytics, traffic
Developer	System diagnostics, API reference access, logs, and maintenance tooling

Notable admin features

/admin/system for runtime diagnostics, storage/webhook wiring checks, bearer-token visibility, and maintenance status
/admin/maintenance for maintenance mode and repair tools
/admin/one-time-plans for non-recurring offers
/docs/api for the public API reference formerly exposed under admin
/admin/logs for persisted WARN and ERROR system log entries with stats and pagination
/admin/users and /admin/organizations for user suspension, organization suspension, and organization restore workflows
/admin/emails, /admin/plans, /admin/settings, and /admin/organizations are all shipped and actively used in the current admin UI

The system page

/admin/system is the quickest operational checkpoint in the admin area. It aggregates the environment, runtime/build details, storage configuration, webhook readiness, internal bearer-token wiring, and maintenance mode into one page.

Use it when you need to verify that a deployment is actually running with the expected auth/payment/storage settings before digging into logs.

User dashboard overview

The user dashboard at /dashboard is already a full self-service application shell. Not every existing route is exposed in the primary sidebar, so it helps to distinguish between what exists and what is directly discoverable.

Page	Path	Primary nav?	Purpose
Home	/dashboard	Yes	Overview plus the shipped demo workspace
Onboarding	/dashboard/onboarding	Yes	New-user setup flow
Plan	/dashboard/plan	No	Current plan, pending changes, and upgrade path
Billing	/dashboard/billing	No	Subscription and payment management
Transactions	/dashboard/transactions	No	Payment history
Team	/dashboard/team	Yes	Invites, members, and team settings
Profile	/dashboard/profile	No	Profile, sessions, export, and account deletion
Settings	/dashboard/settings	No (redirect)	Redirects into the merged profile/settings experience
Notifications	/dashboard/notifications	Yes	Notification center
Support	/dashboard/support	Yes	Tickets and replies
Coupons	/dashboard/coupons	No	Redeemed and pending coupons

In the current primary sidebar, only the main dashboard, onboarding, team, support, and notifications are directly exposed. Other routes exist and work, but they are currently reached by deep links, redirects, or workflow-specific entry points.

Note

That split is intentional. The primary sidebar favors the most common daily flows, while billing, profile, coupons, and some operational pages stay reachable from contextual links so the default navigation does not become overloaded.

Workspace switching and support workflows

Workflow	Where it lives	What it does
Workspace switching	Dashboard sidebar footer	Lets the user move between their personal workspace and team workspaces using the auth-provider organization switcher.
App-managed active workspace	/api/user/active-org	Stores or clears the active organization id in an httpOnly cookie for app-managed workspace selection.
Support center	/dashboard/support and /admin/support	Users open tickets and admins reply/manage status with notification and email hooks.

These workflows matter because billing, feature access, token spending, and team pages all depend on the currently active workspace context.

Note

Workspace context also now drives automatic token spending behavior: organization context uses shared workspace balance, while personal context uses paid and then free balance.

Legacy routes and redirects

Some routes are intentionally retained as redirects so older links or earlier product shapes do not break.

/dashboard/account redirects to /dashboard/profile
/dashboard/editor and /dashboard/sassyapp redirect to the main dashboard
/admin/api now redirects to /docs/api
/admin/moderator-activity is kept as a legacy redirect to moderation

Where to build your product logic

Most teams should keep the shipped business infrastructure and replace the demo workspace with their actual app.

Area	When to use it
app/dashboard/(valid)	New user-facing product pages that require auth
components/	Reusable product UI
lib/	Business logic, orchestration, and integrations
app/api/	Product-specific API endpoints
app/admin/(valid)	Only if your admins need new internal tooling

Tip

The main dashboard page is the intended place to replace the shipped SaaSyApp demo experience with your own application workflow.

In practice, most product teams leave the admin surface largely intact and focus their customization in app/dashboard/(valid), related components, and product-specific API routes.