Implement multiple boards/projects per organization

[luizhcastro]

Description

Implement functionality that allows an organization to have multiple boards/projects instead of being limited to a single board. This will enable organizations to manage different teams, products, or workstreams independently.

Motivation

• Support organizations with multiple teams or products
• Enable better separation of concerns between different workstreams
• Allow teams to work independently within the same organization
• Scale the platform to support larger organizations with diverse needs
• Provide flexibility in organizing work without creating separate organizations

Scope

Core Functionality

• Organization can have multiple boards/projects
• Each board has its own settings and configuration
• Each board can have different members/permissions
• Users can be members of multiple boards within an org
• Board creation and deletion (with proper permissions)
• Board naming and description
• Board archiving (soft delete)

Navigation & Discovery

• Board selector/switcher in navigation
• List view of all boards in an organization
• Search functionality for boards
• Recently accessed boards quick access
• Board favorites/pinning
• Board categories/grouping (optional)

Permissions & Access Control

• Organization-level roles (owner, admin, member)
• Board-level roles (admin, member, viewer)
• Permission inheritance from organization
• Private vs public boards within organization
• Invite users to specific boards
• Board access request workflow

Data & Settings

• Board-specific settings (labels, statuses, workflows)
• Board-specific templates
• Board analytics and insights
• Board activity feed
• Board default settings inherited from org
• Cross-board task references (optional)

Backend Requirements

• Database schema updates (organization-board relationship)
• Board context in all task-related queries
• API endpoints for board CRUD operations
• Board membership management APIs
• Permission checks for all board operations
• Migration strategy for existing single-board orgs

Acceptance Criteria

• Organizations can create multiple boards
• Each board operates independently with its own data
• Board switching is seamless and intuitive
• Permissions are properly enforced at board level
• Users can see only boards they have access to
• Board creation is restricted by organization permissions
• Existing data from single-board setup is preserved during migration
• Board URLs are clean and bookmarkable

Technical Considerations

• Consider URL structure: /org/{org-id}/board/{board-id}
• Plan for board limits per organization (if any)
• Consider board templates for quick setup
• Think about cross-board reporting and analytics
• Plan data isolation strategy between boards
• Consider board cloning/duplication functionality
• Think about board export/import for migration