docs: update Config tab navigation behavior and role gating
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -257,12 +257,14 @@ The UI enforces role-based visibility (backend ACLs remain the authoritative che
|
||||
| UI element | VIEWER | OPERATOR | ADMIN |
|
||||
|-----------|--------|----------|-------|
|
||||
| Exchanges, Dashboard, Runtime, Logs | Yes | Yes | Yes |
|
||||
| Config tab (per-app) | Read-only | Edit | Edit |
|
||||
| Config tab | Read-only | Edit | Edit |
|
||||
| Route control bar | Hidden | Yes | Yes |
|
||||
| Diagram node toolbar | Hidden | Yes | Yes |
|
||||
| Admin sidebar section | Hidden | Hidden | Yes |
|
||||
| Admin pages (`/admin/*`) | Redirect to `/` | Redirect to `/` | Yes |
|
||||
|
||||
Config tab is a main tab alongside Exchanges/Dashboard/Runtime/Logs. Navigation: `/config` shows all-app config table; `/config/:appId` filters to that app with detail panel open. Sidebar clicks while on Config stay on the config tab — route clicks resolve to the parent app's config (config is per-app).
|
||||
|
||||
### Ed25519 Config Signing
|
||||
|
||||
Server derives an Ed25519 keypair deterministically from the JWT secret. Public key is shared with agents at registration. Config-update payloads are signed so agents can verify authenticity.
|
||||
|
||||
Reference in New Issue
Block a user