organize workspace members into teams and add team-aware filters

Problem Statement

Workspace members currently cannot be organized into teams. As a workspace grows, flat member and assignee lists become difficult to scan, and users cannot quickly focus task views on a department, squad, or other working group.

Member-related filters also require selecting people individually, even when the intended scope is an entire team.

Proposed Solution

Allow workspace administrators to create teams within a workspace and assign workspace members to them.

Team management should support:

• Creating, renaming, and deleting a team.
• Adding and removing workspace members from a team.
• Viewing the members of each team.
• Showing a member's team affiliation in workspace member management.
• Preserving workspace membership when a team is deleted; deleting a team must not remove its members from the workspace.

Add a consistent hierarchical selector to member- and assignee-based filters across task views:

• All — include every workspace member.
• Team — include all members of the selected team.
• Member — narrow the selection to an individual member, optionally grouped under their team.

A compact interaction could be represented as:

All
├─ Design
│  ├─ Alice
│  └─ Bob
├─ Engineering
│  ├─ Carol
│  └─ David
└─ Members without a team
   └─ Eve

Suggested behavior:

• Selecting a team filters tasks assigned to any current member of that team.
• Selecting a member filters tasks assigned to that specific person.
• Members without a team remain available.
• Search remains available for workspaces with many teams or members.
• The same team/member selection pattern is used wherever an assignee or member filter appears.
• Team changes update relevant filters without requiring users to reload the page.
• Teams are an organizational grouping and do not implicitly grant roles or permissions.

Alternative Solutions

Users can select each member individually or encode team names in labels. Individual selection is repetitive and easy to get out of sync, while labels duplicate workspace membership data and mix task classification with team organization.

Separate workspaces could also represent teams, but that fragments projects and collaboration when several teams work in the same workspace.

Relevant Context

This feature should build on existing workspace membership and task assignment behavior. It does not need to replace roles or introduce team-specific authorization in its first version.

Suggested acceptance criteria:

• Workspace administrators can create, rename, and delete teams.
• Workspace members can be added to and removed from teams.
• Deleting a team does not remove or deactivate its workspace members.
• Member- and assignee-based task filters expose All, Team, and Member scopes.
• Selecting a team returns tasks assigned to any member of that team.
• Selecting a member returns tasks assigned to that member.
• Members without a team remain selectable.
• Team membership changes are reflected in filters and current views.
• Existing workspace role and permission behavior is unchanged.
• Empty, loading, and no-result states are clearly represented.

Does this feature align with Kaneo's focus on simplicity?

Yes. A lightweight team grouping removes repetitive member selection and keeps large workspaces navigable. Reusing one All → Team → Member pattern across filters avoids introducing different controls for the same concept.

---

Originally requested by @taiyoungjang on 2026-08-30. Original GitHub request #1680.