The Registry
The Projects page: every project you may see with its filters, starting one in the intake wizard, editing it, moving its status, archiving, restoring and deleting it, and reading its history.
By the end of this page you will have started a project from the registry, know every field it carries and what reads each one downstream, and know how a project is moved along its lifecycle, put away, brought back and, when it must be, deleted.
The registry is the Projects page in the sidebar: every project of your team you may see, with the status and health of each, who manages it and when it is due. It is the first page of every phase, because every component, environment, epic, story, test, release and incident lives under one of its rows.
Before you begin
| You want to | You need |
|---|---|
| Open the registry | To belong to the team. Every default role sees it; a guest sees only the projects they were invited to. |
| Create a project | project:create on your role, or to own the team. Admins and project managers have it by default. |
| Edit, move or archive one | project:update, through your role on that project or your team role. |
| Delete one | project:delete. |
| Name a client on the project | The client to exist already; add it on the Clients page first. |
Read the registry
The table lists one project per row:
| Column | What it shows |
|---|---|
| Key | The project's key, the prefix of every reference inside it. |
| Project | The name, with the tagline beneath it. Press the name to open the detail flyout. |
| Client | The client the project is done for, or Internal. |
| Status | The lifecycle status as a badge. |
| Health | On track, at risk, off track or not assessed. |
| Project Manager | The lead named on the project, or Unassigned. |
| Target Launch | The date agreed with the client, when there is one. |
| Updated | How long ago the record last changed. |
| Row menu | View Project, Edit Project, Archive Project or Restore Project, Activity, Delete Project. |
Sort by key, project, status, health, target launch or updated by pressing a column heading; press it again to flip the direction.
Above the table, narrow the list with the search box (words in the key, the name or the tagline), the status list, the client list, and the Archived switch, which shows archived projects instead of live ones. The filters travel in the page address, so a filtered list can be shared; Clear Filters on the empty state drops them all.
Start a project
- Press New Project. It opens the intake wizard on its first step, with nothing filled in.
- Type the Name, pick the Client (or leave Internal project for work the team does for
itself) and write the one-paragraph Description Heimdall drafts from. Leave the Key
empty and one is proposed from the name, or type your own; it is upper-cased as you type and
checked against every project the team ever had, archived and deleted ones included, because
references such as
CRM-142stay in people's hands after a project is gone. - Set how it runs, name the leads you know and the dates agreed, or leave them for later; the same fields as the editor are offered, and every one can change afterwards.
- Press Create Project.
The project appears in the registry at once, project.created goes out to every endpoint
subscribed to it, and the wizard walks on to the project's components, environments, stakeholders
and personas.
The key freezes
Until an artefact is numbered under the project, the key may still change from the editor. The moment the first story, requirement or test case takes a number, the key is locked: the editor shows it read-only and the API refuses a change, because every reference already carries it.
Open a project
Press a project's name, or View Project in its row menu, to open the detail flyout: the key and status at the top, then the client and health, how it runs, the four leads, the dates and budget, the description and the timestamps. From the flyout:
- Open Project leaves the registry for the project itself: the overview, with the sidebar switched to the project's menu. The row menu offers the same entry.
- Move to changes the lifecycle status in one step. Every status but Archived is offered; archiving has its own button so the status it leaves is remembered.
- Edit opens the editor on this project.
- Archive puts the project away, or Restore brings an archived one back.
- Activity opens the project's history: every change, who made it and where it came from.
- Delete opens the confirmation.
A link such as /projects?show=<id> opens the registry with that project's flyout already open;
Heimdall's View buttons and the notifications use it.
Edit a project
- Press Edit Project in the row menu, or Edit in the flyout.
- Change what you need. The same rules as creating apply: the name stays unique, the key may only change while it is not yet locked, the client must be the team's and each lead a member.
- Press Save Changes.
A status changed inside the editor is announced as project.status_changed; every other change
travels as project.updated with its old and new values. An edit that changes nothing announces
nothing.
Archive, restore and delete
- Archive Project sets the status to Archived, remembers the status it left, and takes the project out of the registry's default view. Everything under it is kept and stays readable. Switch on Archived above the table to find it.
- Restore Project brings it back with the status it had before.
- Delete Project removes the project with everything under it: components, environments, people, the planning record, work, tests, releases, incidents and tickets. The confirmation asks you to type the project's key, and the key becomes free to reuse afterwards. Archiving is the reversible alternative; prefer it.
All the fields
What happens next
- Every create, edit, status move, archive, restore and delete is written to the project's activity history with who did it and where from, Heimdall included.
- The
project.created,project.updated,project.status_changed,project.archived,project.restoredandproject.deletedevents go out to every endpoint subscribed to them. - A project's client appears on that client's record, and a client that has projects can no longer be deleted.
Heimdall on this page
Heimdall reads the registry through the same tools the MCP server offers, and its answers carry a View button that opens the project's flyout.
Creating and shaping projects is a person's work: Heimdall and an agent over MCP read the registry and never write to it.
From the API and MCP
Projects API
List, get, create, change, archive, restore and delete projects over REST.
list_projects and get_project
The two MCP tools that read the registry as the token sees it.
Permissions
| Action | Permission |
|---|---|
| See the registry | project:view-any |
| Open a project | project:view |
| Create a project | project:create, or owning the team |
| Edit, move, archive or restore | project:update, through a project role or a team role |
| Delete a project | project:delete |
Frequently asked
Related
- The project overview — the project's home once it is open
- Clients — the organisations projects are done for
- Status reference — every status and what moves a record into it
- Activity log — where every change is recorded
How is this guide?
Last updated on
Projects
What a project is in Zuse Bifrost, the key that prefixes every reference in it, its lifecycle statuses and health, the client it is done for, and the pages that manage them.
The Intake Wizard
Start a project from a client, a name and a paragraph, then add components, environments, stakeholders and personas step by step, resuming any time.