Skip to content

armgit / Pulse

Public Imported from GitHub
0

Real-time monitoring dashboard for Proxmox VE, PBS, Docker, Kubernetes, TrueNAS and vSphere. Self-hosted, with alerts for failed backups, full disks, unhealthy containers and offline nodes.

Keep User Access request notes with their owning lifecycle

pulse-triage[bot]584aeb130617
diff --git a/docs/release-control/v6/internal/subsystems/api-contracts.md b/docs/release-control/v6/internal/subsystems/api-contracts.md
index 6a999add39..287828b909 100644
--- a/docs/release-control/v6/internal/subsystems/api-contracts.md
+++ b/docs/release-control/v6/internal/subsystems/api-contracts.md
@@ -13578,14 +13578,3 @@ earlier raw object; that current-read object remains usable for the same live
ID. A later full read, context withdrawal or deletion invalidates the old
confirmation. The registered sequential scope-edit/revoke consumer regression
and earlier-read rejection test cover both sides without ID-only admission.
-
-### User Access requests retain their confirmed context
-
-RBAC directory/role reads, saved-permission reads and user assignment/removal
-operations accept client-only `RBACAdminRequestOptions`. User Access supplies an
-abort signal, exact expected organisation and `retry: false` to the canonical
-API client, including its CSRF preparation boundary. A withdrawn confirmation
-must not dispatch into the default or a new organisation or automatically replay
-a refusal. Endpoint paths, encoded principal keys, JSON payloads, authentication
-and server permission checks are unchanged. `api/__tests__/rbac.test.ts` and
-`UserAccessReaderLifetime.test.tsx` pin forwarding and the consuming lifecycle.
diff --git a/docs/release-control/v6/internal/subsystems/organization-settings.md b/docs/release-control/v6/internal/subsystems/organization-settings.md
index d39ad77a7d..b995793db4 100644
--- a/docs/release-control/v6/internal/subsystems/organization-settings.md
+++ b/docs/release-control/v6/internal/subsystems/organization-settings.md
@@ -548,3 +548,14 @@ principals must not survive an organisation switch in an old notification.
Paired directory/role reads are aborted when their combined read settles so a
failed sibling does not leave an unowned pending request. The registered
reader-lifetime/paywall tests and actual App browser witness cover this bound.
+
+### User Access requests retain their confirmed context
+
+RBAC directory/role reads, saved-permission reads and user assignment/removal
+operations accept client-only `RBACAdminRequestOptions`. User Access supplies an
+abort signal, exact expected organisation and `retry: false` to the canonical
+API client, including its CSRF preparation boundary. A withdrawn confirmation
+must not dispatch into the default or a new organisation or automatically replay
+a refusal. Endpoint paths, encoded principal keys, JSON payloads, authentication
+and server permission checks are unchanged. `api/__tests__/rbac.test.ts` and
+`UserAccessReaderLifetime.test.tsx` pin forwarding and the consuming lifecycle.