Skip to main content

Deactivate a user

  • Updated

Who can use this feature?

System & User administrators only

 

As an administrator, you can revoke a user's access to your organisation's Qwil services by deactivating their account. This action is permanent and should not be used to reset an account. 

 

What to expect?

When you deactivate a user:

  • They will no longer have access to your organisation on Qwil, and they will not be able to see or download any data, this includes chats, attachments, contacts, etc.
  • They are removed from all their chats and will appear as former participants.
  • They will no longer appear in contact lists of other users.
  • The email linked to the profile will remain (you can't create a new user with the same email again unless you change it on the de-activated user first to Deactivated1@XXX.com for example)

Note: After deactivating a user, you cannot restore their account.

 

To deactivate a user:

Note:If the user has forgotten their log in details, needs to change their account mobile or email, or you have made a mistake on the invitation, DO NOT deactivate the client. These problems can be resolved by following the linked guides.

  1. From your desktop, click on the admin menu.
  2. Click on Staff or Clients.
  3. Locate the user you wish to deactivate.
  4. On the user page, you will see More Actions on the top-right. Click on it.
  5. In the dropdown menu click on Delete user.

  6. A confirmation modal will open. Read the warnings and type "CONFIRM" and then click Deactivate.

You can also deactivate a user directly from the user list by clicking on the three-button menu and selecting Deactivate user.

 

To see your inactive users, go to the Staff or Client menu and select Inactive in the filter options.

 

Things to consider:

In order to maintain your client relationships, you will not be able to deactivate a staff user if they are the only active staff member in a client team that contains clients. If this is the case, you will need to add another staff user to the client team and then try again.

Related articles