# CX002 — Crew Workspace Access & Guest Module

## Extend Crew Access Inside Wedding Workspace

---

# ROLE

You are the Lead UX Designer, Product Architect, and Full Stack Engineer for INVEETAIRE.

Your responsibility is to extend the Crew experience inside the existing Wedding Workspace.

Do NOT redesign the Wedding Workspace.

Reuse every existing module whenever possible.

---

# OBJECTIVE

After entering an assigned Wedding Workspace, Crew users should be able to assist the Couple during wedding operations.

Crew should have access only to operational modules required on the wedding day.

Do NOT create a separate Crew Workspace.

Reuse the existing Wedding Workspace.

---

# WORKSPACE ARCHITECTURE

The existing Wedding Workspace must remain the single source of truth.

Crew enters the same workspace used by the Couple.

The only difference is which menus are visible.

Do NOT duplicate any page, controller, route, or module.

Reuse the existing implementation.

---

# SIDEBAR

When a Crew user enters a Wedding Workspace, display only:

Workspace

• Wedding Day

• Guest

Remove every administrative menu from the sidebar.

---

# WEDDING DAY MODULE

Reuse the existing Wedding Day module.

Crew users should have access to all functionality already available inside this module.

Do NOT create a Crew version.

---

# GUEST MODULE

Reuse the existing Guest module.

Crew users should have access to the same Guest module already implemented for the Couple.

This includes all existing Guest features, including:

• Guest List

• Guest Detail

• Guest Search

• Guest Group

• WhatsApp Sending

Do NOT duplicate the Guest module.

Do NOT build a separate Guest interface for Crew.

Reuse the existing UI, routing, controllers, services, and business logic.

---

# ACCESS RESTRICTIONS

Crew users must NOT see or access administrative modules such as:

• Wedding Settings

• Crew Management

• Workspace Management

• User Management

• Billing

• Reports

• Any system configuration pages

Navigation should remain focused on operational tasks only.

---

# USER EXPERIENCE

The transition from Portal to Workspace should feel seamless.

Portal

↓

Wedding List

↓

Open Workspace

↓

Wedding Workspace

↓

Wedding Day / Guest

Maintain the existing INVEETAIRE design language.

No visual differences should exist between Couple and Crew modules other than menu visibility.

---

# IMPLEMENTATION REQUIREMENTS

Reuse all existing:

• Controllers

• Services

• Models

• Routes

• Components

• Views

Avoid duplicate code.

Use role-based authorization where necessary.

Keep the implementation modular and maintainable.

---

# VALIDATION

Verify:

✓ Crew can enter assigned Wedding Workspaces.

✓ Wedding Day menu is visible.

✓ Guest menu is visible.

✓ Existing Guest module is reused.

✓ Existing Wedding Day module is reused.

✓ Administrative menus remain hidden.

✓ No duplicate implementation is introduced.

✓ Sidebar updates correctly based on workspace context.

✓ Responsive layout remains intact.

Run PHP lint (`php -l`) on every modified PHP file before completion.

Do not mark this sprint complete until every validation item passes.