Project Detail Page
The project detail page (/workspaces/:workspaceId/projects/:projectId) is where you see and manage a single project. It surfaces project metadata, tags, members, related activity, and lifecycle actions.
If you don't have project:read for the project, the page renders an Access Denied message. If the project doesn't exist (or was deleted), a Project not found card is shown with a button back to the projects list.
Header
The header carries:
- A Back to Projects link to
/workspaces/:workspaceId/projects. - The project name and project key (e.g.
ENG,MKTG) in monospace. - Status badges:
- Status badge (
ACTIVE,INACTIVE,ARCHIVED) coloured by status. - An Archived badge if the project's
archivedflag is set, regardless of status. - An actions menu (vertical-dots icon) with:
- Archive / Unarchive — toggles based on current state. Requires
project:archive. - Delete Project — opens a confirmation dialog. Requires
project:delete.
The actions menu only includes the entries you are allowed to perform. If you can do neither, the trigger still renders but the dropdown is empty — a small UX rough edge tracked as a follow-up.
Known issues
- The actions menu trigger renders even when the dropdown would be empty. Tracked as a microfrontend cleanup; the docs describe the current shipped behavior.
Stat cards
Two summary cards near the top:
- Members — count of users who are members of this project (from
projectMembersCount). - Activity — count of activity items related to this project, derived from the workspace activity feed by matching either the resource ID or
Projectresource type.
Tags
The Tags card uses the universal-tags widget to attach tags to the project.
- Click + to add a tag.
- Click x to remove a tag.
Adding or removing a tag immediately calls updateProject with the new tag list. While the call is in flight the widget is briefly disabled and dimmed. If the update fails, the previous tag list is restored.
Tags applied here also affect filtering on the projects list: clicking a tag badge on a project card adds it to the active filter set.
Permissions: project:update.
Project Information
A read-only grid of:
- Project ID (monospace)
- Project Key
- Created — formatted date
- Last Updated — formatted date
- Workspace ID (monospace)
- Creator ID (monospace)
If the project has a non-empty config JSON object, it is rendered below in a collapsible Configuration code block — useful for product-specific settings that this project carries.
Quick actions
The Quick Actions card has two shortcuts:
- Workspace Members — jumps to
/workspaces/:workspaceId/members. - Workspace Activity — jumps to
/workspaces/:workspaceId/activity.
These are workspace-scoped (not project-scoped), so they let you cross-reference the wider workspace context without losing your place.
Deleting a project
Choose Delete Project from the actions menu. A confirmation dialog asks you to confirm:
Are you sure you want to delete
<name>? This action cannot be undone and all project data will be permanently removed.
Click Delete Project to confirm. On success the page returns you to the projects list. The mutation is deleteProject; the deletion is a soft-delete on the backend, but the UI treats it as permanent.
Permissions: project:delete.
Permissions summary
| Action | Permission |
|---|---|
| Open the page | project:read |
| Add/remove tags | project:update |
| Archive or unarchive | project:archive |
| Delete | project:delete |
| See related activity card | activity:read (on the workspace) |
| See member count | project-member:list (resolver enforces) |
Buttons and menu items are hidden when you don't have the matching permission, so the page never offers an action you can't complete.