Deactivate / Restore an employee account

You can deactivate an account if an employee leaves your clinic.

This will allow you to release a license that is assigned to a new employee or replacement during a long absence.

Note that deactivating, activating, or inviting a new user incurs no additional cost as long as you are using the active licenses in your contract. If you no longer have a license to invite a new employee, please send the request to support@medexa.com.

Here are some contexts where you can deactivate a user:

  • An employee leaves the clinic
  • Maternity leave
  • Sick days
  • Sabbatical year
  • Vacation
  • End of the internship
  • End of contract
  • Others

Note that disabling an employee in the system does not delete any data created by that employee. Patient records, appointments, chart notes, information sent, etc. will remain in the system and remain associated with that employee, in accordance with college regulations.

If an employee returns to the clinic after an absence, you only have to activate the employee, and he will keep the same identifiers and parameters. You may need to re-register the employee at different service locations where the employee works and reassign the services. Please refer to the steps in the following Inviting a New User article to ensure the employee's account settings are set up correctly.

DEACTIVATE AN EMPLOYEE ACCOUNT

  1. Go to My Clinic
  2. Click on User Management
  3. Click on the employee whose account you need to deactivate
  4. Click on the button Deactivate in red

REACTIVATE AN EMPLOYEE ACCOUNT

  1. Go to My Clinic
  2. Click on User management
  3. Go to the Inactive section at the top right
  4. Click on the name of the employee whose account you need to restore
  5. Click on the Reactivate button in yellow (Make sure you have a Full-Time or Part-Time license available to perform the reactivation, otherwise add from the "Subscription" tab located in My clinic or contact support at support@medexa.com)

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.