Introduction

Zluri’s Zero Touch Offboarding is a streamlined process designed to automate the offboarding of employees seamlessly, eliminating the need for manual intervention. This is achieved by leveraging third-party integrations with popular HR platforms such as BambooHR, Hibob, PersonioHR, and Freshteam.

Key Features

Integration with Third-Party HR Platforms

Zluri integrates effortlessly with leading HR platforms:

• BambooHR

• HiBob

• PersonioHR

• Freshteam

This integration allows Zluri to directly retrieve essential employee information, including termination dates and other relevant details.

Automated Offboarding Rules

The Zero Touch Offboarding process operates on a set of automated rules and triggers configured within the Zluri platform. These rules are activated by events such as updates to an employee's termination date in the HR platform, prompting Zluri to initiate predefined actions to facilitate offboarding.

Customizable Actions

Organizations can tailor the actions performed during the offboarding process to meet their specific needs. Possible actions include:

• Sending offboarding emails

• Assigning tasks to team members

• De-provisioning access to necessary tools and resources

Efficient Data Retrieval

Zero Touch Offboarding ensures the efficient retrieval of employee data from the HR platform. It periodically updates information, allowing organizations to remain current with employee changes and seamlessly incorporate them into the offboarding workflow.

User-Friendly Interface

Zluri features a user-friendly interface for configuring offboarding rules and monitoring the process. Administrators can easily set up and manage automation rules, track progress, and generate reports to gain insights into the efficiency of the offboarding workflow.

Benefits

• Time and Cost Savings: Automating repetitive tasks reduces the time and costs associated with the employee offboarding process.

• Improved Offboarding Experience: The automated nature guarantees a seamless and consistent offboarding experience for IT teams, HR teams, and Application Admins.

• Enhanced Compliance and Security: Helps organizations maintain compliance with regulatory requirements and internal policies.

• Scalability and Flexibility: Highly scalable and adaptable to organizations of all sizes and industries.

How-to

This section provides detailed instructions on setting up and configuring Zluri’s Zero Touch Offboarding for your organization.

Prerequisites

Before setting up Zero Touch Offboarding, ensure you have:

• Access to the admin or appropriate permissions in the third-party application (e.g., BambooHR).

• Access to Zluri's automation rules section.

• Knowledge of the ‘termination date’ field in the third-party application.

• Instance name shared with Zluri for data retrieval.

Setup Instructions

Follow these step-by-step instructions to set up Zero Touch Offboarding:

1. Access Application Settings

   • Log in to your third-party application (e.g., BambooHR) as an admin or a user with appropriate permissions.

   • Navigate to the settings section and access the fields related to employee information.

2. Locate the ‘Termination Date’ Field

   • Identify the specific field that contains the termination date of employees, as this information is crucial for the offboarding process.

3. Share Details with Zluri

   • Provide Zluri with the instance name from which the employee's offboarding information needs to be fetched to ensure accurate data retrieval.

   • Share the details of the “termination date.” Zluri will perform the internal configuration needed to set up Zero Touch Offboarding for you.

4. Access Zluri's Automation Rules

   • Log in to Zluri and navigate to the Automation Rules section to configure rules and triggers based on various events.

5. Create a New Automation Rule

   • Within Zluri's Offboarding automation rules section, create a new rule specifically for the offboarding process.

6. Choose the Trigger

   • Select "User is Marked for Offboarding" as the trigger for the automation rule. This ensures that the rule executes whenever an employee's termination date is updated in the third-party application.

7. Choose the Condition

   • Select "User Account Type equals Employee." This condition is mandatory.

8. Configure Actions

   • Define the actions to be performed when the termination date is updated in a playbook. Actions may include sending automated farewell emails, assigning tasks to team members, or initiating an offboarding playbook. Choose the playbook to run when the automation rule triggers.

9. Deploy the Automation Rule

   • Save the automation rule and activate it for the live environment. Zluri will now use the termination date from the third-party application as a marker for offboarding.

Additional Notes

• Ensure that the termination date in the third-party application is at least two days in the future for Zluri to fetch information, which occurs every 24-48 hours.

• All users' termination dates will be fetched from the application, with the timezone defaulting to 00:00:00 GMT+0000 (UTC).

• This process will only execute for the instance shared with Zluri. If multiple instances of HRMS are integrated with Zluri, the configuration will be done on the instance level, not at the integration level. Thus, if needed, configuration should be done on all instances.