Delete a Site Admin in GpsGate. Step by step guide

Unused or excessive admin accounts are one of the easiest routes for attackers or accidental damage. Removing former employees or admins enforces the principle of least privilege (give people only the access they need), reduces lateral movement risk if an account is compromised, and keeps audit trails accurate. Treat account removal as part of normal access lifecycle management: identify, reassign, revoke, delete, and log the change.

Quick difference: regular admin vs site admin 

• Site Admin (server level) 
  Site Admin users have privileges across the server and can manage Site Admin settings and roles. Deleting a person from Site Admin removes them from the Site Admin application only.  These users are found under Main Menu > Site Admin > Users > Site Admin Users.
• Application admin (application level) 
  These are admin users inside a specific application (for example Fleet, Reporting, or any custom application). Application admins are managed via the Manage Users panel and can keep working even if the person was removed from Site Admin. You must remove application admin roles explicitly if you want to fully revoke admin access.  

Step-by-step procedure 

Follow these steps in order. 
1. Go to Main Menu > Site Admin > Users > Site Admin Users to see Site Admin accounts. Use Site Admin User Search if you have many users. 

2) See the Site Admin role(s) the user has

Hover the user row and click Edit to open their Site Admin profile. The edit view shows which Site Admin roles (for example _Administrator) they have assigned. 

3) Check every application where this user has admin access

A user can be a Site Admin and also be assigned as an admin inside one or more applications. Make a list of all applications where the user has admin privileges. This is essential because deleting from Site Admin does not automatically remove app-level roles.

4) Edit the user (prepare removal)

Before changing anything, document current role assignments and make a copy of any custom role you plan to modify (recommended best practice when changing roles). This makes rollback easier. 

5) Unselect the applications and remove application admin roles (important)

For each application where the user is an admin, remove them from any admin roles or unselect the application membership that grants admin privileges. This is done by unchecking application assignment boxes or removing the user from the role. (If you skip this, the person may continue to exist as an admin inside that application after Step 7.)  

6) Extra checks before deletion 

Do these checks to make sure the account is truly revoked, and you can post the change to your records. Reassign or remove any assets owned by that user so nothing is orphaned (trackers, rules, schedules). Add an audit comment or ticket note with user id, who removed them, and the timestamp.

7) Delete the user and confirm

In Main Menu > Site Admin > Users > Site Admin Users, hover the user row and click Delete. Confirm the delete modal. Deleting here removes the person from the Site Admin application.  After deletion, verify: (a) The user no longer appears in Site Admin Users. (b) The user no longer appears in any application’s Manage Users lists. If they still do, repeat Step 5 in that application. (c) Check audit logs or User Actions to confirm the deletion entry exists and record it in your change log. 

Final notes 

Make user deletion part of your standard offboarding checklist and log each removal with an audit entry. Set up regular reviews of privileged accounts (every quarter is a good period) so inactive admins don’t linger unnoticed. And when updating custom roles, duplicate them first - that way you have a clean rollback option if something goes wrong.