Employees who are permanently deactivated can be re-enabled if they were not disabled by certification.
To re-enable an employee
-
In the Manager, select the Employees | Inactive employees category.
-
Select the employee in the result list.
- Select the Re-enable employee task.
-
Confirm the security prompt with Yes if the employee should be enabled.
On the master data form for the employee, the Disabled permanently option is not set. The end date and last working day are deleted assuming the dates are past.
- Save the changes.
Related topics
When an employee is deleted, they are tested to see if user accounts and company resources are still assigned, or if there are still pending requests in the IT Shop. The employee is marked for deletion and therefore locked out of further processing. Before an employee can finally be deleted from the One Identity Manager database, you need to delete all company resource assignments and close all requests. You can do this manually or implement custom processes to do it. All the user accounts linked to one employee could be deleted by default by One Identity Manager once this employee has been deleted. If no more company resources are assigned, the employee is finally deleted.
By default, employees are finally deleted from the database after 30 days. During this period it is possible to re-enable the employee. A restore is not possible once deferred deletion has expired. In the Designer, you can set an alternative delay on the Person table.
Related topics
A procedure called QER_PPersonDelete_GDPR is provided to support the special process for deleting employee related data, which implements the General Data Protection Regulation (GDPR) of the European Union. You can use this procedure to delete all data relating to an employee from the One Identity Manager database. For certain dependencies, processes that are handled by the One Identity Manager Service are created by the procedure.
NOTE: During execution of this procedure, the database does not allow any triggers. Therefore, it is recommended to only run the procedure in maintenance periods.
You can execute the procedure in any program suitable for running SQL queries.
Calling syntax:
exec QER_PPersonDelete_GDPR ' <employee UID from the Person table, UID_Person column>'
provides you with support for creating complex password policies, for example, for system user passwords, the employees' central password as well as passwords for individual target systems. Password polices apply not only when the user enters a password but also when random passwords are generated.
Predefined password policies are supplied with the default installation that you can use or customize if required. You can also define your own password policies.
Detailed information about this topic