Dashboard Overview

The dashboard is the central workspace experience in SaaSStinger Lite.

After authentication and onboarding are complete, users interact with their workspaces through the dashboard.

The dashboard brings together:

• Authentication
• Workspace context
• Members
• Projects
• Notifications
• Audit logs
• Usage tracking
• Settings

What You'll Learn

In this guide you'll learn:

• How the dashboard is structured
• How workspace context works
• What information users see
• How dashboard data is loaded
• How different SaaSStinger Lite systems connect

Dashboard Flow

A user's journey into the dashboard follows this flow:

User Opens Application
          │
          ▼
Authentication Check
          │
          ▼
Email Verification Check
          │
          ▼
Workspace Check
          │
          ▼
Dashboard Loaded
          │
          ▼
Workspace Data Displayed

Each step ensures the user has the correct access before application data is displayed.

Dashboard Architecture

The dashboard is workspace-based.

A user does not see global application data.

Instead, the dashboard loads information belonging to the currently active workspace.

Authenticated User

        │

        ▼

Active Workspace

        │

        ├──────── Projects
        ├──────── Members
        ├──────── Notifications
        ├──────── Usage
        ├──────── Audit Logs
        └──────── Settings

Authentication Context

The dashboard depends on an authenticated user.

Before loading protected dashboard pages, SaaSStinger Lite verifies:

• User authentication status
• Email verification status
• Workspace membership
• Active workspace selection

Unauthenticated users are redirected to authentication flows.

Workspace Context

The active workspace determines what data appears throughout the dashboard.

The application uses:

activeWorkspaceId

to identify the current workspace.

Every workspace-related operation uses this context.

Examples:

• Loading projects
• Viewing members
• Creating invitations
• Reading notifications
• Viewing audit logs

Dashboard Sections

The dashboard contains several major areas.

Projects

Projects represent the primary workspace resources users interact with.

Users can:

• View projects
• Create projects
• Manage project resources
• Collaborate with workspace members

Projects are always scoped to the active workspace.

Members

The Members section allows authorized users to manage workspace collaboration.

Depending on permissions, users may:

• View members
• Invite users
• Change roles
• Remove members

Administrative actions are controlled through RBAC.

Invitations

Invitations allow workspaces to grow.

Authorized users can:

• Create invitations
• View pending invitations
• Revoke invitations

Accepted invitations become memberships.

Notifications

Notifications provide users with important workspace updates.

Users can:

• View recent activity
• Identify unread notifications
• Mark notifications as read

Notifications are user-specific while remaining connected to a workspace.

Activity and Audit Logs

SaaSStinger Lite provides two different activity systems.

Activity Feed

Designed for normal workspace awareness.

Examples:

• Recent changes
• Collaboration updates
• User activity

Audit Logs

Designed for administrative accountability.

Examples:

• Role changes
• Member removal
• Workspace modifications

Audit logs are available only to OWNER and ADMIN roles.

Usage Tracking

The dashboard can display workspace usage information.

Usage metrics include:

• Seats used
• Users created
• Invitations created
• Audit logs created

Currently, usage is tracked for visibility and future expansion.

Settings

Workspace settings allow authorized users to manage workspace configuration.

Depending on permissions, settings may include:

• Workspace information
• Profile preferences
• Security-related options

Dashboard Data Flow

When a dashboard page loads:

Dashboard Request

        │

        ▼

Verify Authentication

        │

        ▼

Load Active Workspace

        │

        ▼

Verify Membership

        │

        ▼

Fetch Workspace Data

        │

        ▼

Render Dashboard

This ensures users only receive data they are authorized to access.

Component Architecture

The dashboard is built using reusable components.

Examples include:

Dashboard Layout

├── Navigation
├── Workspace Switcher
├── User Menu
├── Content Area
└── Notifications

Feature-specific components remain separated by domain:

components/

├── projects
├── members
├── invites
├── notifications
├── settings
└── audit

Server and Client Responsibilities

SaaSStinger Lite separates responsibilities between server and client code.

Server Responsibilities

The server handles:

• Authentication verification
• Authorization checks
• Firestore operations
• Sensitive business logic

Client Responsibilities

The client handles:

• User interactions
• Forms
• UI state
• Loading states
• Displaying data

Architecture Note

Client components improve user experience.

Server-side validation protects the application.

Both layers work together to provide a secure SaaS architecture.

Extending the Dashboard

Developers can extend the dashboard by adding new workspace features.

Recommended approach:

1. Create a new domain folder.
2. Add server-side services.
3. Add authorization checks.
4. Add UI components.
5. Connect navigation.

Example:

New Feature

components/
    new-feature/

services/
    new-feature/

server/
    new-feature.server.ts

app/dashboard/
    new-feature/

Best Practices

• Keep dashboard features workspace-aware.
• Validate permissions server-side.
• Reuse existing services.
• Keep business logic outside components.
• Follow the existing folder architecture.

Common Mistakes

Loading Data Without Workspace Checks

Every workspace resource should be scoped to the active workspace.

Putting Business Logic in Components

Keep complex operations in services or server actions.

Skipping Authorization

A visible button does not provide security.

Always protect the operation itself.

Related Articles

• Authentication
• Workspaces
• Members
• RBAC & Permissions
• Audit Logs
• Usage Tracking

Next Steps

You have completed the Core Concepts section.

Continue with Building Features to learn how to extend SaaSStinger Lite while maintaining its architecture and security model.