Skip to content

Evenfire is an intelligence layer platform for running LLM agents that take real actions, on your infrastructure

TypeScript

docs: update docs for team delete conflicts

Jose Gabriel Ramirez Encinas4677758a41ed
diff --git a/control-api/README.md b/control-api/README.md
index 6ed517766..8163fc20b 100644
--- a/control-api/README.md
+++ b/control-api/README.md
@@ -148,7 +148,7 @@ Admin sessions are signed as RS256 JWTs with audience `control-ui`. UI-facing ro
- `DELETE /api/v1/admin/users/:userId` — hard-deletes the user row (profiles, personal context/agent links, and their `team_members` rows CASCADE). Teams are retained even if this leaves them with zero members. User-linked audit/history rows keep their event data but set the deleted user reference to `NULL`. **Destructive and irreversible** for that user id.
- `GET /api/v1/admin/teams`
- `POST /api/v1/admin/teams` — creates a team shell without assigning initial members
-- `DELETE /api/v1/admin/teams/:teamId` — hard-deletes the team (memberships, invitations, team context/agent links CASCADE). **Destructive and irreversible** for that team id.
+- `DELETE /api/v1/admin/teams/:teamId` — hard-deletes an empty team (invitations, inactive memberships, team context/agent links CASCADE). Active members block deletion (`409 team_not_empty`); a team referenced by workflow audit history is kept (`409 team_has_audit_history`). **Destructive and irreversible** for that team id.
- `PUT /api/v1/admin/teams/:teamId/name`
- `GET /api/v1/admin/teams/:teamId/members`
- `PATCH /api/v1/admin/teams/:teamId/members/:userId/role`
diff --git a/control-api/package-lock.json b/control-api/package-lock.json
index 1b6d7666c..355691863 100644
--- a/control-api/package-lock.json
+++ b/control-api/package-lock.json
@@ -1,12 +1,12 @@
{
"name": "clerum-control-api",
- "version": "0.1.752",
+ "version": "0.1.753",
"lockfileVersion": 3,
"requires": true,
"packages": {
"": {
"name": "clerum-control-api",
- "version": "0.1.752",
+ "version": "0.1.753",
"dependencies": {
"@clerum/display-field": "file:../packages/display-field",
"@clerum/grok-provider-attempt-contract": "file:../packages/grok-provider-attempt-contract",
diff --git a/control-api/package.json b/control-api/package.json
index f24fe4a2f..510f8b82b 100644
--- a/control-api/package.json
+++ b/control-api/package.json
@@ -1,6 +1,6 @@
{
"name": "clerum-control-api",
- "version": "0.1.752",
+ "version": "0.1.753",
"description": "Internal Clerum control plane REST API + UI for managing CRDs and secrets",
"main": "dist/main.js",
"engines": {
diff --git a/docs/how-to/manage-users-and-teams.md b/docs/how-to/manage-users-and-teams.md
index 37685d028..640932a40 100644
--- a/docs/how-to/manage-users-and-teams.md
+++ b/docs/how-to/manage-users-and-teams.md
@@ -180,8 +180,9 @@ There is no "deactivate" for members. The options are:
accounts are disabled either way.
- **Delete a team** (Teams tab → **Delete**). The API only deletes a team with
no active members, and returns `team_not_empty` otherwise. Remove or delete
- its members first. Deleting the team also removes its pending invitations
- and its agent and Context grants.
+ its members first. A team referenced by workflow audit history is kept, and
+ the API returns `team_has_audit_history`. Deleting the team also removes its
+ pending invitations and its agent and Context grants.
- **Delete admin** (Admins tab). This removes the admin's Control UI access
immediately: their sessions end and their EvenDrive operator link is
revoked. The record is kept as `disabled` for audit and is hidden from the