# Zuse Bifrost Documentation

> Machine-readable index of the Zuse Bifrost documentation site.
> Base URL: https://alm-docs.labs.zuselab.dev

## (root)

- [Welcome](https://alm-docs.labs.zuselab.dev) — How to plan, build, test, release and maintain a project in Zuse Bifrost, and how to reach it over the API, webhooks and MCP.

## account

- [Appearance](https://alm-docs.labs.zuselab.dev/account/appearance) — Pick light mode, dark mode or your device's own setting for the application, on the device you are using.
- [Your Account](https://alm-docs.labs.zuselab.dev/account) — Everything about the account you sign in with: how it is created, how you sign in, what protects it, and the preferences that follow you.
- [Accepting an Invitation](https://alm-docs.labs.zuselab.dev/account/invitations) — What happens when you follow an invitation link, whether you are new, already have an account, or are signed in as someone else, and why the link is signed.
- [Notifications](https://alm-docs.labs.zuselab.dev/account/notifications) — Read every alert in the Notifications Center, mark it read or open it, and choose which classes of alert reach your email and your linked chat.
- [Passkeys](https://alm-docs.labs.zuselab.dev/account/passkeys) — Register passkeys to sign in with a fingerprint, a face scan or your device lock, keep one per device, and remove the ones you no longer hold.
- [Changing Your Password](https://alm-docs.labs.zuselab.dev/account/password) — Set a new password from Account Settings → Security, what the form asks for, what happens to your other sessions, and how an account that signs in with a passkey alone sets one.
- [Profile](https://alm-docs.labs.zuselab.dev/account/profile) — Keep the name, email address and job title on your account accurate, and verify a new address after you change it.
- [Browser Sessions](https://alm-docs.labs.zuselab.dev/account/sessions) — See every browser signed in to your account and sign the others out when a device is lost, shared or unfamiliar.
- [Signing In](https://alm-docs.labs.zuselab.dev/account/sign-in) — Sign in with your email and password or with a passkey, answer the two-factor challenge, stay signed in, and recover when a password or link no longer works.
- [Timezone and Language](https://alm-docs.labs.zuselab.dev/account/timezone-and-locale) — Choose the timezone every date and time in the application is read and shown in, understand how it was detected, and pick the interface language.
- [Two-Factor Authentication](https://alm-docs.labs.zuselab.dev/account/two-factor-auth) — Add a six-digit code from an authenticator app to your password sign-in, save your recovery codes, and recover when you lose the device.

## api

- [Ability Catalogue](https://alm-docs.labs.zuselab.dev/api/v1/abilities) — Every ability string a token can carry, how the catalogue mirrors the team permissions, what enforces it on the API today, and how to pick the right ones when minting.
- [Agent Readiness](https://alm-docs.labs.zuselab.dev/api/v1/agent-readiness) — The documents an agent reads to find Zuse Bifrost on its own: the API catalog, the MCP server card, the agent skills, the OAuth metadata, AGENTS.md and llms.txt, each built from the running application.
- [Authentication](https://alm-docs.labs.zuselab.dev/api/v1/authentication) — Personal access tokens, ability scopes and tenant resolution for the REST API and the MCP server, and what the API will not accept.
- [Error Codes](https://alm-docs.labs.zuselab.dev/api/v1/errors) — The complete catalogue of error codes from the REST API and the MCP server, their HTTP statuses and what to do about each.
- [Idempotency](https://alm-docs.labs.zuselab.dev/api/v1/idempotency) — Every POST, PATCH, PUT and DELETE takes an Idempotency-Key header so a retry never double-creates or double-mutates.
- [REST API](https://alm-docs.labs.zuselab.dev/api/v1) — Read and write the project record from your own code, under the same permissions a person has.
- [OpenAPI Specification](https://alm-docs.labs.zuselab.dev/api/v1/openapi) — Where the machine-readable OpenAPI document lives, what it carries beyond paths, and how to load it into your tooling.
- [Pagination](https://alm-docs.labs.zuselab.dev/api/v1/pagination) — How list endpoints wrap data in a meta and links envelope, the 100-row page cap, and how to iterate a large result set.
- [REST API Quickstart](https://alm-docs.labs.zuselab.dev/api/v1/quickstart) — Mint a personal access token, call your first endpoint and receive your first signed webhook, end to end in under five minutes.
- [Rate Limiting](https://alm-docs.labs.zuselab.dev/api/v1/rate-limiting) — The named rate-limit buckets applied per token to the REST API and the webhook test endpoint, and the headers that report them.
- [Activity API](https://alm-docs.labs.zuselab.dev/api/v1/reference/activity) — Every mutation Zuse Bifrost performs, whether from the app, the REST API, an MCP tool call, an accepted Heimdall draft or a scheduled system task, is recorded against its subject in the activity log.
- [Read a subject's activity](https://alm-docs.labs.zuselab.dev/api/v1/reference/activity/read-a-subjects-activity) — /v1/activity in the Activity API.
- [Alert Destinations API](https://alm-docs.labs.zuselab.dev/api/v1/reference/alert-destinations) — An alert destination is a place your alerts go: your email address or the Telegram chat linked to your account.
- [List your alert destinations](https://alm-docs.labs.zuselab.dev/api/v1/reference/alert-destinations/list-your-alert-destinations) — /v1/me/alert-destinations in the Alert Destinations API.
- [Replace your alert destinations](https://alm-docs.labs.zuselab.dev/api/v1/reference/alert-destinations/replace-your-alert-destinations) — /v1/me/alert-destinations in the Alert Destinations API.
- [Decide an approval](https://alm-docs.labs.zuselab.dev/api/v1/reference/approvals/decide-an-approval) — /v1/approvals/{approval}/decide in the Approvals API.
- [Get an approval request](https://alm-docs.labs.zuselab.dev/api/v1/reference/approvals/get-an-approval-request) — /v1/approvals/{approval} in the Approvals API.
- [Approvals API](https://alm-docs.labs.zuselab.dev/api/v1/reference/approvals) — An approval request is one time a planning record was put up for approval: an epic, a story, a requirement, a business rule or a use case, a baseline or a change request, submitted by its author and decided by the approvers the project's policy names for that kind of approval.
- [List a project's approval policies](https://alm-docs.labs.zuselab.dev/api/v1/reference/approvals/list-a-projects-approval-policies) — /v1/projects/{project}/approval-policies in the Approvals API.
- [List a project's approvals](https://alm-docs.labs.zuselab.dev/api/v1/reference/approvals/list-a-projects-approvals) — /v1/projects/{project}/approvals in the Approvals API.
- [List the inbox](https://alm-docs.labs.zuselab.dev/api/v1/reference/approvals/list-the-inbox) — /v1/approvals in the Approvals API.
- [Submit a baseline](https://alm-docs.labs.zuselab.dev/api/v1/reference/approvals/submit-a-baseline) — /v1/baselines/{baseline}/submit in the Approvals API.
- [Submit a business rule](https://alm-docs.labs.zuselab.dev/api/v1/reference/approvals/submit-a-business-rule) — /v1/business-rules/{rule}/submit in the Approvals API.
- [Submit a change request](https://alm-docs.labs.zuselab.dev/api/v1/reference/approvals/submit-a-change-request) — /v1/change-requests/{changeRequest}/submit in the Approvals API.
- [Submit a requirement](https://alm-docs.labs.zuselab.dev/api/v1/reference/approvals/submit-a-requirement) — /v1/requirements/{requirement}/submit in the Approvals API.
- [Submit a story](https://alm-docs.labs.zuselab.dev/api/v1/reference/approvals/submit-a-story) — /v1/work-items/{item}/submit in the Approvals API.
- [Submit a use case](https://alm-docs.labs.zuselab.dev/api/v1/reference/approvals/submit-a-use-case) — /v1/use-cases/{useCase}/submit in the Approvals API.
- [Submit an epic](https://alm-docs.labs.zuselab.dev/api/v1/reference/approvals/submit-an-epic) — /v1/epics/{epic}/submit in the Approvals API.
- [Update a project's approval policy](https://alm-docs.labs.zuselab.dev/api/v1/reference/approvals/update-a-projects-approval-policy) — /v1/projects/{project}/approval-policies in the Approvals API.
- [Withdraw an approval](https://alm-docs.labs.zuselab.dev/api/v1/reference/approvals/withdraw-an-approval) — /v1/approvals/{approval}/withdraw in the Approvals API.
- [Delete an attachment](https://alm-docs.labs.zuselab.dev/api/v1/reference/attachments/delete-an-attachment) — /v1/attachments/{attachment} in the Attachments API.
- [Download an attachment](https://alm-docs.labs.zuselab.dev/api/v1/reference/attachments/download-an-attachment) — /v1/attachments/{attachment}/download in the Attachments API.
- [Attachments API](https://alm-docs.labs.zuselab.dev/api/v1/reference/attachments) — An attachment is a file pinned on one artefact of a project: a wireframe on a story, a signed specification on a requirement, a sample export on a data entity, a vendor quote on a decision.
- [List an artefact's attachments](https://alm-docs.labs.zuselab.dev/api/v1/reference/attachments/list-an-artefacts-attachments) — /v1/projects/{project}/attachments in the Attachments API.
- [Upload an attachment](https://alm-docs.labs.zuselab.dev/api/v1/reference/attachments/upload-an-attachment) — /v1/projects/{project}/attachments in the Attachments API.
- [Add a baseline](https://alm-docs.labs.zuselab.dev/api/v1/reference/baselines/add-a-baseline) — /v1/projects/{project}/baselines in the Baselines API.
- [Delete a baseline](https://alm-docs.labs.zuselab.dev/api/v1/reference/baselines/delete-a-baseline) — /v1/baselines/{baseline} in the Baselines API.
- [Get a baseline](https://alm-docs.labs.zuselab.dev/api/v1/reference/baselines/get-a-baseline) — /v1/baselines/{baseline} in the Baselines API.
- [Get a version of a baseline](https://alm-docs.labs.zuselab.dev/api/v1/reference/baselines/get-a-version-of-a-baseline) — /v1/baselines/{baseline}/revisions/{revision} in the Baselines API.
- [Baselines API](https://alm-docs.labs.zuselab.dev/api/v1/reference/baselines) — A baseline is a named set of approved records frozen together: the scope the client signs before the build starts, what a release ships, what a sprint commits to, or the record as it stood at a milestone.
- [List a baseline's versions](https://alm-docs.labs.zuselab.dev/api/v1/reference/baselines/list-a-baselines-versions) — /v1/baselines/{baseline}/revisions in the Baselines API.
- [List baselines](https://alm-docs.labs.zuselab.dev/api/v1/reference/baselines/list-baselines) — /v1/projects/{project}/baselines in the Baselines API.
- [Move a baseline](https://alm-docs.labs.zuselab.dev/api/v1/reference/baselines/move-a-baseline) — /v1/baselines/{baseline}/status in the Baselines API.
- [Restore a version of a baseline](https://alm-docs.labs.zuselab.dev/api/v1/reference/baselines/restore-a-version-of-a-baseline) — /v1/baselines/{baseline}/revisions/{revision}/restore in the Baselines API.
- [Set a baseline's items](https://alm-docs.labs.zuselab.dev/api/v1/reference/baselines/set-a-baselines-items) — /v1/baselines/{baseline}/items in the Baselines API.
- [Update a baseline](https://alm-docs.labs.zuselab.dev/api/v1/reference/baselines/update-a-baseline) — /v1/baselines/{baseline} in the Baselines API.
- [Add a business rule](https://alm-docs.labs.zuselab.dev/api/v1/reference/business-rules/add-a-business-rule) — /v1/projects/{project}/business-rules in the Business Rules API.
- [Delete a business rule](https://alm-docs.labs.zuselab.dev/api/v1/reference/business-rules/delete-a-business-rule) — /v1/business-rules/{rule} in the Business Rules API.
- [Get a business rule](https://alm-docs.labs.zuselab.dev/api/v1/reference/business-rules/get-a-business-rule) — /v1/business-rules/{rule} in the Business Rules API.
- [Get a version of a business rule](https://alm-docs.labs.zuselab.dev/api/v1/reference/business-rules/get-a-version-of-a-business-rule) — /v1/business-rules/{rule}/revisions/{revision} in the Business Rules API.
- [Business Rules API](https://alm-docs.labs.zuselab.dev/api/v1/reference/business-rules) — A business rule is a decision of the business the system must honour: a limit it refuses to cross, a fact derived from others, a number worked out from others, a conclusion drawn when conditions hold, an action it takes when they do, or a standing policy.
- [List a business rule's quality reviews](https://alm-docs.labs.zuselab.dev/api/v1/reference/business-rules/list-a-business-rules-quality-reviews) — /v1/business-rules/{rule}/quality-reviews in the Business Rules API.
- [List a business rule's versions](https://alm-docs.labs.zuselab.dev/api/v1/reference/business-rules/list-a-business-rules-versions) — /v1/business-rules/{rule}/revisions in the Business Rules API.
- [List business rules](https://alm-docs.labs.zuselab.dev/api/v1/reference/business-rules/list-business-rules) — /v1/projects/{project}/business-rules in the Business Rules API.
- [Move a business rule](https://alm-docs.labs.zuselab.dev/api/v1/reference/business-rules/move-a-business-rule) — /v1/business-rules/{rule}/status in the Business Rules API.
- [Restore a version of a business rule](https://alm-docs.labs.zuselab.dev/api/v1/reference/business-rules/restore-a-version-of-a-business-rule) — /v1/business-rules/{rule}/revisions/{revision}/restore in the
- [Review a business rule's quality](https://alm-docs.labs.zuselab.dev/api/v1/reference/business-rules/review-a-business-rules-quality) — /v1/business-rules/{rule}/quality-reviews in the Business Rules API.
- [Update a business rule](https://alm-docs.labs.zuselab.dev/api/v1/reference/business-rules/update-a-business-rule) — /v1/business-rules/{rule} in the Business Rules API.
- [Analyse a change request's impact](https://alm-docs.labs.zuselab.dev/api/v1/reference/change-requests/analyse-a-change-requests-impact) — /v1/change-requests/{changeRequest}/analyse in the Change Requests API.
- [Delete a change request](https://alm-docs.labs.zuselab.dev/api/v1/reference/change-requests/delete-a-change-request) — /v1/change-requests/{changeRequest} in the Change Requests API.
- [Get a change request](https://alm-docs.labs.zuselab.dev/api/v1/reference/change-requests/get-a-change-request) — /v1/change-requests/{changeRequest} in the Change Requests API.
- [Get a version of a change request](https://alm-docs.labs.zuselab.dev/api/v1/reference/change-requests/get-a-version-of-a-change-request) — /v1/change-requests/{changeRequest}/revisions/{revision} in the
- [Change Requests API](https://alm-docs.labs.zuselab.dev/api/v1/reference/change-requests) — A change request is a change asked for after the record was agreed: a new requirement, a clarification, a defect in the baseline, a regulatory demand, a client's wish, a piece of technical debt or a scope reduction.
- [List a change request's versions](https://alm-docs.labs.zuselab.dev/api/v1/reference/change-requests/list-a-change-requests-versions) — /v1/change-requests/{changeRequest}/revisions in the Change Requests API.
- [List change requests](https://alm-docs.labs.zuselab.dev/api/v1/reference/change-requests/list-change-requests) — /v1/projects/{project}/change-requests in the Change Requests API.
- [Move a change request](https://alm-docs.labs.zuselab.dev/api/v1/reference/change-requests/move-a-change-request) — /v1/change-requests/{changeRequest}/status in the Change Requests API.
- [Raise a change request](https://alm-docs.labs.zuselab.dev/api/v1/reference/change-requests/raise-a-change-request) — /v1/projects/{project}/change-requests in the Change Requests API.
- [Restore a version of a change request](https://alm-docs.labs.zuselab.dev/api/v1/reference/change-requests/restore-a-version-of-a-change-request) — /v1/change-requests/{changeRequest}/revisions/{revision}/restore in
- [Update a change request](https://alm-docs.labs.zuselab.dev/api/v1/reference/change-requests/update-a-change-request) — /v1/change-requests/{changeRequest} in the Change Requests API.
- [Verify a change request](https://alm-docs.labs.zuselab.dev/api/v1/reference/change-requests/verify-a-change-request) — /v1/change-requests/{changeRequest}/verify in the Change Requests API.
- [Archive a client](https://alm-docs.labs.zuselab.dev/api/v1/reference/clients/archive-a-client) — /v1/clients/{client}/archive in the Clients API.
- [Create a client](https://alm-docs.labs.zuselab.dev/api/v1/reference/clients/create-a-client) — /v1/clients in the Clients API.
- [Delete a client](https://alm-docs.labs.zuselab.dev/api/v1/reference/clients/delete-a-client) — /v1/clients/{client} in the Clients API.
- [Get a client](https://alm-docs.labs.zuselab.dev/api/v1/reference/clients/get-a-client) — /v1/clients/{client} in the Clients API.
- [Clients API](https://alm-docs.labs.zuselab.dev/api/v1/reference/clients) — A client is an organisation the team does projects for: its names, its primary contact, where it works from and where the relationship stands.
- [List clients](https://alm-docs.labs.zuselab.dev/api/v1/reference/clients/list-clients) — /v1/clients in the Clients API.
- [Restore a client](https://alm-docs.labs.zuselab.dev/api/v1/reference/clients/restore-a-client) — /v1/clients/{client}/restore in the Clients API.
- [Update a client](https://alm-docs.labs.zuselab.dev/api/v1/reference/clients/update-a-client) — /v1/clients/{client} in the Clients API.
- [Delete a comment](https://alm-docs.labs.zuselab.dev/api/v1/reference/comments/delete-a-comment) — /v1/comments/{comment} in the Comments API.
- [Edit a comment](https://alm-docs.labs.zuselab.dev/api/v1/reference/comments/edit-a-comment) — /v1/comments/{comment} in the Comments API.
- [Comments API](https://alm-docs.labs.zuselab.dev/api/v1/reference/comments) — A comment is a note on one artefact of a project: a question on a requirement, an answer under it, a finding on a story, a decision taken in the margin of a RAID item.
- [List an artefact's comments](https://alm-docs.labs.zuselab.dev/api/v1/reference/comments/list-an-artefacts-comments) — /v1/projects/{project}/comments in the Comments API.
- [Post a comment](https://alm-docs.labs.zuselab.dev/api/v1/reference/comments/post-a-comment) — /v1/projects/{project}/comments in the Comments API.
- [Reopen a thread](https://alm-docs.labs.zuselab.dev/api/v1/reference/comments/reopen-a-thread) — /v1/comments/{comment}/reopen in the Comments API.
- [Resolve a thread](https://alm-docs.labs.zuselab.dev/api/v1/reference/comments/resolve-a-thread) — /v1/comments/{comment}/resolve in the Comments API.
- [Archive a component](https://alm-docs.labs.zuselab.dev/api/v1/reference/components/archive-a-component) — /v1/components/{component}/archive in the Components API.
- [Create a component](https://alm-docs.labs.zuselab.dev/api/v1/reference/components/create-a-component) — /v1/projects/{project}/components in the Components API.
- [Delete a component](https://alm-docs.labs.zuselab.dev/api/v1/reference/components/delete-a-component) — /v1/components/{component} in the Components API.
- [Get a component](https://alm-docs.labs.zuselab.dev/api/v1/reference/components/get-a-component) — /v1/components/{component} in the Components API.
- [Components API](https://alm-docs.labs.zuselab.dev/api/v1/reference/components) — A component is one application a project is made of: the web app, the API, a mobile app, a background service, an integration, a database or the platform itself.
- [List components](https://alm-docs.labs.zuselab.dev/api/v1/reference/components/list-components) — /v1/projects/{project}/components in the Components API.
- [Restore a component](https://alm-docs.labs.zuselab.dev/api/v1/reference/components/restore-a-component) — /v1/components/{component}/restore in the Components API.
- [Update a component](https://alm-docs.labs.zuselab.dev/api/v1/reference/components/update-a-component) — /v1/components/{component} in the Components API.
- [Accept a council finding](https://alm-docs.labs.zuselab.dev/api/v1/reference/council/accept-a-council-finding) — /v1/council-findings/{finding}/accept in the Council API.
- [Convene the council](https://alm-docs.labs.zuselab.dev/api/v1/reference/council/convene-the-council) — /v1/projects/{project}/council in the Council API.
- [Dismiss a council finding](https://alm-docs.labs.zuselab.dev/api/v1/reference/council/dismiss-a-council-finding) — /v1/council-findings/{finding}/dismiss in the Council API.
- [Council API](https://alm-docs.labs.zuselab.dev/api/v1/reference/council) — The council is Heimdall with named voices beside it: Odin for architecture and the data model, Thor for testing, Loki for security, Týr for rigour and compliance, Frigg for planning and risk, Baldur for the people who will use the product and Hel for what fails in production.
- [List a project's council sessions](https://alm-docs.labs.zuselab.dev/api/v1/reference/council/list-a-projects-council-sessions) — /v1/projects/{project}/council in the Council API.
- [Retrieve a council session](https://alm-docs.labs.zuselab.dev/api/v1/reference/council/retrieve-a-council-session) — /v1/council/{session} in the Council API.
- [Create a data entity](https://alm-docs.labs.zuselab.dev/api/v1/reference/data-entities/create-a-data-entity) — /v1/projects/{project}/data-entities in the Data Entities API.
- [Delete a data entity](https://alm-docs.labs.zuselab.dev/api/v1/reference/data-entities/delete-a-data-entity) — /v1/data-entities/{entity} in the Data Entities API.
- [Get a data entity](https://alm-docs.labs.zuselab.dev/api/v1/reference/data-entities/get-a-data-entity) — /v1/data-entities/{entity} in the Data Entities API.
- [Data Entities API](https://alm-docs.labs.zuselab.dev/api/v1/reference/data-entities) — A data entity is a thing the project keeps records of: a customer, an order, a branch, a shipment.
- [List a entity's versions](https://alm-docs.labs.zuselab.dev/api/v1/reference/data-entities/list-a-entitys-versions) — /v1/data-entities/{entity}/revisions in the Data Entities API.
- [List data entities](https://alm-docs.labs.zuselab.dev/api/v1/reference/data-entities/list-data-entities) — /v1/projects/{project}/data-entities in the Data Entities API.
- [Move a data entity](https://alm-docs.labs.zuselab.dev/api/v1/reference/data-entities/move-a-data-entity) — /v1/data-entities/{entity}/status in the Data Entities API.
- [Read one version of a entity](https://alm-docs.labs.zuselab.dev/api/v1/reference/data-entities/read-one-version-of-a-entity) — /v1/data-entities/{entity}/revisions/{revision} in the Data Entities API.
- [Replace a data entity's fields](https://alm-docs.labs.zuselab.dev/api/v1/reference/data-entities/replace-a-data-entitys-fields) — /v1/data-entities/{entity}/fields in the Data Entities API.
- [Restore a version of a entity](https://alm-docs.labs.zuselab.dev/api/v1/reference/data-entities/restore-a-version-of-a-entity) — /v1/data-entities/{entity}/revisions/{revision}/restore in the Data
- [Update a data entity](https://alm-docs.labs.zuselab.dev/api/v1/reference/data-entities/update-a-data-entity) — /v1/data-entities/{entity} in the Data Entities API.
- [Add a decision](https://alm-docs.labs.zuselab.dev/api/v1/reference/decisions/add-a-decision) — /v1/projects/{project}/decisions in the Decisions API.
- [Delete a decision](https://alm-docs.labs.zuselab.dev/api/v1/reference/decisions/delete-a-decision) — /v1/decisions/{decision} in the Decisions API.
- [Get a decision](https://alm-docs.labs.zuselab.dev/api/v1/reference/decisions/get-a-decision) — /v1/decisions/{decision} in the Decisions API.
- [Get a version of a decision](https://alm-docs.labs.zuselab.dev/api/v1/reference/decisions/get-a-version-of-a-decision) — /v1/decisions/{decision}/revisions/{revision} in the Decisions API.
- [Decisions API](https://alm-docs.labs.zuselab.dev/api/v1/reference/decisions) — A decision is the record of a choice the project made: the context it was taken in, the options weighed with their pros and cons, what was decided, what follows, who decided and when, and the earlier decision it replaces.
- [List a decision's versions](https://alm-docs.labs.zuselab.dev/api/v1/reference/decisions/list-a-decisions-versions) — /v1/decisions/{decision}/revisions in the Decisions API.
- [List decisions](https://alm-docs.labs.zuselab.dev/api/v1/reference/decisions/list-decisions) — /v1/projects/{project}/decisions in the Decisions API.
- [Move a decision](https://alm-docs.labs.zuselab.dev/api/v1/reference/decisions/move-a-decision) — /v1/decisions/{decision}/status in the Decisions API.
- [Restore a version of a decision](https://alm-docs.labs.zuselab.dev/api/v1/reference/decisions/restore-a-version-of-a-decision) — /v1/decisions/{decision}/revisions/{revision}/restore in the Decisions API.
- [Update a decision](https://alm-docs.labs.zuselab.dev/api/v1/reference/decisions/update-a-decision) — /v1/decisions/{decision} in the Decisions API.
- [Add a design reference](https://alm-docs.labs.zuselab.dev/api/v1/reference/design-references/add-a-design-reference) — /v1/projects/{project}/design-references in the Design References API.
- [Delete a design reference](https://alm-docs.labs.zuselab.dev/api/v1/reference/design-references/delete-a-design-reference) — /v1/design-references/{reference} in the Design References API.
- [Get a design reference](https://alm-docs.labs.zuselab.dev/api/v1/reference/design-references/get-a-design-reference) — /v1/design-references/{reference} in the Design References API.
- [Design References API](https://alm-docs.labs.zuselab.dev/api/v1/reference/design-references) — A design reference is a link a project keeps to one of its designs: a Figma file, a wireframe, a prototype, a screenshot, an API contract, a sequence diagram, an entity diagram or a document.
- [List design references](https://alm-docs.labs.zuselab.dev/api/v1/reference/design-references/list-design-references) — /v1/projects/{project}/design-references in the Design References API.
- [Update a design reference](https://alm-docs.labs.zuselab.dev/api/v1/reference/design-references/update-a-design-reference) — /v1/design-references/{reference} in the Design References API.
- [Create an environment](https://alm-docs.labs.zuselab.dev/api/v1/reference/environments/create-an-environment) — /v1/projects/{project}/environments in the Environments API.
- [Delete an environment](https://alm-docs.labs.zuselab.dev/api/v1/reference/environments/delete-an-environment) — /v1/environments/{environment} in the Environments API.
- [Freeze an environment](https://alm-docs.labs.zuselab.dev/api/v1/reference/environments/freeze-an-environment) — /v1/environments/{environment}/freeze in the Environments API.
- [Get an environment](https://alm-docs.labs.zuselab.dev/api/v1/reference/environments/get-an-environment) — /v1/environments/{environment} in the Environments API.
- [Environments API](https://alm-docs.labs.zuselab.dev/api/v1/reference/environments) — An environment is one named place a project's software runs, from a developer's machine to production: its kind, the component it runs (or the whole project), its addresses, the branch deployed there, the autodeploy and protected flags, the health the last check found, the version running there and whether a change freeze is in force.
- [List environments](https://alm-docs.labs.zuselab.dev/api/v1/reference/environments/list-environments) — /v1/projects/{project}/environments in the Environments API.
- [Record an environment's health](https://alm-docs.labs.zuselab.dev/api/v1/reference/environments/record-an-environments-health) — /v1/environments/{environment}/health in the Environments API.
- [Unfreeze an environment](https://alm-docs.labs.zuselab.dev/api/v1/reference/environments/unfreeze-an-environment) — /v1/environments/{environment}/unfreeze in the Environments API.
- [Update an environment](https://alm-docs.labs.zuselab.dev/api/v1/reference/environments/update-an-environment) — /v1/environments/{environment} in the Environments API.
- [Add an epic](https://alm-docs.labs.zuselab.dev/api/v1/reference/epics/add-an-epic) — /v1/projects/{project}/epics in the Epics API.
- [Delete an epic](https://alm-docs.labs.zuselab.dev/api/v1/reference/epics/delete-an-epic) — /v1/epics/{epic} in the Epics API.
- [Get a version of an epic](https://alm-docs.labs.zuselab.dev/api/v1/reference/epics/get-a-version-of-an-epic) — /v1/epics/{epic}/revisions/{revision} in the Epics API.
- [Get an epic](https://alm-docs.labs.zuselab.dev/api/v1/reference/epics/get-an-epic) — /v1/epics/{epic} in the Epics API.
- [Epics API](https://alm-docs.labs.zuselab.dev/api/v1/reference/epics) — An epic is a body of work the client recognises: the scope a release is cut from and the parent of every story.
- [List an epic's versions](https://alm-docs.labs.zuselab.dev/api/v1/reference/epics/list-an-epics-versions) — /v1/epics/{epic}/revisions in the Epics API.
- [List epics](https://alm-docs.labs.zuselab.dev/api/v1/reference/epics/list-epics) — /v1/projects/{project}/epics in the Epics API.
- [Move an epic](https://alm-docs.labs.zuselab.dev/api/v1/reference/epics/move-an-epic) — /v1/epics/{epic}/status in the Epics API.
- [Restore a version of an epic](https://alm-docs.labs.zuselab.dev/api/v1/reference/epics/restore-a-version-of-an-epic) — /v1/epics/{epic}/revisions/{revision}/restore in the Epics API.
- [Update an epic](https://alm-docs.labs.zuselab.dev/api/v1/reference/epics/update-an-epic) — /v1/epics/{epic} in the Epics API.
- [Add a glossary term](https://alm-docs.labs.zuselab.dev/api/v1/reference/glossary/add-a-glossary-term) — /v1/projects/{project}/glossary in the Glossary API.
- [Delete a glossary term](https://alm-docs.labs.zuselab.dev/api/v1/reference/glossary/delete-a-glossary-term) — /v1/glossary/{term} in the Glossary API.
- [Get a glossary term](https://alm-docs.labs.zuselab.dev/api/v1/reference/glossary/get-a-glossary-term) — /v1/glossary/{term} in the Glossary API.
- [Glossary API](https://alm-docs.labs.zuselab.dev/api/v1/reference/glossary) — A glossary term is a word the project agrees on.
- [List a term's versions](https://alm-docs.labs.zuselab.dev/api/v1/reference/glossary/list-a-terms-versions) — /v1/glossary/{term}/revisions in the Glossary API.
- [List glossary terms](https://alm-docs.labs.zuselab.dev/api/v1/reference/glossary/list-glossary-terms) — /v1/projects/{project}/glossary in the Glossary API.
- [Move a glossary term](https://alm-docs.labs.zuselab.dev/api/v1/reference/glossary/move-a-glossary-term) — /v1/glossary/{term}/status in the Glossary API.
- [Read one version of a term](https://alm-docs.labs.zuselab.dev/api/v1/reference/glossary/read-one-version-of-a-term) — /v1/glossary/{term}/revisions/{revision} in the Glossary API.
- [Restore a version of a term](https://alm-docs.labs.zuselab.dev/api/v1/reference/glossary/restore-a-version-of-a-term) — /v1/glossary/{term}/revisions/{revision}/restore in the Glossary API.
- [Update a glossary term](https://alm-docs.labs.zuselab.dev/api/v1/reference/glossary/update-a-glossary-term) — /v1/glossary/{term} in the Glossary API.
- [Create a group](https://alm-docs.labs.zuselab.dev/api/v1/reference/groups/create-a-group) — /v1/groups in the Groups API.
- [Delete a group](https://alm-docs.labs.zuselab.dev/api/v1/reference/groups/delete-a-group) — /v1/groups/{group} in the Groups API.
- [Get a group](https://alm-docs.labs.zuselab.dev/api/v1/reference/groups/get-a-group) — /v1/groups/{group} in the Groups API.
- [Groups API](https://alm-docs.labs.zuselab.dev/api/v1/reference/groups) — A group is a named bundle of permissions on a team that several members hold at once: put the three people who run the on-call rota into an incident-commanders group and they share its permissions, take one out and they keep only what their own role gives them.
- [List groups](https://alm-docs.labs.zuselab.dev/api/v1/reference/groups/list-groups) — /v1/groups in the Groups API.
- [Replace a group's members](https://alm-docs.labs.zuselab.dev/api/v1/reference/groups/replace-a-groups-members) — /v1/groups/{group}/members in the Groups API.
- [Update a group](https://alm-docs.labs.zuselab.dev/api/v1/reference/groups/update-a-group) — /v1/groups/{group} in the Groups API.
- [Accept a suggestion](https://alm-docs.labs.zuselab.dev/api/v1/reference/imports/accept-a-suggestion) — /v1/suggestions/{suggestion}/accept in the Imports API.
- [Discard an import](https://alm-docs.labs.zuselab.dev/api/v1/reference/imports/discard-an-import) — /v1/imports/{batch}/discard in the Imports API.
- [Get an import](https://alm-docs.labs.zuselab.dev/api/v1/reference/imports/get-an-import) — /v1/imports/{batch} in the Imports API.
- [Import a brief](https://alm-docs.labs.zuselab.dev/api/v1/reference/imports/import-a-brief) — /v1/projects/{project}/imports in the Imports API.
- [Imports API](https://alm-docs.labs.zuselab.dev/api/v1/reference/imports) — A brief import hands a client's brief to Heimdall and gets back suggestions: the epics, stories, requirements, business rules, use cases, glossary terms, personas, stakeholders, risks, assumptions and decisions a good analyst would draft from it, each with how sure Heimdall was, why, and the passage of the brief it drew on, plus improvements, the gaps and questions a project of this kind leaves open.
- [List a project's imports](https://alm-docs.labs.zuselab.dev/api/v1/reference/imports/list-a-projects-imports) — /v1/projects/{project}/imports in the Imports API.
- [List an import's suggestions](https://alm-docs.labs.zuselab.dev/api/v1/reference/imports/list-an-imports-suggestions) — /v1/imports/{batch}/suggestions in the Imports API.
- [Merge a suggestion](https://alm-docs.labs.zuselab.dev/api/v1/reference/imports/merge-a-suggestion) — /v1/suggestions/{suggestion}/merge in the Imports API.
- [Reject a suggestion](https://alm-docs.labs.zuselab.dev/api/v1/reference/imports/reject-a-suggestion) — /v1/suggestions/{suggestion}/reject in the Imports API.
- [Improvements API](https://alm-docs.labs.zuselab.dev/api/v1/reference/improvements) — Improvements are Heimdall's standing suggestions on a project's own record: the gaps a good analyst fills before anyone builds.
- [Sweep a project's record](https://alm-docs.labs.zuselab.dev/api/v1/reference/improvements/sweep-a-projects-record) — /v1/projects/{project}/improvements in the Improvements API.
- [API Reference](https://alm-docs.labs.zuselab.dev/api/v1/reference) — Every operation of the REST API, generated from the OpenAPI document and grouped by resource.
- [Add a label](https://alm-docs.labs.zuselab.dev/api/v1/reference/labels/add-a-label) — /v1/projects/{project}/labels in the Labels API.
- [Labels API](https://alm-docs.labs.zuselab.dev/api/v1/reference/labels) — A label is a word a project pins on its work items: payments, tech-debt, client-asked.
- [List a project's labels](https://alm-docs.labs.zuselab.dev/api/v1/reference/labels/list-a-projects-labels) — /v1/projects/{project}/labels in the Labels API.
- [Remove a label](https://alm-docs.labs.zuselab.dev/api/v1/reference/labels/remove-a-label) — /v1/labels/{label} in the Labels API.
- [Rewrite a label](https://alm-docs.labs.zuselab.dev/api/v1/reference/labels/rewrite-a-label) — /v1/labels/{label} in the Labels API.
- [Links API](https://alm-docs.labs.zuselab.dev/api/v1/reference/links) — A link joins two artefacts of a project with a kind that says how the source relates to the target: a story implements a requirement, a test case verifies a rule, a bug is fixed by a story, a decision supersedes an older one.
- [Link two artefacts](https://alm-docs.labs.zuselab.dev/api/v1/reference/links/link-two-artefacts) — /v1/projects/{project}/links in the Links API.
- [List an artefact's links](https://alm-docs.labs.zuselab.dev/api/v1/reference/links/list-an-artefacts-links) — /v1/projects/{project}/links in the Links API.
- [Unlink two artefacts](https://alm-docs.labs.zuselab.dev/api/v1/reference/links/unlink-two-artefacts) — /v1/links/{link} in the Links API.
- [Get the caller's account](https://alm-docs.labs.zuselab.dev/api/v1/reference/me/get-the-callers-account) — /v1/me in the Me API.
- [Me API](https://alm-docs.labs.zuselab.dev/api/v1/reference/me) — GET /v1/me is the first call a client makes.
- [Notifications API](https://alm-docs.labs.zuselab.dev/api/v1/reference/notifications) — Every alert Zuse Bifrost sends a person (an approval waiting on them, an assignment, a mention, a failing test run, a release approved, an incident opened, a security notice, the Monday digest) also lands in the Notifications Center: the sidebar entry with its unread count and popover, and the page at /notifications.
- [List the caller's notifications](https://alm-docs.labs.zuselab.dev/api/v1/reference/notifications/list-the-callers-notifications) — /v1/me/notifications in the Notifications API.
- [Mark a notification read](https://alm-docs.labs.zuselab.dev/api/v1/reference/notifications/mark-a-notification-read) — /v1/me/notifications/{notification}/read in the Notifications API.
- [Mark every notification read](https://alm-docs.labs.zuselab.dev/api/v1/reference/notifications/mark-every-notification-read) — /v1/me/notifications/read-all in the Notifications API.
- [Archive a persona](https://alm-docs.labs.zuselab.dev/api/v1/reference/personas/archive-a-persona) — /v1/personas/{persona}/archive in the Personas API.
- [Create a persona](https://alm-docs.labs.zuselab.dev/api/v1/reference/personas/create-a-persona) — /v1/projects/{project}/personas in the Personas API.
- [Delete a persona](https://alm-docs.labs.zuselab.dev/api/v1/reference/personas/delete-a-persona) — /v1/personas/{persona} in the Personas API.
- [Get a persona](https://alm-docs.labs.zuselab.dev/api/v1/reference/personas/get-a-persona) — /v1/personas/{persona} in the Personas API.
- [Personas API](https://alm-docs.labs.zuselab.dev/api/v1/reference/personas) — A persona is an archetypal user the project is built for: a named, sketched person with goals, frustrations and habits, so the analyst, the developers and the testers picture the same someone.
- [List a persona's versions](https://alm-docs.labs.zuselab.dev/api/v1/reference/personas/list-a-personas-versions) — /v1/personas/{persona}/revisions in the Personas API.
- [List personas](https://alm-docs.labs.zuselab.dev/api/v1/reference/personas/list-personas) — /v1/projects/{project}/personas in the Personas API.
- [Read one version of a persona](https://alm-docs.labs.zuselab.dev/api/v1/reference/personas/read-one-version-of-a-persona) — /v1/personas/{persona}/revisions/{revision} in the Personas API.
- [Restore a persona](https://alm-docs.labs.zuselab.dev/api/v1/reference/personas/restore-a-persona) — /v1/personas/{persona}/restore in the Personas API.
- [Restore a version of a persona](https://alm-docs.labs.zuselab.dev/api/v1/reference/personas/restore-a-version-of-a-persona) — /v1/personas/{persona}/revisions/{revision}/restore in the Personas API.
- [Update a persona](https://alm-docs.labs.zuselab.dev/api/v1/reference/personas/update-a-persona) — /v1/personas/{persona} in the Personas API.
- [Check the API is up](https://alm-docs.labs.zuselab.dev/api/v1/reference/ping/check-the-api-is-up) — /v1/ping in the Ping API.
- [Ping API](https://alm-docs.labs.zuselab.dev/api/v1/reference/ping) — The one endpoint that needs no token.
- [Get a project's settings](https://alm-docs.labs.zuselab.dev/api/v1/reference/project-settings/get-a-projects-settings) — /v1/projects/{project}/settings in the Project Settings API.
- [Project Settings API](https://alm-docs.labs.zuselab.dev/api/v1/reference/project-settings) — A project's settings are its per-project knobs: how long a sprint runs and on which days, which timezone its deadlines are read in, what work is sized in and on which scale, who a new item goes to, whether pull requests move items along and whether checklists gate a sprint or a done, whether a client guest may comment, whether Heimdall assists, where alerts go on Telegram, the board's limits and hidden columns, the business hours SLAs count and whether a production outage opens an incident.
- [Update a project's settings](https://alm-docs.labs.zuselab.dev/api/v1/reference/project-settings/update-a-projects-settings) — /v1/projects/{project}/settings in the Project Settings API.
- [Archive a project](https://alm-docs.labs.zuselab.dev/api/v1/reference/projects/archive-a-project) — /v1/projects/{project}/archive in the Projects API.
- [Create a project](https://alm-docs.labs.zuselab.dev/api/v1/reference/projects/create-a-project) — /v1/projects in the Projects API.
- [Delete a project](https://alm-docs.labs.zuselab.dev/api/v1/reference/projects/delete-a-project) — /v1/projects/{project} in the Projects API.
- [Get a project](https://alm-docs.labs.zuselab.dev/api/v1/reference/projects/get-a-project) — /v1/projects/{project} in the Projects API.
- [Projects API](https://alm-docs.labs.zuselab.dev/api/v1/reference/projects) — A project is one client engagement from discovery to maintenance: the container every component, environment, epic, story, requirement, test, release and incident lives under.
- [List projects](https://alm-docs.labs.zuselab.dev/api/v1/reference/projects/list-projects) — /v1/projects in the Projects API.
- [Restore a project](https://alm-docs.labs.zuselab.dev/api/v1/reference/projects/restore-a-project) — /v1/projects/{project}/restore in the Projects API.
- [Update a project](https://alm-docs.labs.zuselab.dev/api/v1/reference/projects/update-a-project) — /v1/projects/{project} in the Projects API.
- [Add a RAID item](https://alm-docs.labs.zuselab.dev/api/v1/reference/raid-log/add-a-raid-item) — /v1/projects/{project}/raid-items in the RAID Log API.
- [Delete a RAID item](https://alm-docs.labs.zuselab.dev/api/v1/reference/raid-log/delete-a-raid-item) — /v1/raid-items/{raidItem} in the RAID Log API.
- [Get a RAID item](https://alm-docs.labs.zuselab.dev/api/v1/reference/raid-log/get-a-raid-item) — /v1/raid-items/{raidItem} in the RAID Log API.
- [Get a version of a RAID item](https://alm-docs.labs.zuselab.dev/api/v1/reference/raid-log/get-a-version-of-a-raid-item) — /v1/raid-items/{raidItem}/revisions/{revision} in the RAID Log API.
- [RAID Log API](https://alm-docs.labs.zuselab.dev/api/v1/reference/raid-log) — The RAID log is where a project writes down what may go wrong and what it leans on: risks (something that may happen and would hurt, scored by probability and impact, with a mitigation and a contingency), assumptions (something taken as true for the plan to hold, reviewed until it is confirmed or fails), issues (something that has happened and hurts now, scored by impact) and dependencies (something the project needs from outside itself).
- [List a RAID item's versions](https://alm-docs.labs.zuselab.dev/api/v1/reference/raid-log/list-a-raid-items-versions) — /v1/raid-items/{raidItem}/revisions in the RAID Log API.
- [List RAID items](https://alm-docs.labs.zuselab.dev/api/v1/reference/raid-log/list-raid-items) — /v1/projects/{project}/raid-items in the RAID Log API.
- [Move a RAID item](https://alm-docs.labs.zuselab.dev/api/v1/reference/raid-log/move-a-raid-item) — /v1/raid-items/{raidItem}/status in the RAID Log API.
- [Restore a version of a RAID item](https://alm-docs.labs.zuselab.dev/api/v1/reference/raid-log/restore-a-version-of-a-raid-item) — /v1/raid-items/{raidItem}/revisions/{revision}/restore in the RAID Log API.
- [Update a RAID item](https://alm-docs.labs.zuselab.dev/api/v1/reference/raid-log/update-a-raid-item) — /v1/raid-items/{raidItem} in the RAID Log API.
- [Delete a repository](https://alm-docs.labs.zuselab.dev/api/v1/reference/repositories/delete-a-repository) — /v1/repositories/{repository} in the Repositories API.
- [Disconnect a repository](https://alm-docs.labs.zuselab.dev/api/v1/reference/repositories/disconnect-a-repository) — /v1/repositories/{repository}/disconnect in the Repositories API.
- [Get a repository](https://alm-docs.labs.zuselab.dev/api/v1/reference/repositories/get-a-repository) — /v1/repositories/{repository} in the Repositories API.
- [Repositories API](https://alm-docs.labs.zuselab.dev/api/v1/reference/repositories) — A repository is a Git repository a project's code lives in: its provider, the account that owns it, its name, the branch releases are cut from, whether it is private and which component it builds.
- [List repositories](https://alm-docs.labs.zuselab.dev/api/v1/reference/repositories/list-repositories) — /v1/projects/{project}/repositories in the Repositories API.
- [Reconnect a repository](https://alm-docs.labs.zuselab.dev/api/v1/reference/repositories/reconnect-a-repository) — /v1/repositories/{repository}/reconnect in the Repositories API.
- [Register a repository](https://alm-docs.labs.zuselab.dev/api/v1/reference/repositories/register-a-repository) — /v1/projects/{project}/repositories in the Repositories API.
- [Update a repository](https://alm-docs.labs.zuselab.dev/api/v1/reference/repositories/update-a-repository) — /v1/repositories/{repository} in the Repositories API.
- [Add a requirement](https://alm-docs.labs.zuselab.dev/api/v1/reference/requirements/add-a-requirement) — /v1/projects/{project}/requirements in the Requirements API.
- [Delete a requirement](https://alm-docs.labs.zuselab.dev/api/v1/reference/requirements/delete-a-requirement) — /v1/requirements/{requirement} in the Requirements API.
- [Get a requirement](https://alm-docs.labs.zuselab.dev/api/v1/reference/requirements/get-a-requirement) — /v1/requirements/{requirement} in the Requirements API.
- [Get a version of a requirement](https://alm-docs.labs.zuselab.dev/api/v1/reference/requirements/get-a-version-of-a-requirement) — /v1/requirements/{requirement}/revisions/{revision} in the Requirements API.
- [Requirements API](https://alm-docs.labs.zuselab.dev/api/v1/reference/requirements) — A requirement is one sentence the client and the team agree the system must honour: a functional requirement says what it does for a person (CRM-FR-12), a non-functional one says a quality it keeps while it does it (CRM-NFR-3), with the category the quality belongs to and a measure with the metric and the target.
- [List a requirement's quality reviews](https://alm-docs.labs.zuselab.dev/api/v1/reference/requirements/list-a-requirements-quality-reviews) — /v1/requirements/{requirement}/quality-reviews in the Requirements API.
- [List a requirement's versions](https://alm-docs.labs.zuselab.dev/api/v1/reference/requirements/list-a-requirements-versions) — /v1/requirements/{requirement}/revisions in the Requirements API.
- [List requirements](https://alm-docs.labs.zuselab.dev/api/v1/reference/requirements/list-requirements) — /v1/projects/{project}/requirements in the Requirements API.
- [Move a requirement](https://alm-docs.labs.zuselab.dev/api/v1/reference/requirements/move-a-requirement) — /v1/requirements/{requirement}/status in the Requirements API.
- [Restore a version of a requirement](https://alm-docs.labs.zuselab.dev/api/v1/reference/requirements/restore-a-version-of-a-requirement) — /v1/requirements/{requirement}/revisions/{revision}/restore in the
- [Review a requirement's quality](https://alm-docs.labs.zuselab.dev/api/v1/reference/requirements/review-a-requirements-quality) — /v1/requirements/{requirement}/quality-reviews in the Requirements API.
- [Update a requirement](https://alm-docs.labs.zuselab.dev/api/v1/reference/requirements/update-a-requirement) — /v1/requirements/{requirement} in the Requirements API.
- [Research API](https://alm-docs.labs.zuselab.dev/api/v1/reference/research) — Research is Heimdall reading the web for what a project's brief never states: what products of this kind commonly do, the laws, regulations and standards that apply in the client's country and industry, the integrations the client will expect, what the market already offers and the security and accessibility expectations the client will be held to.
- [List a project's research suggestions](https://alm-docs.labs.zuselab.dev/api/v1/reference/research/list-a-projects-research-suggestions) — /v1/projects/{project}/suggestions in the Research API.
- [List a project's research](https://alm-docs.labs.zuselab.dev/api/v1/reference/research/list-a-projects-research) — /v1/projects/{project}/research in the Research API.
- [Research a project's domain](https://alm-docs.labs.zuselab.dev/api/v1/reference/research/research-a-projects-domain) — /v1/projects/{project}/research in the Research API.
- [Create a role](https://alm-docs.labs.zuselab.dev/api/v1/reference/roles/create-a-role) — /v1/roles in the Roles API.
- [Delete a role](https://alm-docs.labs.zuselab.dev/api/v1/reference/roles/delete-a-role) — /v1/roles/{role} in the Roles API.
- [Get a role](https://alm-docs.labs.zuselab.dev/api/v1/reference/roles/get-a-role) — /v1/roles/{role} in the Roles API.
- [Roles API](https://alm-docs.labs.zuselab.dev/api/v1/reference/roles) — A role is the permission set a member holds on a team.
- [List roles](https://alm-docs.labs.zuselab.dev/api/v1/reference/roles/list-roles) — /v1/roles in the Roles API.
- [Update a role](https://alm-docs.labs.zuselab.dev/api/v1/reference/roles/update-a-role) — /v1/roles/{role} in the Roles API.
- [Add a stakeholder](https://alm-docs.labs.zuselab.dev/api/v1/reference/stakeholders/add-a-stakeholder) — /v1/projects/{project}/stakeholders in the Stakeholders API.
- [Get a stakeholder](https://alm-docs.labs.zuselab.dev/api/v1/reference/stakeholders/get-a-stakeholder) — /v1/stakeholders/{stakeholder} in the Stakeholders API.
- [Stakeholders API](https://alm-docs.labs.zuselab.dev/api/v1/reference/stakeholders) — A stakeholder is a person the project answers to: the client's sponsor and product owner, the people who sign off requirements, UAT runs and releases, Zuse's own account manager or architect, and third parties such as an auditor or a vendor.
- [List a stakeholder's versions](https://alm-docs.labs.zuselab.dev/api/v1/reference/stakeholders/list-a-stakeholders-versions) — /v1/stakeholders/{stakeholder}/revisions in the Stakeholders API.
- [List stakeholders](https://alm-docs.labs.zuselab.dev/api/v1/reference/stakeholders/list-stakeholders) — /v1/projects/{project}/stakeholders in the Stakeholders API.
- [Read one version of a stakeholder](https://alm-docs.labs.zuselab.dev/api/v1/reference/stakeholders/read-one-version-of-a-stakeholder) — /v1/stakeholders/{stakeholder}/revisions/{revision} in the Stakeholders API.
- [Remove a stakeholder](https://alm-docs.labs.zuselab.dev/api/v1/reference/stakeholders/remove-a-stakeholder) — /v1/stakeholders/{stakeholder} in the Stakeholders API.
- [Restore a version of a stakeholder](https://alm-docs.labs.zuselab.dev/api/v1/reference/stakeholders/restore-a-version-of-a-stakeholder) — /v1/stakeholders/{stakeholder}/revisions/{revision}/restore in the
- [Update a stakeholder](https://alm-docs.labs.zuselab.dev/api/v1/reference/stakeholders/update-a-stakeholder) — /v1/stakeholders/{stakeholder} in the Stakeholders API.
- [Change a team member's role](https://alm-docs.labs.zuselab.dev/api/v1/reference/team-members/change-a-team-members-role) — /v1/teams/{team}/members/{member}/role in the Team Members API.
- [Get a team member](https://alm-docs.labs.zuselab.dev/api/v1/reference/team-members/get-a-team-member) — /v1/teams/{team}/members/{member} in the Team Members API.
- [Team Members API](https://alm-docs.labs.zuselab.dev/api/v1/reference/team-members) — Team members are the people inside a team: the owner and everyone invited to work in it, staff and client guests alike.
- [Invite a team member](https://alm-docs.labs.zuselab.dev/api/v1/reference/team-members/invite-a-team-member) — /v1/teams/{team}/members in the Team Members API.
- [List a team's members](https://alm-docs.labs.zuselab.dev/api/v1/reference/team-members/list-a-teams-members) — /v1/teams/{team}/members in the Team Members API.
- [List a team's pending invitations](https://alm-docs.labs.zuselab.dev/api/v1/reference/team-members/list-a-teams-pending-invitations) — /v1/teams/{team}/invitations in the Team Members API.
- [Remove a team member](https://alm-docs.labs.zuselab.dev/api/v1/reference/team-members/remove-a-team-member) — /v1/teams/{team}/members/{member} in the Team Members API.
- [Withdraw an invitation](https://alm-docs.labs.zuselab.dev/api/v1/reference/team-members/withdraw-an-invitation) — /v1/teams/{team}/invitations/{invitation} in the Team Members API.
- [Create a team](https://alm-docs.labs.zuselab.dev/api/v1/reference/teams/create-a-team) — /v1/teams in the Teams API.
- [Delete a team](https://alm-docs.labs.zuselab.dev/api/v1/reference/teams/delete-a-team) — /v1/teams/{team} in the Teams API.
- [Get a team](https://alm-docs.labs.zuselab.dev/api/v1/reference/teams/get-a-team) — /v1/teams/{team} in the Teams API.
- [Get the current team](https://alm-docs.labs.zuselab.dev/api/v1/reference/teams/get-the-current-team) — /v1/teams/current in the Teams API.
- [Teams API](https://alm-docs.labs.zuselab.dev/api/v1/reference/teams) — A team is the tenant: the container every project, role, group, token and webhook endpoint hangs off.
- [List teams](https://alm-docs.labs.zuselab.dev/api/v1/reference/teams/list-teams) — /v1/teams in the Teams API.
- [Rename a team](https://alm-docs.labs.zuselab.dev/api/v1/reference/teams/rename-a-team) — /v1/teams/{team} in the Teams API.
- [Get a token](https://alm-docs.labs.zuselab.dev/api/v1/reference/tokens/get-a-token) — /v1/tokens/{token} in the Tokens API.
- [Tokens API](https://alm-docs.labs.zuselab.dev/api/v1/reference/tokens) — Personal access tokens are what authorise every REST and MCP call.
- [List the caller's tokens](https://alm-docs.labs.zuselab.dev/api/v1/reference/tokens/list-the-callers-tokens) — /v1/tokens in the Tokens API.
- [Mint a token](https://alm-docs.labs.zuselab.dev/api/v1/reference/tokens/mint-a-token) — /v1/tokens in the Tokens API.
- [Revoke a token](https://alm-docs.labs.zuselab.dev/api/v1/reference/tokens/revoke-a-token) — /v1/tokens/{token} in the Tokens API.
- [Add a use case](https://alm-docs.labs.zuselab.dev/api/v1/reference/use-cases/add-a-use-case) — /v1/projects/{project}/use-cases in the Use Cases API.
- [Delete a use case](https://alm-docs.labs.zuselab.dev/api/v1/reference/use-cases/delete-a-use-case) — /v1/use-cases/{useCase} in the Use Cases API.
- [Get a use case](https://alm-docs.labs.zuselab.dev/api/v1/reference/use-cases/get-a-use-case) — /v1/use-cases/{useCase} in the Use Cases API.
- [Get a version of a use case](https://alm-docs.labs.zuselab.dev/api/v1/reference/use-cases/get-a-version-of-a-use-case) — /v1/use-cases/{useCase}/revisions/{revision} in the Use Cases API.
- [Use Cases API](https://alm-docs.labs.zuselab.dev/api/v1/reference/use-cases) — A use case is how an actor reaches a goal with the system, step by step: the persona who acts, the other actors in the room, the goal, what triggers it, what must be true before and after, how often it happens, and the steps (what the actor does and what the system does in reply) in a main flow with alternate and exception flows branching off numbered main steps.
- [List a use case's versions](https://alm-docs.labs.zuselab.dev/api/v1/reference/use-cases/list-a-use-cases-versions) — /v1/use-cases/{useCase}/revisions in the Use Cases API.
- [List use cases](https://alm-docs.labs.zuselab.dev/api/v1/reference/use-cases/list-use-cases) — /v1/projects/{project}/use-cases in the Use Cases API.
- [Move a use case](https://alm-docs.labs.zuselab.dev/api/v1/reference/use-cases/move-a-use-case) — /v1/use-cases/{useCase}/status in the Use Cases API.
- [Replace a use case's steps](https://alm-docs.labs.zuselab.dev/api/v1/reference/use-cases/replace-a-use-cases-steps) — /v1/use-cases/{useCase}/steps in the Use Cases API.
- [Restore a version of a use case](https://alm-docs.labs.zuselab.dev/api/v1/reference/use-cases/restore-a-version-of-a-use-case) — /v1/use-cases/{useCase}/revisions/{revision}/restore in the Use Cases API.
- [Update a use case](https://alm-docs.labs.zuselab.dev/api/v1/reference/use-cases/update-a-use-case) — /v1/use-cases/{useCase} in the Use Cases API.
- [Follow an artefact](https://alm-docs.labs.zuselab.dev/api/v1/reference/watchers/follow-an-artefact) — /v1/projects/{project}/watchers in the Watchers API.
- [Watchers API](https://alm-docs.labs.zuselab.dev/api/v1/reference/watchers) — A watcher is a person following one artefact: they are told of every comment posted on it.
- [List an artefact's followers](https://alm-docs.labs.zuselab.dev/api/v1/reference/watchers/list-an-artefacts-followers) — /v1/projects/{project}/watchers in the Watchers API.
- [Stop following](https://alm-docs.labs.zuselab.dev/api/v1/reference/watchers/stop-following) — /v1/watchers/{watcher} in the Watchers API.
- [Get a webhook delivery](https://alm-docs.labs.zuselab.dev/api/v1/reference/webhook-deliveries/get-a-webhook-delivery) — /v1/webhook-deliveries/{delivery} in the Webhook Deliveries API.
- [Webhook Deliveries API](https://alm-docs.labs.zuselab.dev/api/v1/reference/webhook-deliveries) — Every event Zuse Bifrost posts to one of your webhook endpoints is a delivery: one row per endpoint per event, carrying the signed envelope that was sent, the target's response and where the row is on the retry ladder.
- [List webhook deliveries](https://alm-docs.labs.zuselab.dev/api/v1/reference/webhook-deliveries/list-webhook-deliveries) — /v1/webhook-deliveries in the Webhook Deliveries API.
- [Retry a webhook delivery](https://alm-docs.labs.zuselab.dev/api/v1/reference/webhook-deliveries/retry-a-webhook-delivery) — /v1/webhook-deliveries/{delivery}/retry in the Webhook Deliveries API.
- [Retry every recent dead delivery](https://alm-docs.labs.zuselab.dev/api/v1/reference/webhook-deliveries/retry-every-recent-dead-delivery) — /v1/webhook-deliveries/retry-dead in the Webhook Deliveries API.
- [Delete a webhook endpoint](https://alm-docs.labs.zuselab.dev/api/v1/reference/webhook-endpoints/delete-a-webhook-endpoint) — /v1/webhook-endpoints/{endpoint} in the Webhook Endpoints API.
- [Get a webhook endpoint](https://alm-docs.labs.zuselab.dev/api/v1/reference/webhook-endpoints/get-a-webhook-endpoint) — /v1/webhook-endpoints/{endpoint} in the Webhook Endpoints API.
- [Webhook Endpoints API](https://alm-docs.labs.zuselab.dev/api/v1/reference/webhook-endpoints) — A webhook endpoint is a URL of yours that Zuse Bifrost posts events to, with the events it subscribes to and a signing secret you verify each delivery against.
- [List webhook endpoints](https://alm-docs.labs.zuselab.dev/api/v1/reference/webhook-endpoints/list-webhook-endpoints) — /v1/webhook-endpoints in the Webhook Endpoints API.
- [Pause a webhook endpoint](https://alm-docs.labs.zuselab.dev/api/v1/reference/webhook-endpoints/pause-a-webhook-endpoint) — /v1/webhook-endpoints/{endpoint}/pause in the Webhook Endpoints API.
- [Register a webhook endpoint](https://alm-docs.labs.zuselab.dev/api/v1/reference/webhook-endpoints/register-a-webhook-endpoint) — /v1/webhook-endpoints in the Webhook Endpoints API.
- [Resume a webhook endpoint](https://alm-docs.labs.zuselab.dev/api/v1/reference/webhook-endpoints/resume-a-webhook-endpoint) — /v1/webhook-endpoints/{endpoint}/resume in the Webhook Endpoints API.
- [Rotate a webhook endpoint's secret](https://alm-docs.labs.zuselab.dev/api/v1/reference/webhook-endpoints/rotate-a-webhook-endpoints-secret) — /v1/webhook-endpoints/{endpoint}/rotate-secret in the Webhook Endpoints API.
- [Test-fire a webhook endpoint](https://alm-docs.labs.zuselab.dev/api/v1/reference/webhook-endpoints/test-fire-a-webhook-endpoint) — /v1/webhook-endpoints/{endpoint}/test in the Webhook Endpoints API.
- [Webhook Events API](https://alm-docs.labs.zuselab.dev/api/v1/reference/webhook-events) — A read-only polling endpoint that surfaces the most recent webhook deliveries for a given event type.
- [Poll recent webhook events](https://alm-docs.labs.zuselab.dev/api/v1/reference/webhook-events/poll-recent-webhook-events) — /v1/webhook-events in the Webhook Events API.
- [Add a work item](https://alm-docs.labs.zuselab.dev/api/v1/reference/work-items/add-a-work-item) — /v1/projects/{project}/work-items in the Work Items API.
- [Assign a work item](https://alm-docs.labs.zuselab.dev/api/v1/reference/work-items/assign-a-work-item) — /v1/work-items/{item}/assign in the Work Items API.
- [Delete a work item](https://alm-docs.labs.zuselab.dev/api/v1/reference/work-items/delete-a-work-item) — /v1/work-items/{item} in the Work Items API.
- [Get a version of a work item](https://alm-docs.labs.zuselab.dev/api/v1/reference/work-items/get-a-version-of-a-work-item) — /v1/work-items/{item}/revisions/{revision} in the Work Items API.
- [Get a work item](https://alm-docs.labs.zuselab.dev/api/v1/reference/work-items/get-a-work-item) — /v1/work-items/{item} in the Work Items API.
- [Work Items API](https://alm-docs.labs.zuselab.dev/api/v1/reference/work-items) — A work item is one row of the tracker: a story, a task, a sub-task, a bug, a spike or an improvement.
- [List a work item's quality reviews](https://alm-docs.labs.zuselab.dev/api/v1/reference/work-items/list-a-work-items-quality-reviews) — /v1/work-items/{item}/quality-reviews in the Work Items API.
- [List a work item's versions](https://alm-docs.labs.zuselab.dev/api/v1/reference/work-items/list-a-work-items-versions) — /v1/work-items/{item}/revisions in the Work Items API.
- [List my work items](https://alm-docs.labs.zuselab.dev/api/v1/reference/work-items/list-my-work-items) — /v1/me/work-items in the Work Items API.
- [List work items](https://alm-docs.labs.zuselab.dev/api/v1/reference/work-items/list-work-items) — /v1/projects/{project}/work-items in the Work Items API.
- [Move a work item](https://alm-docs.labs.zuselab.dev/api/v1/reference/work-items/move-a-work-item) — /v1/work-items/{item}/status in the Work Items API.
- [Replace a work item's acceptance criteria](https://alm-docs.labs.zuselab.dev/api/v1/reference/work-items/replace-a-work-items-acceptance-criteria) — /v1/work-items/{item}/acceptance-criteria in the Work Items API.
- [Restore a version of a work item](https://alm-docs.labs.zuselab.dev/api/v1/reference/work-items/restore-a-version-of-a-work-item) — /v1/work-items/{item}/revisions/{revision}/restore in the Work Items API.
- [Review a work item's quality](https://alm-docs.labs.zuselab.dev/api/v1/reference/work-items/review-a-work-items-quality) — /v1/work-items/{item}/quality-reviews in the Work Items API.
- [Update a work item](https://alm-docs.labs.zuselab.dev/api/v1/reference/work-items/update-a-work-item) — /v1/work-items/{item} in the Work Items API.
- [Tenancy & Scopes](https://alm-docs.labs.zuselab.dev/api/v1/tenancy-and-scopes) — Every read and write is scoped to one team, scope entries on a token narrow it further to chosen projects, and a guest's token never reaches beyond their invitations.
- [Versioning & Deprecation](https://alm-docs.labs.zuselab.dev/api/v1/versioning-and-deprecation) — How the API is versioned under /v1, how new functionality is added, and how breaking changes are announced and retired.

## building

- [Board](https://alm-docs.labs.zuselab.dev/building/board) — The Board page of a project: the running sprint's work in a column per status, dragged along its lifecycle and into its place in the order, with the limits each column keeps, swimlanes by epic, person or kind, and the quick filters.
- [Building](https://alm-docs.labs.zuselab.dev/building) — Where the team turns the planning record into working software: the sprints it plans and commits to, the board it works them on, with the time tracking, the definitions of ready and done and the Git links joining as they land.
- [Sprints](https://alm-docs.labs.zuselab.dev/building/sprints) — Plan a sprint with its dates, goal and capacity, pull its scope from the backlog, put it to the team for the commitment that starts it, follow it while it runs, close it with its velocity and carry the unfinished work on.

## copilot

- [Brief import](https://alm-docs.labs.zuselab.dev/copilot/brief-import) — What Heimdall is given before it reads a brief, how it fills each kind of suggestion from one uniform row, how it judges its own confidence, why it runs on the queue as you, what it costs and where it stops.
- [The Council](https://alm-docs.labs.zuselab.dev/copilot/council) — Heimdall's council: seven named voices, each a lens, convened on a story, a requirement, a rule, a brief import or a project Heimdall scaffolded in conversation; how the voices research the ground, read the record, answer one another and refine the plan Heimdall drafts, how Heimdall rules, what accepting a finding writes, what a sitting costs and where it stops.
- [Impact analysis](https://alm-docs.labs.zuselab.dev/copilot/impact-analysis) — What Heimdall reads before it weighs a change request, what it is told to look for, how its answer becomes the draft and the numbers on the request, what a reading costs, how the council's change impact moment differs, and where it stops.
- [Improvement Sweep](https://alm-docs.labs.zuselab.dev/copilot/improvement-sweep) — The five gaps Heimdall's sweep looks for in a project's record, how it proposes a card per gap on the review queue, why the same idea is never proposed twice, when it runs on its own, what accepting a card does and what it costs: nothing.
- [Heimdall](https://alm-docs.labs.zuselab.dev/copilot) — The operator inside Zuse Bifrost: ask it about your projects, teams, webhooks and history in plain words, have it do the routine work, and confirm anything that changes what already exists. Beside every page, metered against the team's monthly AI budget.
- [Inline assists](https://alm-docs.labs.zuselab.dev/copilot/inline-assist) — Ask Heimdall beside any long field of an epic, story, requirement, rule, use case, RAID item, decision or dictionary entry: draft it, improve it, shorten it, make it testable or rewrite it as Given, When, Then, then take the draft or drop it.
- [The Panel](https://alm-docs.labs.zuselab.dev/copilot/panel) — Heimdall sheet beside every page, end to end: opening it, the context chip and the eye, the start screen, threads, the composer, the model tiers and the review switch, the work timeline and the streamed answer, buttons and follow-ups, confirmation cards and the budget line.
- [Quality review](https://alm-docs.labs.zuselab.dev/copilot/quality-review) — What Heimdall reads before it judges a record, how it grades and codes a finding, why the score is arithmetic, what a review costs and where it stops: it never writes to the record.
- [Research](https://alm-docs.labs.zuselab.dev/copilot/research) — What Heimdall is told before it reads the web for a project, what it searches for, how its notes and suggestions are shaped and filtered, why a dismissed idea never returns, what a run costs and where it stops: it never writes to the record.
- [Permissions & Safety](https://alm-docs.labs.zuselab.dev/copilot/safety-and-permissions) — Who may use Heimdall, how a team member's role bounds what it can do, the confirmation gate on anything that changes what exists, what the activity log records, what the model is shown and what it is never shown, and the models behind it.
- [Start a Project in Conversation](https://alm-docs.labs.zuselab.dev/copilot/start-a-project) — Tell Heimdall about a client and what they need; it creates the client and the project, writes the record as drafts, asks only for what it cannot infer, and convenes the council on the result inside the conversation.
- [Usage & Budgets](https://alm-docs.labs.zuselab.dev/copilot/usage-and-budgets) — How every model call is priced and filed, what a turn costs on each tier, the team's monthly AI budget with its warning line and its cap, who is told when a line is crossed, what is never metered, and where to read the statement.

## documents

- [Business Requirements Document](https://alm-docs.labs.zuselab.dev/documents/brd) — What the BRD a project generates prints, section by section, where each section is read from, what the executive summary and the sign-off page ask of the client, and how to render the copy the sponsor signs.
- [Generated Documents](https://alm-docs.labs.zuselab.dev/documents/generated-documents) — Generate a business requirements document or a software requirements specification from the project's own record, edit the opening page Heimdall drafts, render it again, put it to the project manager, and share the final copy with the client.
- [Documents](https://alm-docs.labs.zuselab.dev/documents) — The documents a project generates from the record its team wrote once: the business requirements document the client signs and the software requirements specification the team builds against, each rendered, reviewed, approved and shared from one page.
- [Software Requirements Specification](https://alm-docs.labs.zuselab.dev/documents/srs) — What the SRS a project generates prints, section by section, where each section is read from, how the introduction is drafted, and how the team builds and tests against the final copy.

## guests

- [Approving as a Client](https://alm-docs.labs.zuselab.dev/guests/approving-requirements) — What an approval that names you looks like, how to approve, request changes or reject it with a reason, what your verdict does, and what the team sees afterwards.
- [Documents Shared With You](https://alm-docs.labs.zuselab.dev/guests/documents-shared-with-you) — Where the final BRD and SRS of your projects appear, how to download or open one, what the status badges mean, and why a draft the team is still working on is not shown to you.
- [For Clients](https://alm-docs.labs.zuselab.dev/guests) — The guest's view of a project: the approved record, the approvals assigned to you, and what stays on the team's side of the line.
- [Signing Off the Scope](https://alm-docs.labs.zuselab.dev/guests/signing-off-scope) — What a frozen baseline is, how the sign-off reaches you and what your signature means, what a change request is and how to raise one, and what you read of each afterwards.

## integrations

- [Integrations](https://alm-docs.labs.zuselab.dev/integrations) — GitHub, CI/CD pipelines, Telegram, email, Postman and custom agents.
- [Telegram](https://alm-docs.labs.zuselab.dev/integrations/telegram) — Link your account to the Zuse Bifrost bot with a one-time code, receive alerts in a private chat, and ask the bot who you are linked as.

## introduction

- [Introduction](https://alm-docs.labs.zuselab.dev/introduction) — The five phases of a project in Zuse Bifrost, the one record they share, and the roles that work in it.

## mcp

- [MCP Authentication](https://alm-docs.labs.zuselab.dev/mcp/v1/authentication) — How a client connects to the MCP server, by signing in with OAuth 2.1 or with a personal access token, and how every tool enforces its ability.
- [Connecting ChatGPT Desktop](https://alm-docs.labs.zuselab.dev/mcp/v1/connecting-chatgpt-desktop) — Configure ChatGPT's developer-mode connectors to work with Zuse Bifrost, by signing in or with a personal access token.
- [Connecting Claude](https://alm-docs.labs.zuselab.dev/mcp/v1/connecting-claude-desktop) — Add the Zuse Bifrost MCP server to claude.ai, Claude Desktop and Claude Code as a connector, by signing in or with a personal access token.
- [Connecting Cursor](https://alm-docs.labs.zuselab.dev/mcp/v1/connecting-cursor) — Configure Cursor's MCP support to use the Zuse Bifrost server, by signing in or with a personal access token.
- [Connecting VS Code](https://alm-docs.labs.zuselab.dev/mcp/v1/connecting-vscode-claude) — Add the Zuse Bifrost MCP server to VS Code or the Claude Code extension, by signing in or with a personal access token.
- [MCP Server](https://alm-docs.labs.zuselab.dev/mcp/v1) — Connect Claude, Cursor, ChatGPT or VS Code to a project's record over the Model Context Protocol and let an agent read context and write the record back, as far as the person's role allows.
- [Prompting Guide](https://alm-docs.labs.zuselab.dev/mcp/v1/prompting-guide) — Prompt patterns that respect rate limits, keep the blast radius small and keep the person in view when an LLM drives the MCP server.
- [MCP Quickstart](https://alm-docs.labs.zuselab.dev/mcp/v1/quickstart) — Add the Zuse Bifrost MCP server as a Claude connector, sign in, approve the connection and run your first tool call.
- [Resources Reference](https://alm-docs.labs.zuselab.dev/mcp/v1/resources-reference) — The three read-only JSON resources the MCP server publishes so an agent can ground itself before it calls a tool.
- [MCP Security](https://alm-docs.labs.zuselab.dev/mcp/v1/security) — How OAuth connections and personal access tokens are scoped, revoked and audited, and what to do the moment a credential leaks.
- [Tools Reference](https://alm-docs.labs.zuselab.dev/mcp/v1/tools-reference) — Every MCP tool the Zuse Bifrost server exposes today, grouped by what it works on, with the ability each one enforces.
- [get_me](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/account/get-me) — Describe the person the token acts as — the team the token is scoped to, every team held, where alerts go, the unread count and whether Telegram is linked. Takes no input.
- [Account Tools](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/account) — The account behind the token: who is acting, which team the token is scoped to, where alerts go and what sits unread in the Notifications Center.
- [list_notifications](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/account/list-notifications) — Read the Notifications Center of the person the token acts for — every alert sent to them, newest first, with its class, where it points and whether it was read.
- [mark_all_notifications_read](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/account/mark-all-notifications-read) — Mark every unread entry of the person's Notifications Center as read in one call.
- [mark_notification_read](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/account/mark-notification-read) — Mark one entry of the person's Notifications Center as read.
- [assign_work_item](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/build/assign-work-item) — Hand a work item to a member of the team, or to nobody, and announce the hand-over.
- [create_label](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/build/create-label) — Adds a word the project pins on its work items, with a colour and a meaning.
- [create_work_item](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/build/create-work-item) — Adds a work item of any kind to a project's backlog, with everything set at once; the full form beside create_story_draft.
- [delete_label](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/build/delete-label) — Deletes a label of a project after the person confirms; every item wearing it loses it.
- [delete_work_item](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/build/delete-work-item) — Deletes a work item after the person confirms; cancelling with a reason keeps it on the record instead.
- [get_board_snapshot](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/build/get-board-snapshot) — Reads a project's board as the Board page draws it, the columns the project keeps in order with their limits, tallies and cards, for the running sprint, a sprint by id, every open item or the unplanned ones; a guest token reads none.
- [get_sprint](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/build/get-sprint) — Fetches one sprint by id with everything the list gives and its scope, the work items it holds in the backlog's order with their status and points, plus the points planned and done.
- [get_work_item](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/build/get-work-item) — One work item by id, with its reference, kind, title, prose, status, priority, people, estimates, the fields its kind adds, the components it touches and its acceptance criteria in order.
- [Build Tools](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/build) — The tracker of a project: its stories, tasks, sub-tasks, bugs, spikes and improvements, each numbered from the same sequence as the epics (`CRM-142`) with its kind, status from the backlog to done, resolution, priority, the people on it, its estimates and dates, the fields its kind adds and, for a story, the acceptance criteria that say when it is done.
- [list_labels](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/build/list-labels) — A project's labels by name, each with its colour, what it means and how many work items carry it; the vocabulary to read before you draft or filter stories.
- [list_my_work](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/build/list-my-work) — The work items assigned to the person the token acts as, across every project the token may see, open ones by default.
- [list_sprints](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/build/list-sprints) — Lists a project's sprints in number order with their dates, status, capacity, the points committed to and finished, the velocity, the item count and who started and closed them, narrowed by status, open or words; a guest token reads none.
- [list_work_items](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/build/list-work-items) — A project's stories, tasks, sub-tasks, bugs, spikes and improvements in the project's order, with reference, kind, status, priority, people and estimate, narrowed by the typed filters and for a guest token.
- [move_work_item](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/build/move-work-item) — Move a work item along its lifecycle, from the backlog through ready, in progress, in review and in QA to done or cancelled, with a resolution on a close.
- [update_label](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/build/update-label) — Changes a label in part; every item wearing it shows the new word at once.
- [update_work_item](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/build/update-work-item) — Changes a work item in part; the criteria, components and labels are replaced only when their list is sent, and every change writes a version.
- [create_repository](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/code/create-repository) — Registers where a component's code lives, so the Git integration can link branches, commits and pull requests to it later.
- [delete_repository](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/code/delete-repository) — Removes a repository from a project's registry after the person confirms; the code itself is untouched.
- [get_repository](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/code/get-repository) — One repository by id, with its provider, owner, name, default branch, address, privacy, component and disconnected stamp.
- [Code Tools](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/code) — Where a project's code lives: the Git repositories the team registered, each with its provider, the owner and name as the provider spells them, the branch releases are cut from, the address, whether it is private and the component it builds.
- [list_repositories](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/code/list-repositories) — Paginated list of the Git repositories a project's code lives in, each with its provider, owner, name, default branch, privacy and component, narrowed by provider, component, disconnected state or search words.
- [update_repository](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/code/update-repository) — Changes a registered repository in part.
- [create_data_entity](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/dictionary/create-data-entity) — Adds a thing the system keeps records of, with its fields, so the data dictionary a brief implies is laid down as the conversation goes.
- [create_glossary_term](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/dictionary/create-glossary-term) — Adds a word the project agrees on, so the vocabulary a brief uses is pinned as the conversation goes.
- [delete_data_entity](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/dictionary/delete-data-entity) — Deletes a data entity and its fields after the person confirms; deprecating keeps it on the record instead.
- [delete_glossary_term](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/dictionary/delete-glossary-term) — Deletes a glossary term after the person confirms; deprecating keeps the word on the record instead.
- [get_data_entity](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/dictionary/get-data-entity) — One data entity by id with its fields in order, each with its type, flags, validation, example and description.
- [get_glossary_term](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/dictionary/get-glossary-term) — One glossary term by id, with its definition, other names, related terms, source and review status.
- [Dictionary Tools](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/dictionary) — The dictionary of a project: the glossary (the words the project agrees on, each with one definition, the other names it goes by, the terms it leans on, its source and its review status) and the data entities (the things the project keeps records of, each with its fields, their types, flags, validation and examples, its component, its owner, whether it holds personal data and how long it is kept).
- [list_data_entities](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/dictionary/list-data-entities) — Paginated list of the things a project keeps records of, each with its component, owner, personal-data flag, retention note, review status and field count, narrowed by status, component, personal data or search words.
- [list_glossary_terms](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/dictionary/list-glossary-terms) — Paginated list of the words a project agrees on, each with its definition, other names, related terms, source and review status, narrowed by status or search words.
- [update_data_entity](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/dictionary/update-data-entity) — Changes a data entity in part, replaces its fields when a list is sent and moves it along its review when a status is sent.
- [update_glossary_term](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/dictionary/update-glossary-term) — Changes a glossary term in part and moves it along its review when a status is sent.
- [generate_document](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/documents/generate-document) — Asks a project for a business requirements document or a software requirements specification as the token's holder, with a title, a file format and a scope, and answers with the document while it renders in the background.
- [get_document](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/documents/get-document) — Fetches one generated document by id with its kind, reference, title, format, status, scope, opening prose, stamps and download address, and on request the rendered document as plain words.
- [Documents Tools](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/documents) — The documents a project writes from its own record: the business requirements document the client signs and the software requirements specification the team builds against, each asked for with a kind, a title, a file format (PDF or HTML) and a scope (the record as it stands, with or without drafts, or a frozen baseline), rendered in the background as the person who asked and under their permissions, numbered within its kind (`BRD #2`), with an opening page Heimdall drafts when nobody wrote it, moved to final by the project manager's approval, which supersedes the kind's earlier final copy, and shared with the client's guests from that moment.
- [list_documents](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/documents/list-documents) — Lists a project's generated documents newest first with their kind, reference, title, format, status, scope, stamps and download address, narrowed by kind, status or words; a guest token sees the final copies only.
- [create_webhook_endpoint](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/observability/create-webhook-endpoint) — Register an outbound webhook endpoint for the token's team. The signing secret is returned in this response only.
- [delete_webhook_endpoint](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/observability/delete-webhook-endpoint) — Remove an outbound webhook endpoint. Destructive — an integration listening on it goes dark at once; its delivery log is kept.
- [get_activity_log](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/observability/get-activity-log) — Read the activity log of one subject, newest first — every change made to it, who made it, the surface it came through and the columns that changed.
- [get_webhook_delivery](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/observability/get-webhook-delivery) — One outbound webhook delivery by UUID — its event, status, attempts, the payload that was posted and what the endpoint answered.
- [get_webhook_endpoint](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/observability/get-webhook-endpoint) — One of the team's outbound webhook endpoints by UUID, with its health counters. The signing secret is never returned.
- [Observability Tools](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/observability) — Where to look when something did not happen: outbound webhook endpoints and their deliveries, and the activity log of every change made to a subject and who made it, from the application, the REST API, an MCP tool, an accepted Heimdall draft or a scheduled job.
- [list_webhook_deliveries](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/observability/list-webhook-deliveries) — The team's outbound webhook delivery log, newest first — what was posted, what the endpoint answered, and where each row is on the retry ladder.
- [list_webhook_endpoints](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/observability/list-webhook-endpoints) — List the outbound webhook endpoints registered for the token's team, paginated, with their health counters. Secrets are never returned.
- [pause_webhook_endpoint](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/observability/pause-webhook-endpoint) — Stop deliveries to an endpoint without removing it. Events raised while paused are not queued for it.
- [resume_webhook_endpoint](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/observability/resume-webhook-endpoint) — Start deliveries to a paused endpoint again and clear its failure streak. Events raised while paused are not replayed.
- [retry_dead_webhook_deliveries](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/observability/retry-dead-webhook-deliveries) — Replay every webhook delivery the team dead-lettered since an instant, once the consumer is fixed. Defaults to the last 24 hours.
- [retry_webhook_delivery](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/observability/retry-webhook-delivery) — Replay one failed or dead-lettered webhook delivery from the start of the retry ladder. A pending or delivered row is refused.
- [rotate_webhook_endpoint_secret](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/observability/rotate-webhook-endpoint-secret) — Replace an endpoint's signing secret. The new secret is returned in this response only and the old one stops verifying at once.
- [test_webhook_endpoint](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/observability/test-webhook-endpoint) — Queue a synthetic test event to an endpoint so its consumer can be checked end to end. Returns the queued delivery to poll.
- [create_persona](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/people/create-persona) — Adds one of the people the product is built for, so the stories that follow have someone to be written as.
- [create_stakeholder](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/people/create-stakeholder) — Adds one of the people a project answers to, so the sponsor and the product owner a brief names take their seats as the conversation goes.
- [delete_persona](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/people/delete-persona) — Deletes a persona of a project after the person confirms; the stories and use cases written as them keep their words.
- [delete_stakeholder](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/people/delete-stakeholder) — Deletes a stakeholder of a project after the person confirms; approvals that name the seat lose an approver.
- [get_persona](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/people/get-persona) — Fetch a single persona by UUID — their sketch in full, with goals, frustrations, behaviours, proficiency, devices, quote and archive stamp.
- [get_stakeholder](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/people/get-stakeholder) — Fetch a single stakeholder by UUID — their side, role, weight, RACI default, approver flags and, for a staff token, contact details, notes and linked account.
- [People Tools](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/people) — The people of a project: the stakeholders it answers to (the client's sponsor, product owner and approvers, Zuse's own leads, third parties, each with a side, a role, a weight and the approvals that name them) and the personas it is built for (named, sketched users with goals, frustrations and habits, the \"as a …\" of every story).
- [list_personas](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/people/list-personas) — Paginated list of the archetypal users a project is built for, with their goals, frustrations, habits, proficiency and devices, narrowed by search words or archived state.
- [list_stakeholders](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/people/list-stakeholders) — Paginated list of the people a project answers to, with their side, role, weight and the approvals that name them, narrowed by side, role, approval or search words.
- [update_persona](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/people/update-persona) — Changes a persona of a project in part; the devices replace the list when sent.
- [update_stakeholder](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/people/update-stakeholder) — Changes a stakeholder of a project in part, so an approval flag or an email can be added as the person mentions it.
- [analyse_change_impact](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/analyse-change-impact) — Asks Heimdall to read one change request against its baseline and the records it names, writes the draft onto the request, fills the impact fields the analyst left empty, and answers with the request; one metered call under the team's AI budget.
- [comment_on_item](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/comment-on-item) — Post a comment on one artefact as the person the token acts as, in Markdown, under a first comment when answering; the people named and the followers are told and comment.created goes out.
- [convene_council](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/convene-council) — Convenes Heimdall's council on a brief import, a work item, a requirement, a business rule or a change request with the voices named, and answers with the sitting queued; spends the team's AI budget within the council's share.
- [create_baseline](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/create-baseline) — Composes a draft baseline on a project from approved records, with its name, kind and words, and answers with the draft and its record rows; nothing is frozen until a person submits it and the project manager approves.
- [create_epic](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/create-epic) — Adds an epic to a project as a draft, so Heimdall can split a brief into bodies of work and hang the stories under them.
- [create_raid_item](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/create-raid-item) — Adds any entry of the RAID log, an assumption, an issue or a dependency as well as a risk; the full form beside raise_risk.
- [create_requirement_draft](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/create-requirement-draft) — Add a functional or non-functional requirement to a project as a draft a person reviews, with its statement, source, priority, measure and verification method.
- [create_story_draft](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/create-story-draft) — Add a story to a project's backlog with its sentence, its epic, its priority and its acceptance criteria, as a draft a person reviews.
- [create_use_case](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/create-use-case) — Adds a use case as a draft, with its main, alternate and exception flows, so how a persona reaches a goal is written step by step.
- [decide_council_finding](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/decide-council-finding) — Decides one finding of a council sitting on the person's word, after they confirm; accepting takes it up, dismissing sets it aside for good.
- [decide_suggestion](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/decide-suggestion) — Decides one row of the review queue on the person's word, after they confirm; accepting writes the record, rejecting settles the row.
- [delete_baseline](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/delete-baseline) — Deletes a draft baseline with its record rows and versions; a baseline past its draft is the record and is superseded rather than deleted.
- [delete_business_rule](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/delete-business-rule) — Deletes a business rule after the person confirms; deprecating keeps it on the record instead.
- [delete_change_request](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/delete-change-request) — Deletes a change request that was never agreed, with its links and versions; a request past its gate is closed rather than deleted, and its number is never handed out again.
- [delete_decision](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/delete-decision) — Deletes a decision after the person confirms; rejecting or deprecating keeps it on the record instead.
- [delete_epic](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/delete-epic) — Deletes an epic after the person confirms; the work items under it stay without an epic.
- [delete_raid_item](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/delete-raid-item) — Deletes a RAID item after the person confirms; closing it keeps it on the log instead.
- [delete_requirement](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/delete-requirement) — Deletes a requirement after the person confirms; deprecating keeps it on the record instead.
- [delete_use_case](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/delete-use-case) — Deletes a use case and its steps after the person confirms; deprecating keeps it on the record instead.
- [get_approval_request](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/get-approval-request) — Fetches one approval request by UUID with the record it is about, the approvers the policy named, the tally, the clocks and every verdict given, round by round.
- [get_baseline](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/get-baseline) — Fetches one baseline by id with the records it holds, each by family, key, title, the version pinned and whether it is still locked or was unlocked by a change request.
- [get_business_rule](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/get-business-rule) — One business rule by id, with its reference, name, kind, statement, condition and action, exceptions, worked examples, authority, priority, dates in force, status and owner.
- [get_change_request](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/get-change-request) — Fetches one change request by id with the records it touches, its impact, Heimdall's draft, its baseline and the people behind it; a guest token reads it without the effort, the cost and the draft.
- [get_council_session](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/get-council-session) — One sitting of Heimdall's council with everything it holds, the verdict, the voices' turns and every finding with what a person decided; free to call.
- [get_decision](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/get-decision) — One decision by id, with its reference, kind, title, context, the options weighed, what was decided, consequences, status, the day decided, deciders and the decision it supersedes.
- [get_epic](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/get-epic) — One epic by id, with its reference, goal, prose, owner, priority, status, dates and colour.
- [get_import_batch](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/get-import-batch) — Fetches one brief import with its words and every suggestion Heimdall drafted from it, each with its decision so far.
- [get_raid_item](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/get-raid-item) — One RAID item by id, with its reference, kind, title, description, area, probability, impact and score, mitigation and contingency, owner and raiser, dates, dependency and status.
- [get_requirement](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/get-requirement) — One requirement by id, with its reference, kind, category, statement, rationale, source, priority, measure, verification method, status and owner.
- [get_revision](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/get-revision) — One version of an artefact by id, with its snapshot, the diff from the version before, who wrote it and why.
- [get_use_case](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/get-use-case) — One use case by id, with its reference, title, actor, other actors, goal, trigger, conditions, frequency, priority, status and its steps in order, each in the main flow or in an alternate or exception flow that leaves a main step.
- [Planning Tools](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning) — The planning record of a project: its epics (the bodies of work the client recognises, each numbered from the project's tracker sequence, `CRM-12`, with its goal, value, measures, owner, MoSCoW priority, status from draft to done and dates) and its requirements (what the system shall do, functional, `CRM-FR-12`, and the qualities it shall keep, non-functional, `CRM-NFR-3`, each with a category and a measure, with the statement, the source, the priority, the verification method and the status from draft to baselined).
- [link_artefacts](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/link-artefacts) — Join two artefacts of a project with a kind read from the source, such as a story that implements a requirement; a repeat, a self-link or a foreign end is refused, and link.created goes out.
- [list_attachments](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/list-attachments) — The files pinned on one artefact, newest first, each with its name, size, kind, uploader and the REST endpoint that streams its bytes; the agreed record only for a guest token.
- [list_baselines](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/list-baselines) — Lists a project's baselines in the project's order with their kind, status, version, clocks and record count, narrowed by kind, status or words; a guest token sees the frozen baselines only.
- [list_business_rules](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/list-business-rules) — A project's business rules in the project's order, with reference, name, kind, statement, condition and action, examples, authority, priority, dates in force, status and owner, narrowed for a guest token.
- [list_change_requests](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/list-change-requests) — Lists a project's change requests in the project's order with their reason, priority, impact level, status, baseline and the people behind them, narrowed by reason, status, priority, impact level, baseline or words; a guest token sees the requests they raised or asked for, without the effort, the cost and Heimdall's draft.
- [list_comments](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/list-comments) — The conversation on one artefact, oldest first, each comment with its author, its audience, the people it names, the thread it answers and whether the thread is resolved; the open comments only for a guest token.
- [list_council_sessions](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/list-council-sessions) — The sittings of Heimdall's council on a project, newest first, each with its moment, record, voices, status, verdict, counts, cost and turns; free to call.
- [list_decisions](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/list-decisions) — A project's decisions in the project's order, with reference, kind, title, context, the options weighed, what was decided, consequences, status, the day decided, deciders and the decision each supersedes; never for a guest token.
- [list_epics](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/list-epics) — A project's epics in the project's order, with reference, goal, owner, priority, status and dates, narrowed for a guest token.
- [list_import_batches](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/list-import-batches) — Lists the brief imports of a project, newest first, with where each reading stands.
- [list_links](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/list-links) — Every link that touches one artefact, both ends named with their keys and titles, each read from the artefact's side; never for a guest token.
- [list_pending_approvals](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/list-pending-approvals) — Lists approval requests as the inbox shows them, waiting on the token holder by default, raised by them or everything they may see, with filters and paging.
- [list_quality_reviews](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/list-quality-reviews) — The quality reviews Heimdall wrote of one work item, requirement or business rule, newest first, each with the version it read, its score, band, summary and findings; free to call.
- [list_raid_items](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/list-raid-items) — A project's RAID log in the project's order, with reference, kind, title, area, probability, impact and score, mitigation and contingency, owner and raiser, dates, dependency and status; never for a guest token.
- [list_requirements](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/list-requirements) — A project's functional and non-functional requirements in the project's order, with reference, kind, category, statement, source, priority, measure, verification method, status and owner, narrowed for a guest token.
- [list_research_notes](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/list-research-notes) — Reads what Heimdall's research sweep found about a project's domain, with the latest run's standing.
- [list_revisions](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/list-revisions) — Every version of a revisable artefact, newest first, with who wrote it, why, and the diff from the version before.
- [list_use_cases](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/list-use-cases) — A project's use cases in the project's order, with reference, title, actor, other actors, goal, trigger, conditions, frequency, priority and status, narrowed for a guest token; the steps come with get_use_case.
- [propose_business_rule](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/propose-business-rule) — Add a business rule to a project as a draft a person reviews, with its kind, statement, condition and action, exceptions, worked examples, authority and priority.
- [raise_change_request](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/raise-change-request) — Raises a change request on a project, numbered from the change requests' own sequence, with its reason, the baseline it changes, the stakeholder who asked, the records it touches and whatever impact is known; a guest token raises one without the impact.
- [raise_risk](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/raise-risk) — Raise a risk in a project's RAID log, numbered from the log's sequence, scored by probability and impact, raised by the person the token acts as and open for the review meeting.
- [record_decision_draft](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/record-decision-draft) — Record a decision in a project as proposed, numbered from the decisions' sequence, with its context, the options weighed and what is proposed, for a person to accept or reject.
- [remove_link](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/remove-link) — Removes a link between two artefacts after the person confirms; both artefacts stay.
- [restore_revision](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/restore-revision) — Put an earlier version of an artefact back, which writes a new version that names the one restored and announces it.
- [review_quality](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/review-quality) — Asks Heimdall to review one work item, requirement or business rule and keeps the review, with its score, band, summary and findings; spends the team's AI budget.
- [start_brief_import](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/start-brief-import) — Hands a whole brief to Heimdall's reader, so a document pasted into the conversation lands on the review queue as a scaffold of drafts.
- [start_project_research](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/start-project-research) — Sends Heimdall to research a project's domain, so a conversation that opened a project can ask for the industry's expectations without leaving the panel.
- [submit_for_review](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/submit-for-review) — Puts an epic, story, requirement, business rule, use case, baseline or change request up for approval under the record's own submit ability, or resubmits it as the next round when its open request waits for changes.
- [sweep_improvements](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/sweep-improvements) — Runs Heimdall's improvement sweep on a project and answers with how many gaps became cards, how many cards came down and how many wait; calls no model and spends nothing.
- [update_approval_policy](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/update-approval-policy) — Writes a project's approval policy for one kind, after the person confirms; who decides, how many must agree and how long they have.
- [update_baseline](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/update-baseline) — Changes a draft baseline's name, kind, words or records, or moves a frozen baseline to superseded; a frozen baseline's fields and records never change, and the approval engine's moves are refused.
- [update_business_rule](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/update-business-rule) — Changes a business rule in part and moves it where the lifecycle allows by hand; the review states stay with the approvers.
- [update_change_request](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/update-change-request) — Changes a change request's words, records touched or impact while it is not yet decided, or moves it by hand along its lifecycle; the moves through the approval gate are refused.
- [update_decision](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/update-decision) — Changes a decision in part and moves it along its lifecycle when a status is sent; accepting stamps the date decided.
- [update_epic](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/update-epic) — Changes an epic in part and moves it where the lifecycle allows by hand; the review states stay with the approvers.
- [update_raid_item](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/update-raid-item) — Changes a RAID item in part and moves it along its lifecycle when a status is sent.
- [update_requirement](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/update-requirement) — Changes a requirement in part and moves it where the lifecycle allows by hand; the kind is fixed and the review states stay with the approvers.
- [update_use_case](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/planning/update-use-case) — Changes a use case in part, replaces its steps when a list is sent and moves it where the lifecycle allows by hand.
- [create_client](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/project/create-client) — Adds a client to the team's registry, the first record Heimdall writes when a person describes a new client's project in conversation.
- [create_component](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/project/create-component) — Adds one of the applications a project is made of, so Heimdall can lay down the web app and the API of a new project on the house stack.
- [create_design_reference](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/project/create-design-reference) — Adds a link to a design, so the Figma file or the API contract a person pastes into the conversation lands on the record.
- [create_environment](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/project/create-environment) — Adds one place a project runs, so Heimdall can lay down the development, staging, UAT and production rows of a new project.
- [create_project](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/project/create-project) — Creates a project on the team's registry from a name and a paragraph, with the key suggested when none is given, so Heimdall can open a project in conversation.
- [delete_component](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/project/delete-component) — Deletes a component of a project after the person confirms; the environments and repositories under it lose their component.
- [delete_design_reference](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/project/delete-design-reference) — Deletes a design reference of a project after the person confirms; the design itself is untouched.
- [delete_environment](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/project/delete-environment) — Deletes an environment of a project after the person confirms.
- [get_client](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/project/get-client) — Fetch a single client by UUID — its name, contacts, status and notes.
- [get_component](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/project/get-component) — Fetch a single component by UUID — its name, slug, kind, description, tech stack, owner and archive stamp.
- [get_design_reference](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/project/get-design-reference) — One design reference by id, with its address, kind, what it is attached to, version, notes and who added it.
- [get_environment](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/project/get-environment) — Fetch a single environment by UUID — its kind, component, addresses, branch, flags, health, version and freeze, never a secret.
- [get_project_settings](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/project/get-project-settings) — A project's settings by project id, every key present with the workspace default filled in, from sprint length and working days to estimation, workflow flags, business hours and alert routing.
- [get_project](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/project/get-project) — Fetch a single project by UUID — its key, status, methodology, visibility, health, leads and dates.
- [Project Tools](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/project) — A project is one client engagement's record: its key, which prefixes every reference inside it, its status from discovery to maintenance, its methodology, visibility, health and leads.
- [list_clients](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/project/list-clients) — Paginated list of the clients the token's team does projects for, narrowed by status, search words or archived state.
- [list_components](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/project/list-components) — Paginated list of the components a project is made of, with how many environments run each, narrowed by kind, search words or archived state.
- [list_design_references](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/project/list-design-references) — Paginated list of the links a project keeps to its designs, each with its kind, what it is attached to, version and notes, narrowed by kind, component, whole-project scope or search words.
- [list_environments](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/project/list-environments) — Paginated list of a project's environments in promotion order, with their addresses, branch, flags and health, narrowed by kind, component, health or search words.
- [list_projects](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/project/list-projects) — Paginated list of the projects the token can see, narrowed by status, client, search words or archived state.
- [update_client](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/project/update-client) — Changes a client on the team's registry in part, so a contact, a country or a status can be filled in as the conversation reveals it.
- [update_component](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/project/update-component) — Changes a component of a project in part; a field left out keeps its value and the tags replace the list when sent.
- [update_design_reference](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/project/update-design-reference) — Changes a design reference of a project in part.
- [update_environment](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/project/update-environment) — Changes an environment of a project in part; the health and the freeze have their own doors and never change here.
- [update_project_settings](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/project/update-project-settings) — Changes the settings every later module reads, from the sprint length to the council's seats, after the person confirms.
- [update_project](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/project/update-project) — Changes a project's record in part, so a conversation can add the launch date, the leads, the client or a status one answer at a time.
- [Role & Group Tools](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/roles-and-groups) — A role is the permission set one member holds, seeded per team and editable by its owner; a group is a bundle of members with permissions they share.
- [list_groups](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/roles-and-groups/list-groups) — List groups across every team the caller owns or belongs to, with the permissions each group shares and the members in it.
- [list_roles](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/roles-and-groups/list-roles) — List roles across every team the caller owns or belongs to. Each role carries a flat permission list and whether it was seeded.
- [Team Member Tools](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/team-members) — Team members are the staff and guests who collaborate inside a team, each with a role that decides what they may do.
- [list_team_members](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/team-members/list-team-members) — List the people on a team, the owner first, each with the role they hold there. Email addresses only for a token that may view a member.
- [get_team](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/team/get-team) — Fetch a single team by UUID from the caller's visibility set (owned or joined). A foreign team answers RESOURCE_NOT_FOUND.
- [Team Tools](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/team) — A team groups the people, roles and projects of one organisation, and every token is scoped to exactly one.
- [list_teams](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/team/list-teams) — List every team the authenticated person owns or belongs to. Read-only — changing a team stays in the application and the REST API.
- [Token Tools](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/tokens) — Personal access tokens authorise every REST and MCP call, and the plaintext value exists exactly once.
- [list_tokens](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/tokens/list-tokens) — List the authenticated person's own personal access tokens with abilities and scope tuples split out. The plaintext value is never shown.
- [revoke_token](https://alm-docs.labs.zuselab.dev/mcp/v1/tools/tokens/revoke-token) — Revoke one of the authenticated person's own tokens by id. Self-revocation is refused.
- [MCP Troubleshooting](https://alm-docs.labs.zuselab.dev/mcp/v1/troubleshooting) — Common MCP failure modes, from a client that cannot connect to a tool that refuses an ability, and how to resolve each.

## planning

- [Acceptance Criteria](https://alm-docs.labs.zuselab.dev/planning/acceptance-criteria) — The acceptance criteria rows on a work item: one sentence each with an optional Given, When and Then and a kind, written in the item's editor, ordered, versioned with the item and replaced over the API.
- [Approvals](https://alm-docs.labs.zuselab.dev/planning/approvals) — Submit an epic, story, requirement, rule or use case for review, who decides under the project's policy, the inbox, resubmitting after changes, withdrawing, the clocks, and what a client guest signs.
- [Attachments](https://alm-docs.labs.zuselab.dev/planning/attachments) — The Files panel in every artefact flyout: pin wireframes, signed specifications and sample files on epics, stories, requirements, rules, use cases, RAID items, decisions and dictionary entries, read them through the application, and remove them.
- [Backlog](https://alm-docs.labs.zuselab.dev/planning/backlog) — The Backlog page of a project: every story, task, sub-task, bug, spike and improvement with its reference, kind, status, priority, people, estimates and the fields its kind adds, its lifecycle, its hand-over and its versions.
- [Baselines](https://alm-docs.labs.zuselab.dev/planning/baselines) — Compose a baseline from approved records, submit it for the project manager's approval that freezes it, have the client sign a scope baseline, read what it holds, supersede it, and understand the lock a frozen baseline puts on every record it holds.
- [Brief import](https://alm-docs.labs.zuselab.dev/planning/brief-import) — Paste a brief, let Heimdall draft epics, stories, requirements, rules, terms, personas, risks and decisions from it, and accept, edit, merge or reject each suggestion from a review queue; nothing lands until you say so.
- [Business Rules](https://alm-docs.labs.zuselab.dev/planning/business-rules) — The Business Rules page of a project: the decisions of the business the system must honour, each with its kind, statement, condition and action, exceptions, worked examples, authority, priority, dates in force, status and owner, its review lifecycle and its versions.
- [Change Requests](https://alm-docs.labs.zuselab.dev/planning/change-requests) — Raise a change request against a frozen baseline, name the records it touches, write or ask Heimdall for the impact on scope, schedule, effort, cost and risk, convene the council, submit it to the approvers whose agreement unlocks the records named, and see the change through to verified.
- [Comments and mentions](https://alm-docs.labs.zuselab.dev/planning/comments-and-mentions) — The Discussion panel in every artefact flyout: ask and answer in threads, name people with @ to tell them, keep a comment internal, resolve a thread, and follow an artefact to hear of every comment on it.
- [Decisions](https://alm-docs.labs.zuselab.dev/planning/decisions) — The Decisions page of a project: every choice the project made with its kind, context, the options weighed, what was decided, the consequences, who decided and when, the decision it supersedes, the lifecycle from proposed to accepted and the versions.
- [Epics](https://alm-docs.labs.zuselab.dev/planning/epics) — The Epics page of a project: each body of work with its reference, goal, value, measures, owner, MoSCoW priority, status, dates and colour, its lifecycle and its versions.
- [Functional Requirements](https://alm-docs.labs.zuselab.dev/planning/functional-requirements) — The Requirements page of a project: what the system shall do, each requirement with its reference, statement, rationale, source, priority, verification method, status and owner, its review lifecycle and its versions.
- [Planning](https://alm-docs.labs.zuselab.dev/planning) — The pages where a project's scope is written down: epics, the backlog of stories, tasks, bugs and spikes with their acceptance criteria, the functional and non-functional requirements, the business rules, the use cases with their flows, the RAID log, the decisions, the links between them, the comments and the files on each, every save kept as a restorable version, and the approvals that turn a draft into an agreed version; the rest as it lands.
- [Labels](https://alm-docs.labs.zuselab.dev/planning/labels) — A project's own words pinned on its work items: pick labels on an item, filter the backlog by one, and shape the vocabulary from the backlog's label manager with a colour and a meaning for each word.
- [Non-Functional Requirements](https://alm-docs.labs.zuselab.dev/planning/non-functional-requirements) — The qualities a system shall keep: each non-functional requirement with the category it belongs to and the measure that says when it is met, the categories, how to write a target and what reads them.
- [Quality review](https://alm-docs.labs.zuselab.dev/planning/quality-review) — Heimdall reads a story, a requirement or a business rule against INVEST, clear wording, testability, the project's business rules and its siblings, scores it out of 100 and lists what to fix; nothing changes until you do.
- [RAID Log](https://alm-docs.labs.zuselab.dev/planning/raid-log) — The RAID Log page of a project: risks scored by probability and impact with their mitigation and contingency, assumptions, issues and dependencies, each with its area, owner, dates and status, the risk matrix, the lifecycle and the versions.
- [Revisions and Versions](https://alm-docs.labs.zuselab.dev/planning/revisions-and-versions) — Every save of a planning artefact, by a person or by Heimdall, writes a version with its diff, author and reason; read them in the flyout, the API or the tools, and restore any.
- [Traceability](https://alm-docs.labs.zuselab.dev/planning/traceability) — The Links panel in every artefact flyout: join a story to the requirement it implements, a bug to the story that fixes it, a decision to the epic it shapes, read each link from either side and open the other end.
- [Use Cases](https://alm-docs.labs.zuselab.dev/planning/use-cases) — The Use Cases page of a project: how each actor reaches a goal with the system, with the actor, the goal, the trigger, the conditions before and after, the steps of the main flow and the alternate and exception flows that leave it, the review lifecycle and the versions.

## projects

- [Clients](https://alm-docs.labs.zuselab.dev/projects/clients) — The Clients page: the organisations your team does projects for, adding one with its contacts and status, editing it, archiving and restoring it, and why a client with projects is never deleted.
- [Components](https://alm-docs.labs.zuselab.dev/projects/components) — The Components page of a project: the web app, the API, the mobile apps and the services it is made of, each with a slug, a kind, a tech stack and an owner; adding, editing, archiving, restoring and deleting them.
- [Data Dictionary](https://alm-docs.labs.zuselab.dev/projects/data-dictionary) — The Data Entities tab of a project's Dictionary pages: the things the project keeps records of, their fields, owners, personal data, retention and review status.
- [Design References](https://alm-docs.labs.zuselab.dev/projects/design-references) — The Designs page of a project: the links it keeps to Figma files, wireframes, prototypes, screenshots, API contracts and diagrams, attached to the whole project or to one component.
- [Environments](https://alm-docs.labs.zuselab.dev/projects/environments) — The Environments page of a project: development, staging, UAT and production with their addresses, branch and flags; the scheduled health check; freezing changes; and what a client guest sees of it.
- [Glossary](https://alm-docs.labs.zuselab.dev/projects/glossary) — The Glossary tab of a project's Dictionary pages: the words the project agrees on, with definitions, other names, related terms and a review status.
- [Projects](https://alm-docs.labs.zuselab.dev/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](https://alm-docs.labs.zuselab.dev/projects/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.
- [The Project Overview](https://alm-docs.labs.zuselab.dev/projects/overview) — Opening a project from the selector, the registry or a Heimdall button; what the overview shows: the key, status and health, the lifecycle strip, the Heimdall suggests rail, the client, dates, leads, budget, description and recent activity; and what a client guest sees of it.
- [Personas](https://alm-docs.labs.zuselab.dev/projects/personas) — The Personas tab of a project's People pages: the archetypal users the project is built for, with their goals, frustrations, habits, proficiency and devices; adding, editing, archiving, restoring and deleting them.
- [Project Settings](https://alm-docs.labs.zuselab.dev/projects/project-settings) — The Settings page of a project: cadence, estimation, workflow, collaboration and alert knobs with their defaults, plus the danger zone.
- [The Registry](https://alm-docs.labs.zuselab.dev/projects/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.
- [Repositories](https://alm-docs.labs.zuselab.dev/projects/repositories) — The Repositories tab of a project's Code pages: the Git repositories the code lives in, with provider, owner, name, default branch, privacy and component; registering, editing, disconnecting and deleting them.
- [Stakeholders](https://alm-docs.labs.zuselab.dev/projects/stakeholders) — The Stakeholders tab of a project's People pages: the client's sponsor, product owner and approvers, Zuse's own leads and third parties, each with a side, a role, a weight and the approvals that name them; adding, editing and removing them, and what a guest sees.

## reference

- [Changelog](https://alm-docs.labs.zuselab.dev/reference/changelog) — Every change that reached Zuse Bifrost, newest first, dated by the day it landed and linked to the pages of this guide that describe it.
- [Status Reference](https://alm-docs.labs.zuselab.dev/reference/status-reference) — Every status badge the application shows, enum by enum: client and project lifecycle statuses, project health, the review of a glossary term or data entity, design reference kinds, Git providers, epic statuses and priorities, work item kinds, statuses, resolutions, priorities, bug severities and criterion kinds, requirement kinds, categories, verification methods and statuses, business rule kinds, use case flows, RAID kinds, areas and statuses, decision kinds and statuses, baseline kinds and statuses, change reasons, change request statuses and impact levels, document statuses, sprint statuses, link kinds, attachment kinds, quality bands and finding severities, import, research, council sitting, council finding and suggestion statuses, suggestion kinds, revision reasons, webhook delivery states and the states of a Heimdall action.

## webhooks

- [ai.budget_exhausted](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/ai/ai-budget-exhausted) — The month's spend reaches the cap.
- [ai.budget_warning](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/ai/ai-budget-warning) — The month's spend crosses the budget's alert threshold.
- [ai.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/ai) — The team's monthly AI budget approaching and reaching its cap.
- [approval.approved](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/approval/approval-approved) — A request carries.
- [approval.changes_requested](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/approval/approval-changes-requested) — An approver asks for changes.
- [approval.decided](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/approval/approval-decided) — One approver gives a verdict.
- [approval.escalated](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/approval/approval-escalated) — A pending request passes the time the policy allows.
- [approval.policy_updated](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/approval/approval-policy-updated) — A project changes how one kind of approval is decided.
- [approval.rejected](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/approval/approval-rejected) — An approver rejects the request.
- [approval.requested](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/approval/approval-requested) — An artefact is put up for approval.
- [approval.withdrawn](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/approval/approval-withdrawn) — An open request is taken back.
- [approval.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/approval) — The life of an approval request: an artefact put up for approval, each approver's verdict, the outcome the verdicts settle, a request taken back, a request that ran past its time, and a change to how a project decides a kind of approval.
- [attachment.created](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/attachment/attachment-created) — A file is uploaded onto an artefact.
- [attachment.deleted](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/attachment/attachment-deleted) — A file is removed.
- [attachment.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/attachment) — The files pinned on a project's artefacts: a file uploaded and a file removed.
- [baseline.created](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/baseline/baseline-created) — A baseline is added.
- [baseline.deleted](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/baseline/baseline-deleted) — A draft baseline is deleted.
- [baseline.frozen](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/baseline/baseline-frozen) — The team's approval froze a baseline.
- [baseline.restored](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/baseline/baseline-restored) — An earlier version of a draft baseline is put back.
- [baseline.signed_off](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/baseline/baseline-signed-off) — The client signed a scope baseline.
- [baseline.status_changed](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/baseline/baseline-status-changed) — A baseline moves between its states.
- [baseline.updated](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/baseline/baseline-updated) — A draft baseline's words or records change.
- [baseline.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/baseline) — The life of a project's baselines: a baseline added as a draft, its words or items changed, moved by hand, frozen by the team's approval, signed by the client, put back to an earlier version and deleted.
- [business_rule.created](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/business-rule/business-rule-created) — A rule is added.
- [business_rule.deleted](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/business-rule/business-rule-deleted) — A rule is deleted.
- [business_rule.quality_reviewed](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/business-rule/business-rule-quality-reviewed) — A rule's quality is reviewed.
- [business_rule.restored](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/business-rule/business-rule-restored) — An earlier version of a rule is put back.
- [business_rule.status_changed](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/business-rule/business-rule-status-changed) — A rule moves along its review lifecycle.
- [business_rule.updated](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/business-rule/business-rule-updated) — A rule's fields change.
- [business_rule.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/business-rule) — The lifecycle of a project's business rules: a rule added, changed, moved along its review lifecycle, put back to an earlier version and deleted.
- [change_request.analysed](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/change-request/change-request-analysed) — Heimdall read a change request against its baseline.
- [change_request.created](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/change-request/change-request-created) — A change request is raised.
- [change_request.deleted](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/change-request/change-request-deleted) — A change request that was never agreed is deleted.
- [change_request.restored](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/change-request/change-request-restored) — An earlier version of a change request is put back.
- [change_request.status_changed](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/change-request/change-request-status-changed) — A change request moves between its states.
- [change_request.updated](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/change-request/change-request-updated) — A change request's fields change.
- [change_request.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/change-request) — The life of a project's change requests: a request raised, its words or impact changed, moved along its lifecycle by hand or by the approval engine, read by Heimdall for its impact, put back to an earlier version and deleted.
- [client.archived](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/client/client-archived) — A client is archived.
- [client.created](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/client/client-created) — A client is added.
- [client.deleted](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/client/client-deleted) — A client that no project names is deleted.
- [client.restored](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/client/client-restored) — An archived client is restored.
- [client.updated](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/client/client-updated) — A client's fields change.
- [client.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/client) — The lifecycle of a client: creation, edits, archiving, restoring and deletion.
- [comment.created](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/comment/comment-created) — A comment is posted.
- [comment.deleted](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/comment/comment-deleted) — A comment is deleted.
- [comment.reopened](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/comment/comment-reopened) — A resolved thread is marked open again.
- [comment.resolved](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/comment/comment-resolved) — The first comment of a thread is marked resolved.
- [comment.updated](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/comment/comment-updated) — A comment's words are rewritten.
- [comment.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/comment) — The conversations on a project's artefacts: a comment posted, edited, resolved, reopened and deleted.
- [component.archived](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/component/component-archived) — A component is archived.
- [component.created](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/component/component-created) — A component is added.
- [component.deleted](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/component/component-deleted) — A component no environment runs is deleted.
- [component.restored](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/component/component-restored) — An archived component is restored.
- [component.updated](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/component/component-updated) — A component's fields change.
- [component.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/component) — The lifecycle of a project's components: creation, edits, archiving, restoring and deletion.
- [council.convened](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/council/council-convened) — council.convened
- [council.failed](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/council/council-failed) — council.failed
- [council.finding_accepted](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/council/council-finding-accepted) — council.finding_accepted
- [council.finding_dismissed](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/council/council-finding-dismissed) — council.finding_dismissed
- [council.ready](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/council/council-ready) — council.ready
- [council.round_opened](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/council/council-round-opened) — council.round_opened
- [council.voice_spoke](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/council/council-voice-spoke) — council.voice_spoke
- [council.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/council)
- [data_entity.created](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/data-entity/data-entity-created) — An entity is created.
- [data_entity.deleted](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/data-entity/data-entity-deleted) — An entity is deleted.
- [data_entity.fields_changed](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/data-entity/data-entity-fields-changed) — The entity's fields are replaced.
- [data_entity.restored](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/data-entity/data-entity-restored) — An earlier version of a entity is put back.
- [data_entity.status_changed](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/data-entity/data-entity-status-changed) — An entity moves along its review.
- [data_entity.updated](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/data-entity/data-entity-updated) — An entity's fields change.
- [data_entity.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/data-entity) — The lifecycle of a project's data dictionary: an entity created, changed, moved along its review, its fields replaced and the entity deleted.
- [decision.created](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/decision/decision-created) — A decision is added.
- [decision.deleted](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/decision/decision-deleted) — A decision is deleted.
- [decision.restored](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/decision/decision-restored) — An earlier version of a decision is put back.
- [decision.status_changed](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/decision/decision-status-changed) — A decision moves along its lifecycle.
- [decision.updated](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/decision/decision-updated) — A decision's fields change.
- [decision.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/decision) — The lifecycle of a project's decisions: a decision added, changed, moved along its lifecycle, put back to an earlier version and deleted.
- [design_reference.created](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/design-reference/design-reference-created) — A reference is added.
- [design_reference.deleted](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/design-reference/design-reference-deleted) — A reference is deleted.
- [design_reference.updated](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/design-reference/design-reference-updated) — A reference's fields change.
- [design_reference.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/design-reference) — The lifecycle of a project's design references: a link added, changed and removed.
- [environment.created](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/environment/environment-created) — An environment is added.
- [environment.deleted](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/environment/environment-deleted) — An environment is deleted.
- [environment.frozen](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/environment/environment-frozen) — A change freeze starts.
- [environment.health_changed](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/environment/environment-health-changed) — A check finds the environment in a different health than before.
- [environment.unfrozen](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/environment/environment-unfrozen) — A change freeze is lifted before it ends.
- [environment.updated](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/environment/environment-updated) — An environment's fields change.
- [environment.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/environment) — The lifecycle and the state of a project's environments: creation, edits, deletion, change freezes and the health the checks find.
- [epic.created](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/epic/epic-created) — An epic is added.
- [epic.deleted](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/epic/epic-deleted) — An epic is deleted.
- [epic.restored](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/epic/epic-restored) — An earlier version of an epic is put back.
- [epic.status_changed](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/epic/epic-status-changed) — An epic moves along its lifecycle.
- [epic.updated](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/epic/epic-updated) — An epic's fields change.
- [epic.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/epic) — The lifecycle of a project's epics: an epic added, changed, moved along its lifecycle, put back to an earlier version and deleted.
- [glossary_term.created](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/glossary-term/glossary-term-created) — A term is added.
- [glossary_term.deleted](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/glossary-term/glossary-term-deleted) — A term is deleted.
- [glossary_term.restored](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/glossary-term/glossary-term-restored) — An earlier version of a term is put back.
- [glossary_term.status_changed](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/glossary-term/glossary-term-status-changed) — A term moves along its review.
- [glossary_term.updated](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/glossary-term/glossary-term-updated) — A term's fields change.
- [glossary_term.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/glossary-term) — The lifecycle of a project's glossary: a term added, changed, moved along its review and deleted.
- [import.discarded](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/import/import-discarded) — A person dropped the batch.
- [import.failed](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/import/import-failed) — The reading failed.
- [import.ready](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/import/import-ready) — Heimdall read the brief.
- [import.started](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/import/import-started) — A brief is handed to Heimdall.
- [import.suggestion_accepted](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/import/import-suggestion-accepted) — A person accepted a suggestion.
- [import.suggestion_merged](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/import/import-suggestion-merged) — A person merged a suggestion into a record the project already held.
- [import.suggestion_rejected](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/import/import-suggestion-rejected) — A person rejected a suggestion, or dismissed a note.
- [import.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/import) — The life of a brief import: a brief handed to Heimdall, read into suggestions or failed, discarded, and each suggestion accepted, rejected or merged by a person.
- [improvement.swept](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/improvement/improvement-swept) — The sweep ran on a project.
- [improvement.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/improvement) — Heimdall's improvement sweep of a project's record: one event each time it ran, with what it proposed, took down and left waiting.
- [Event Reference](https://alm-docs.labs.zuselab.dev/webhooks/v1/events) — Every outbound webhook event, generated from the OpenAPI document and grouped by family.
- [label.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/label) — A project's label vocabulary: a label added, rewritten and removed.
- [label.created](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/label/label-created) — A word is added to the vocabulary.
- [label.deleted](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/label/label-deleted) — A label is removed.
- [label.updated](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/label/label-updated) — A label's word, colour or note changes.
- [link.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/link) — The links between a project's artefacts: a link made and a link removed.
- [link.created](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/link/link-created) — Two artefacts are linked.
- [link.deleted](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/link/link-deleted) — A link is removed.
- [persona.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/persona) — The lifecycle of a project's personas: creation, edits, archiving, restoring and deletion.
- [persona.archived](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/persona/persona-archived) — A persona is archived.
- [persona.created](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/persona/persona-created) — A persona is added.
- [persona.deleted](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/persona/persona-deleted) — A persona is deleted.
- [persona.restored](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/persona/persona-restored) — An archived persona is restored.
- [persona.updated](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/persona/persona-updated) — A persona's fields change.
- [persona.version_restored](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/persona/persona-version-restored) — An earlier version of a persona is put back.
- [project.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/project) — The lifecycle of a project and its membership: creation, edits, status moves, archiving, restoring, deletion, and people joining or leaving it.
- [project.archived](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/project/project-archived) — A project is archived.
- [project.created](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/project/project-created) — A project is created.
- [project.deleted](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/project/project-deleted) — A project is deleted with everything under it.
- [project.member_added](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/project/project-member-added) — A person gains a membership row on the project.
- [project.member_removed](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/project/project-member-removed) — A person's membership row on the project is removed.
- [project.restored](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/project/project-restored) — An archived project is restored.
- [project.settings_changed](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/project/project-settings-changed) — One or more of the project's settings change.
- [project.status_changed](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/project/project-status-changed) — A project moves between lifecycle statuses.
- [project.updated](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/project/project-updated) — A project's own fields change.
- [raid_item.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/raid-item) — The lifecycle of a project's RAID log: a risk, an assumption, an issue or a dependency raised, changed, moved along its lifecycle, put back to an earlier version and deleted.
- [raid_item.created](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/raid-item/raid-item-created) — An item is raised.
- [raid_item.deleted](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/raid-item/raid-item-deleted) — An item is deleted.
- [raid_item.restored](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/raid-item/raid-item-restored) — An earlier version of an item is put back.
- [raid_item.status_changed](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/raid-item/raid-item-status-changed) — An item moves along its lifecycle.
- [raid_item.updated](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/raid-item/raid-item-updated) — An item's fields change.
- [repository.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/repository) — The lifecycle of a project's repositories: registration, edits, disconnecting, reconnecting and deletion.
- [repository.created](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/repository/repository-created) — A repository is registered.
- [repository.deleted](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/repository/repository-deleted) — A repository is deleted.
- [repository.disconnected](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/repository/repository-disconnected) — A repository is set aside.
- [repository.reconnected](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/repository/repository-reconnected) — A disconnected repository is brought back.
- [repository.updated](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/repository/repository-updated) — A repository's fields change.
- [requirement.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/requirement) — The lifecycle of a project's requirements: a functional or non-functional requirement added, changed, moved along its review lifecycle, put back to an earlier version and deleted.
- [requirement.created](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/requirement/requirement-created) — A requirement is added.
- [requirement.deleted](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/requirement/requirement-deleted) — A requirement is deleted.
- [requirement.quality_reviewed](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/requirement/requirement-quality-reviewed) — A requirement's quality is reviewed.
- [requirement.restored](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/requirement/requirement-restored) — An earlier version of a requirement is put back.
- [requirement.status_changed](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/requirement/requirement-status-changed) — A requirement moves along its review lifecycle.
- [requirement.updated](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/requirement/requirement-updated) — A requirement's fields change.
- [research.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/research) — The life of a research run: Heimdall asked to read a project's domain, done with notes and suggestions, or failed.
- [research.failed](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/research/research-failed) — The run failed.
- [research.ready](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/research/research-ready) — Heimdall finished the research.
- [research.started](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/research/research-started) — A person asks Heimdall to research the project.
- [role.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/role) — Role creation, edits and deletion.
- [role.created](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/role/role-created) — A role is created.
- [role.deleted](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/role/role-deleted) — A custom role is deleted.
- [role.updated](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/role/role-updated) — A role's name, description or permissions change.
- [stakeholder.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/stakeholder) — The lifecycle of a project's stakeholders: who was added to the record, what changed about them and who was removed.
- [stakeholder.created](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/stakeholder/stakeholder-created) — A stakeholder is added.
- [stakeholder.deleted](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/stakeholder/stakeholder-deleted) — A stakeholder is removed.
- [stakeholder.restored](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/stakeholder/stakeholder-restored) — An earlier version of a stakeholder is put back.
- [stakeholder.updated](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/stakeholder/stakeholder-updated) — A stakeholder's fields change.
- [team.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/team) — Team creation, rename and deletion, and the comings and goings of the people in it.
- [team.created](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/team/team-created) — A team is created.
- [team.deleted](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/team/team-deleted) — A team with no projects is deleted.
- [team.member_invited](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/team/team-member-invited) — An invitation is sent to a staff member or a client guest.
- [team.member_joined](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/team/team-member-joined) — An invitee accepts and becomes a member.
- [team.member_removed](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/team/team-member-removed) — A member is removed from the team.
- [team.member_role_changed](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/team/team-member-role-changed) — A member moves to another of the team's roles.
- [team.updated](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/team/team-updated) — A team is renamed.
- [token.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/token) — Personal access token minting and revocation.
- [token.created](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/token/token-created) — A token is minted.
- [token.revoked](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/token/token-revoked) — A token is revoked.
- [use_case.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/use-case) — The lifecycle of a project's use cases: a use case added, changed, moved along its review lifecycle, given new steps, put back to an earlier version and deleted.
- [use_case.created](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/use-case/use-case-created) — A use case is added.
- [use_case.deleted](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/use-case/use-case-deleted) — A use case is deleted.
- [use_case.restored](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/use-case/use-case-restored) — An earlier version of a use case is put back.
- [use_case.status_changed](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/use-case/use-case-status-changed) — A use case moves along its review lifecycle.
- [use_case.steps_changed](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/use-case/use-case-steps-changed) — A use case's steps are replaced.
- [use_case.updated](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/use-case/use-case-updated) — A use case's fields change.
- [work_item.* events](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/work-item) — The lifecycle of a project's work items: a story, task, sub-task, bug, spike or improvement added, changed, moved along its lifecycle, handed to a person, given new acceptance criteria, put back to an earlier version and deleted.
- [work_item.assigned](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/work-item/work-item-assigned) — An item is handed to a person, or to nobody.
- [work_item.created](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/work-item/work-item-created) — An item is added.
- [work_item.criteria_changed](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/work-item/work-item-criteria-changed) — An item's acceptance criteria are replaced.
- [work_item.deleted](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/work-item/work-item-deleted) — An item is deleted.
- [work_item.quality_reviewed](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/work-item/work-item-quality-reviewed) — An item's quality is reviewed.
- [work_item.restored](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/work-item/work-item-restored) — An earlier version of an item is put back.
- [work_item.transitioned](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/work-item/work-item-transitioned) — An item moves along its lifecycle.
- [work_item.updated](https://alm-docs.labs.zuselab.dev/webhooks/v1/events/work-item/work-item-updated) — An item's fields change.
- [Webhooks & Events](https://alm-docs.labs.zuselab.dev/webhooks/v1) — Event-driven HTTPS notifications from Zuse Bifrost to your server, CI or anything that takes JSON over POST, with retries and replay.
- [Webhooks Quickstart](https://alm-docs.labs.zuselab.dev/webhooks/v1/quickstart) — Register a target, subscribe to an event, receive a signed payload, verify it and respond 200, end to end.
- [Retries & Delivery](https://alm-docs.labs.zuselab.dev/webhooks/v1/retries-and-delivery) — The exponential back-off schedule, dead-lettering, the auto-disable threshold and how to replay a failed delivery.
- [Webhook Security](https://alm-docs.labs.zuselab.dev/webhooks/v1/security) — Secret rotation, replay windows, the IP allow-list and what to trust on an inbound delivery, so nothing can spoof or replay a Zuse Bifrost event.
- [Signature Verification](https://alm-docs.labs.zuselab.dev/webhooks/v1/signature-verification) — HMAC-SHA256 verification of every delivery's ZG-Signature header, in a Stripe-compatible scheme, and how a rotation replaces the secret.
- [Testing & Debugging Webhooks](https://alm-docs.labs.zuselab.dev/webhooks/v1/testing-and-debugging) — Fire a test payload, read the delivery log and retry a failed delivery by hand, without waiting for the production trigger.

## workspace

- [Ability Reference](https://alm-docs.labs.zuselab.dev/workspace/abilities) — The complete list of permissions a role or a group can grant, what each entity covers, and a plain sentence on what a member holding each permission can do.
- [Activity Log](https://alm-docs.labs.zuselab.dev/workspace/activity-log) — Read every change recorded in your team, see who made it and whether it came from a person, a token, an agent, an integration or the system, and open an item's full history with its field-by-field changes.
- [AI Settings](https://alm-docs.labs.zuselab.dev/workspace/ai-settings) — Read where the team's AI budget stands this month, set the cap and the warning line, read the statement per feature and model and the latest calls, and see which model each job runs on.
- [API Tokens](https://alm-docs.labs.zuselab.dev/workspace/api-tokens) — Mint a personal access token for the REST API, the MCP server or a pipeline, scope it to a team and optionally one project, tick its abilities, and revoke it.
- [Groups](https://alm-docs.labs.zuselab.dev/workspace/groups) — Grant a set of permissions to several members at once, on top of their roles, and keep the group's membership in step with the team.
- [Your Workspace](https://alm-docs.labs.zuselab.dev/workspace) — How a workspace is organised: teams that own projects, the people in them, the roles that say what each person may do, and groups that grant more.
- [Members and Guests](https://alm-docs.labs.zuselab.dev/workspace/members-and-guests) — Invite a colleague with a role or a client as a guest of one project, change a member's role, remove someone, and manage the invitations still waiting.
- [Roles](https://alm-docs.labs.zuselab.dev/workspace/roles) — The eight default roles every team starts with, how to create and edit custom roles, the permission catalogue, and the rules on deleting a role.
- [Teams](https://alm-docs.labs.zuselab.dev/workspace/teams) — Create a team, make one of yours current, open its members, and rename or delete the teams you own, with what each action changes.
- [Webhooks](https://alm-docs.labs.zuselab.dev/workspace/webhooks) — Register an endpoint that receives signed event payloads, pick its events, rotate its secret, pause or test it, and read and replay the delivery log.