Cannot remove own technician profile or fix Permission Denied in Hexnode portalSolved

Participant
Discussion
3 months ago Apr 30, 2026

Hi everyone. I’m managing technicians in our Hexnode portal and ran into a few confusing things. First, I tried to remove my own technician account but couldn’t find a way to do it. Second, I removed and re-added another technician with a scope, but the dashboard still showed the old technician count for a while. Finally, the newly added technician is now seeing a “Permission Denied” message when trying to access the portal.

What is the correct way to handle these issues?

Replies (1)

Marked SolutionPending Review
Hexnode Expert
3 months ago Apr 30, 2026
Marked SolutionPending Review

Hello,

Thanks for reaching out to Hexnode Connect.

Let’s break down each of these behaviors and how to resolve them:

1. Removing your own technician profile:

In Hexnode, a technician cannot delete their own profile from the portal. This action must always be performed by another technician with sufficient privileges, such as an Admin or Super Admin.

2. Dashboard technician count delay:

The dashboard widget refreshes based on a periodic sync cycle, meaning the number shown can temporarily lag behind the actual data after you add or remove technicians. If you need to check the real-time active technician count, you should always rely on Admin > Technicians and Roles > Technician.

3. “Permission Denied” errors:

This message usually indicates that the newly added technician does not have an active role assigned, or their assigned scope is blocking access to the required resources. To fix this:

  1. Navigate to Admin > Technicians and Roles.
  2. Open the affected technician’s profile.
  3. Verify that they have an active role assigned.
  4. Ensure that the role includes the necessary read/write permissions.
  5. Confirm that the correct scope is applied so they are not blocked from the portal sections they need to access.

Once the role and scope are properly configured, the technician should be able to access the portal without encountering the error.

I hope this helps clear things up! Feel free to reach out if you have any more doubts or need further assistance.

Best regards,
George,
Hexnode UEM

Save