# RC-016B — Platform Administration Refinement & Workspace Architecture Finalization

Act as Senior Software Architect, Senior Backend Engineer, Senior Product Designer, and Senior QA Engineer.

This release is RC-016B.

Objective:

Refine and finalize the Platform Administration architecture introduced in RC-016.

This is NOT a feature release.

This is NOT a UI redesign.

This release only improves workflow, information architecture, administration flow, and prepares the platform for future modules.

Do NOT implement Budget Planner.

Do NOT implement Timeline Planner.

Do NOT implement Vendor Management.

Do NOT redesign Invitation themes.

Do NOT modify Landing Page.

====================================================
PART A
Workspace Provision Flow
====================================================

Current flow is too short.

Replace it with:

Create Workspace

↓

Workspace Created

↓

Create Couple Account

↓

Assign Crew (Optional)

↓

Finish

The Workspace should never exist without an Owner Couple.

Assign Crew is optional.

Display a clean success summary before returning to the dashboard.

====================================================
PART B
Workspace Architecture Rules
====================================================

Enforce the following business rules:

One Couple Account

=

One Workspace

Couple accounts may NEVER own multiple workspaces.

Crew accounts may belong to multiple workspaces.

Super Admin can access every workspace.

Never duplicate workspace ownership.

====================================================
PART C
Administration Menu Structure
====================================================

Reorganize the Admin navigation.

Workspace

- Workspace List
- Create Workspace

Workspace Users

- Couple Accounts

Crew Management

- Crew Accounts
- Workspace Assignment

Commercial Plans

Theme Management

Settings

The separation between Couple Users and Crew Users must be very clear.

====================================================
PART D
Workspace Assignment
====================================================

Crew Management becomes global.

One Crew

↓

Many Workspaces

One Workspace

↓

Many Crew

Workspace Users page only manages Couple Owner accounts.

Crew assignment is managed only inside Crew Management.

====================================================
PART E
Crew Login Flow
====================================================

Crew login should never immediately enter a workspace.

Flow:

Login

↓

Crew Home

↓

Assigned Workspace List

↓

Select Workspace

↓

Enter Workspace

If only one workspace exists,

redirect automatically.

====================================================
PART F
Workspace Switcher
====================================================

Inside Crew Portal

Display current workspace.

Allow workspace switching without logout.

Only assigned workspaces appear.

Remember the last selected workspace.

====================================================
PART G
Super Admin Workspace View
====================================================

When Super Admin opens a workspace:

Display a persistent information banner.

Example:

Viewing Workspace

Holy Matrimony

Mode

Super Admin

Button

Return to Admin

Super Admin never impersonates Couple.

====================================================
PART H
Super Admin Dashboard
====================================================

Transform the dashboard into a SaaS business dashboard.

Summary Cards

Total Workspaces

Active Workspaces

Upcoming Events

Today's Events

This Week Events

Commercial Summary

Starter

Pro

Custom

Event Summary

Engagement

Wedding

Custom

Upcoming Event Widget

Display

Couple

Workspace

Event Type

Date

Status

Recent Workspace Widget

Newest workspaces.

Recent Activity Widget

Workspace Created

Invitation Published

Crew Assigned

Guest Imported

Quick Actions

Create Workspace

Search Workspace

Manage Crew

Manage Plans

====================================================
PART I
Commercial Plan Architecture
====================================================

Define capability metadata.

Starter

Purpose

Engagement

Guest Limit

150

Pro

Purpose

Wedding

Guest Limit

500

Custom

Unlimited

Configurable Guest Limit

This release only defines the architecture.

Do NOT implement feature gating.

====================================================
PART J
Workspace Lifecycle
====================================================

Standardize lifecycle.

Draft

Preparing

Published

Running

Completed

Archived

Suspended

Dashboard statistics should use these statuses.

====================================================
PART K
Global Search
====================================================

Improve Workspace Search.

Search by

Workspace

Couple Name

Groom

Bride

Username

Email

Phone

Slug

Event Date

Plan

Status

Crew

====================================================
PART L
Preparation for Future Releases
====================================================

Prepare the platform architecture for

RC-017 Budget Planner

RC-018 Timeline Planner

RC-019 Vendor Management

Do NOT implement these modules.

Only prepare navigation placeholders, route stubs, permission stubs, and clean extension points if necessary.

====================================================
PART M
Verification
====================================================

Verify

Workspace Creation

Couple Creation

Crew Assignment

Crew Login

Workspace Switching

Super Admin View Mode

Workspace Search

Commercial Plans

Dashboard Statistics

PHP Syntax

Browser Testing

Responsive Testing

====================================================
Deliverables
====================================================

Provide a complete walkthrough including

Architecture overview

Modified files

Controllers

Models

Views

Routes

Verification

PHP syntax validation

Browser testing

Responsive testing

====================================================
IMPORTANT
====================================================

This is an architecture refinement release.

Prioritize maintainability over adding new features.

Avoid unnecessary UI redesigns.

Keep all existing design language.

Do not introduce regressions.

The platform after RC-016B should be considered the finalized SaaS administration foundation before entering RC-017 (Budget Planner).