Projects Directory
Search, filter, group, sort, and act on the workspace project portfolio.
The Projects landing page is a server-backed directory designed for large workspaces. It loads one page at a time and keeps filters in the URL so views can be bookmarked and shared.
Directory views
| View | Purpose |
|---|---|
| All | Every non-deleted project allowed by the current filters |
| Mine | Projects owned by or relevant to you |
| Needs attention | Projects with missing setup, risk, or overdue work |
| At risk | Projects whose calculated health is at risk |
| Overdue | Projects with overdue work |
| Due soon | Projects approaching their due date |
| Recently completed | Recently finished projects |
The summary strip reports total, active, at-risk, off-track, overdue-task, due-soon, and missing-setup counts.
Filters and organization
You can filter by canonical project status, health, owner, team, or project group. Search accepts up to 120 characters.
Sort by:
- risk;
- recent activity;
- due date;
- name;
- progress.
Group rows by status, health, owner, team, or project group. Optional columns cover health, owner, status, schedule, progress, and activity.
Pagination
The directory supports page sizes of 25, 50, or 100. Filtering and sorting happen on the server so the browser does not need to download the full project portfolio.
URL state
Common parameters include:
?q=onboarding
?view=attention
?status=active
?health=at_risk
?owner=<user-id>
?sort=due_date&direction=asc
?groupBy=team
?page=2&pageSize=50Invalid parameters fall back to safe defaults instead of breaking the page.
Statuses
The directory uses the canonical project lifecycle:
draft → planned → active → on_hold → completed | cancelled | archived
Legacy aliases are normalized. See Project Lifecycle for the exact mapping.
Bulk actions
Select directory rows to access available bulk actions. Permissions and workspace scope are checked by the server; selecting a visible row does not grant additional access.