NOTE: WHEN DISABLING A USER, ALWAYS DO SO FROM THE USER RECORD, NEVER FROM THE REP RECORD. EVEN THOUGH UNPUBLISHING A REP RECORD WILL AUTOMATICALLY DISABLE A USER IF THE CORRECT CONFIGURATIONS ARE SET, IF A USER IS DISABLED VIA UNPUBLISHING THEIR REP RECORD IN THIS WAY, THE HIERARCHY WILL NOT ADJUST CORRECTLY. 

1. Login to Backend FastGem (ADMIN). You can reach the backend of your instance by adding /a to the end of your instance address. For example, the backend address of our demo instance is demo.fastgem.net/a
2. Click on 'Users' up top. Then, click on 'Manage' Wait for page to load. 
   
3. Click the square to the left of the rep whose FastGem you need to deactivate. Then, click 'Block' up top. 
   

 

Blocked/Deactivated Users are automatically unpublished as well, so their names no longer appear for selection in front end FastGem. FastGem support can turn the automatic unpublishing/publishing feature off for your instance if you wish. 

If you want your reps' reporting hierarchy to be automatically adjusted when a rep is disabled, so that any reps under the disabled user are automatically re-assigned under the next user in the hierarchy chain, let FastGem support know, and we can turn that feature on for your instance as well. Keep in mind that if this feature is enabled, then when you RE-enable a rep, the reps who were previously assigned under them will not be under them anymore.