Projects are the central workspace for delivering client work. Every project contains a Kanban task board (with submission and review workflows), a knowledge base (with block-based WYSIWYG editor, slash commands, and page hierarchy), and an integrated chat channel for team communication. Projects are linked to orders, so revenue and delivery are always connected.

Navigate to Work → Projects in the sidebar. Youʼll see a grid of project cards showing progress bars and task counts. Click any card to enter the project workspace.

Creating a Project

1. Click Create Project (Admin/Manager only)
2. Enter the project name and description
3. Assign a project manager (employee)
4. Add team members who will work on the project
5. Click Save — the project appears in the grid

Project Roles

• Admin/Manager — Can create projects, manage settings, add/remove members, delete projects
• Project Members — Can view and work on tasks, access the knowledge base, participate in project chat
• Non-members — Cannot see or access the project

Project Tabs

Each project has two tabs accessible via query parameters: Board (?tab=board) for Kanban task management and KB (?tab=kb) for the Knowledge Base. Switch between them using the tab bar.

Project Grid

The main projects page shows color-coded project cards with progress bars (completed/total tasks), status badges (active/completed), and search/filter by name or status.

Kanban Board

Four-stage board: To Do → In Progress → Review → Complete. Tasks show title, description, priority (Low/Medium/High), assignee avatar, due date (with timezone), links, files, and creator. Actions per stage: Start (move to In Progress), Request Review (move to Review with submission), Approve/Reject (move to Complete or back), Reopen (move back to To Do).

Task Creation & Editing

Create tasks with: title, description, assignee (employee), priority (Low/Medium/High), deadline (datetime with timezone), external links (multiple), and file attachments (5MB limit). Edit any task field or change its status. Delete tasks as needed.

Task Submission & Review

When work is complete, submit the task with proof (links and file attachments) via the SubmitReviewDialog. Reviewer can approve (moves to Complete) or reject with feedback (moves back to In Progress). This enforces quality control on deliverables.

Knowledge Base

Rich WYSIWYG editor with 11 block types: Text, Heading, Image, Divider, Checklist, Bullet List, Numbered List, Code, Callout, Quote, File, and Link. Features include:

• Slash Commands — Type / to insert any block type via command menu
• Drag & Drop — Reorder blocks by dragging
• Page Hierarchy — Nested pages with parent/child relationships and page icons
• Sidebar Tree — Navigate pages in a collapsible sidebar tree
• Auto-Save — Changes are debounced and auto-saved as you type

Project Settings

Edit project name, description, and status (active/completed). Manage team members with a searchable multi-select dropdown. Mark project as complete (archives it) or reopen. Delete project if needed. All changes to members sync to the project chat.

Project Chat Sync

When you add or remove a project member in Project Settings, the following happens automatically: employee email → global user ID mapping, user is added to/removed from the project chat channel, a system message is posted announcing the change.

Project Lifecycle

1. Create project and assign manager + members
2. Set up KB pages with project scope, requirements, and documentation
3. Create tasks on the board and assign to team members
4. Team works on tasks, moving them through the board
5. Completed work is submitted for review
6. Reviewer approves or requests changes
7. When all tasks are Complete, mark the project as completed

Task Workflow with Review

1. Task created in To Do with assignee, priority, deadline
2. Assignee moves task to In Progress and begins work
3. Work completed → assignee clicks "Request Review" and submits proof (links, files)
4. Task moves to Review column
5. Reviewer checks the submission: Approve (→ Complete) or Reject (→ In Progress with feedback)
6. If rejected, assignee revises and resubmits

• Create a KB page for project scope before creating tasks — it gives the team direction
• Assign every task to a specific person — unassigned tasks get overlooked
• Use the submission/review workflow for deliverables that need quality checks
• Build the KB as the project progresses, not at the end
• Mark projects as Completed rather than deleting them to preserve history
• Use descriptive file names on task attachments for clarity