Project — Task Board | Development Standards

WeWeb + Supabase ~8 Hours Intermediate

What You Are Building

Build a workspace-based task board where users can create, assign, filter, update, and delete tasks according to their workspace role.

This project teaches

Multi-table schema
Supabase RPC functions
RLS policies
Task list UI in WeWeb
Filters and bulk actions
Add/edit modal
Delete confirmation

Flow Design

Example Flow

flowchart TD
    Login[User logs in]
    Workspace[Selects workspace]
    Board[Opens Task Board]

    Login --> Workspace --> Board

    Board --> Owner[Owner Flow]
    Board --> Admin[Admin Flow]
    Board --> Member[Member Flow]

    Owner --> OwnerOverview[View tasks across owned workspaces]
    OwnerOverview --> OwnerFilter[Search / filter / paginate]
    OwnerFilter --> OwnerView[Open task detail]
    OwnerView --> OwnerManage[Create, assign, edit, bulk update, delete]

    Admin --> AdminList[View workspace tasks]
    AdminList --> AdminFilter[Search / filter / paginate]
    AdminFilter --> AdminCreate[Create task]
    AdminCreate --> AdminAssign[Assign task to member]
    AdminAssign --> AdminReview[Review progress and status]
    AdminReview --> AdminBulk[Bulk update or delete selected tasks]
    AdminBulk -. cannot access other workspaces .-> AdminBlocked[Blocked by workspace permission rules]

    Member --> MemberList[View assigned or visible tasks]
    MemberList --> MemberFilter[Search / filter own visible tasks]
    MemberFilter --> MemberView[Open task detail]
    MemberView --> MemberUpdate[Update allowed fields or progress]
    MemberUpdate -. cannot delete or bulk manage tasks .-> MemberBlocked[Restricted actions hidden and denied]

Required Screens

Task Board Page

Should include:

Kanban or list view with clear status grouping.
Search by title and filters for assignee, priority, status, and due date.
Pagination or lazy loading if the task list grows.
Bulk-select checkboxes for admin actions.
Quick status update control from the board itself.
Badges for priority, due date, and overdue state.
Loading, empty, filtered-empty, and error states.

Add/Edit Task Modal

Fields:

Title, description, assignee, priority, status, due date, and workspace context.
Shared component for both add and edit mode.
Validation for required title, valid due date, and allowed assignee.
Clear submit loading state and cancel/close behavior.

Task Detail / View Panel

Should show:

Full task title and description.
Assignee, created by, created date, due date, priority, and status timeline.
Edit action for Owner/Admin and for the assigned member when only allowed task fields are being updated.
Delete action only for Admin/Owner.
Activity log or comments are out of scope for the base project unless the team intentionally extends it after the core board is complete.

Bulk Action Bar

Admin flow should include:

Visible selection count.
Change status action.
Change assignee action.
Change priority action.
Delete selected tasks with confirmation.
Permission-safe UI so members never see admin-only bulk actions.

Data Model

Recommended tables:

Table	Purpose
`workspaces`	Workspace/team.
`workspace_members`	Workspace roles.
`tasks`	Main task records.
`task_comments`	Optional task discussions.
`task_activity_logs`	Tracks task changes.

Recommended tasks fields:

Field	Purpose
`workspace_id`	Isolates task by workspace.
`title`	Task title.
`description`	Task details.
`assignee_id`	Assigned user.
`created_by`	Creator.
`status`	Task state.
`priority`	Low, medium, high, urgent.
`due_date`	Deadline.

Permission Rules

Actor	Allowed
Owner	Manage all tasks in owned workspaces.
Admin	Manage tasks in assigned workspace.
Member	View workspace tasks and update assigned tasks.
Non-member	No access.

RPC Examples

Use RPC functions for actions that require business rules, such as:

Bulk update task status.
Bulk assign tasks.
Move task between statuses.
Safely delete task with audit log.

Example business rule:

A task can move to Done only if it is currently in Review or if the actor is Admin/Owner.

Acceptance Checklist

Tasks are scoped by workspace.
Admin cannot see another workspace’s tasks.
Member can only update allowed task fields.
Add/edit modal validates required fields.
Delete confirmation prevents accidental deletion.
Bulk actions work only for authorized users.
Loading, empty, and error states are implemented.
RPC functions validate permissions server-side.