How to Remove / Deactivate User in Procella

To remove Procella portal access for a specific user, the User's account has to be deactivated.

There are two options to deactivate the User

  1. Deactivate Effective Immediately
  2. Schedule Deactivation on Specific Date/Time

Scheduled Deactivation is useful when an Employee's last working day is known.

  • To deactivate a User, Navigate to Administration -> Access Management -> Users

  • Click on the Ellipsis icon against the user who should be deactivated. Choose the Inactive User option


  • A confirmation pop-up will show up.
  • You will have the option to select a specific date and time. Please note that the date and time you select will serve as the effective deactivation time, after which the user will no longer be able to log into the Procella platform.

  • Once the date is selected, click on the time to select deactivation time. After selecting time, Click on Yes button to set the deactivation date/time.

  • It's important to be aware that the date/time displayed in the pop-up is Eastern Time. Please ensure that you take this time zone into consideration when setting the deactivation time for the user.
  • The deactivation date/ time, also referred to as the termination date and time, will be prominently displayed on the 'Edit User' screen.

Note:

  • Once the Termination date/time has been set for a user, it CANNOT be undone. If it is required to undo, please contact support.
  • When a user is inactivated, The user's access to the Procella platform is revoked.
  • (Say) User A has access to PBM 1, PBM 2, and PBM 3. When the user is deactivated, the complete access is revoked. It is NOT based on the PBM
  • If the User's access needs to be removed from a particular PBM in the platform (say you need to remove User A from PBM 3). Contact support
  • User deactivation ONLY revokes access to the Procella platform. If the user has access to AWS for accessing reports. Please contact support to revoke the VPN / AWS access
  • When a deactivated user tries to log in, this is the error message they will see in the login page







Did this solve your problem?