hermes - 💡(How to fix) Fix feat(admin): add ability to change user role (admin ↔ agent) [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#16848Fetched 2026-04-29 06:38:31
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
labeled ×4
RAW_BUFFERClick to expand / collapse

Problem: There is no way to change a user's role after creation. The Admin → User Management UI only offers: Create, Deactivate, Reset Password. No "Change Role" button or API endpoint.

Impact: If a user is created with the wrong role (e.g., admin instead of agent), the only fix is to delete and recreate the account — losing any data associated with that user.

Required:

  1. API endpoint: PUT /api/admin/users/{id}/role — accepts {"role": "admin" | "agent"}
  2. UI button: Add "Change Role" to the Actions column in User Management table, opens a modal with a role dropdown
  3. Validation: Admin should not be able to demote themselves to agent (prevent lockout)

extent analysis

TL;DR

Implementing a PUT /api/admin/users/{id}/role API endpoint and adding a "Change Role" button to the User Management UI will allow administrators to change a user's role after creation.

Guidance

  • Create a new API endpoint PUT /api/admin/users/{id}/role that accepts a JSON body with a role property, which can be either "admin" or "agent".
  • Add a "Change Role" button to the Actions column in the User Management table, which opens a modal with a role dropdown menu.
  • Implement validation to prevent an admin from demoting themselves to an agent, to avoid lockout.
  • Ensure the API endpoint and UI button are properly secured with authentication and authorization checks.

Example

// Example API request body
{
  "role": "agent"
}

Notes

The implementation details of the API endpoint and UI button may vary depending on the specific technology stack and framework being used. Additionally, proper error handling and validation should be implemented to ensure the security and integrity of the system.

Recommendation

Apply workaround by implementing the required API endpoint and UI changes, as this will provide a direct solution to the problem and allow administrators to change a user's role after creation.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING