Deactivate a User in your Organisation

A User's access to your Organisation is removed by deactivating them. This is done from within their Staff (or Friend) Profile, which you'll find under People in the top menu bar. If the user has Manage User clearance or above and receives notifications, make sure you update your organisation profile under Our Organisation as well. See the link to How to Update Organisation Details below. 


1. Go to the Staff (or Friend ) Profile you want to deactivate 

If you need help to find the User read this article:  Find a User in your Organisation

2. Deactivate the User

From the Staff/ Friend Profile screen

  1. Click the Options menu.
  2. Click Deactivate.

This removes their access to your Organisation, including the Web application and the Mobile App. You will see (inactive) in red beside the Users name and they will then be found in your inactive list.


More about Deactivating Users 

  • Users are deactivated rather than deleted because they have records associated with them in PeopleSafe eg  in stories or training, it's important to keep those records as part of your data.
  • When a User is deactivated, they're moved to the Inactive List in your Organisation. This means any of the records they were a part of, are retained. 
  • Deactivating a Staff Profile will not delete any existing tasks assigned to the user. These need to be removed manually. 
  • Deactivating a Staff Profile will not prevent the person from receiving notifications if their email or cellphone number has been added either to the "E-mail Serious Stories to" field or "TXT Serious Stories to" field on your Our Organisation screen. .
  • If the person you are deactivating is the Main Contact person listed in your Organisation Profile you will need to go in and update the details with your new Main Contact. For Help : Update Organisation Details
  • If you want to re-activate a person's profile see Restore a User's Access in Related Articles.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.