Automation Rules

This section allows you to create rules for your playbook and view the existing set of automation rules and relevant information. To set a new rule, click on the New Rule button on the top right of the screen.



The onboarding rule creation screen opens.



You can set the following parameters for the rule:


  1. Add trigger: Define a trigger that runs your automation. There are mainly three kinds of triggers:

  • User Status Changes

  • New User Added/Discovered In Zluri

  • The user Is Marked For Onboarding



  1. Add attributes: This enables you to selectively run the automation based on the conditions that can be set from the list below:



  • Reporting Manager: This is usually the name of the employee’s reporting manager.

  • User Designation: The name of the designation that applies to the user.

  • Last Active: This usually is in numeric format and denotes the timestamp of the user's last activity.

  • User Account Type: Usually, in text, this denotes whether the user account is an admin account or any other type.

  • Critical Apps Used: The number of critical apps the user uses is an attribute here.

  • Primary Source: The name of the app/apps used as the primary source for creating the condition.

  • User Department: The name of the user department.

  • Role: This is the name of the user role.

  • Created At: a number denoting the timestamp to be used as a condition.

  • Risk Level: A number denoting the risk level associated with the particular condition.

  • Apps Used: The number of apps used to set the particular condition.

  • User Status: a text denoting the current user status based on which the condition can be set.


  1. Add a playbook: Choose to run an existing playbook for the new rule.

  2. Add Delay: This is used to set a time delay after which the rule will be executed. Delays can be really helpful when working with multiple automation rules, as you might want to cascade automation rules. 


(For example, you may create an automation rule for providing access to general apps used across an organization when a New user is Onboarded, and this will run automatically immediately as soon as Zluri detects a new User marked for onboarding. 


For convenience, you can set the admin access time with a delay of 2 days after a New user is marked for onboarding. Then this automation rule can  give access to specific apps used by department users.)

  1. Save rule: You can save the rule once all the previous conditions have been set.



From the list of rules available, you can perform the following actions:


  1. Edit/Delete a rule by clicking on the 3-dot option next to each rule.

  2. You can change the status of a rule and set it to active/inactive by clicking on the toggle below the status column.

You can manually drag each rule by the arrow next to the rule name to put it above/below a rule. This will help you set the Order of the rule.

Can’t find what you are looking for? Let us help you!

Automation Rules

Modified on Sat, 31 Dec 2022 at 05:43 PM

This section allows you to create rules for your playbook and view the existing set of automation rules and relevant information. To set a new rule, click on the New Rule button on the top right of the screen.



The onboarding rule creation screen opens.



You can set the following parameters for the rule:


  1. Add trigger: Define a trigger that runs your automation. There are mainly three kinds of triggers:

  • User Status Changes

  • New User Added/Discovered In Zluri

  • The user Is Marked For Onboarding



  1. Add attributes: This enables you to selectively run the automation based on the conditions that can be set from the list below:



  • Reporting Manager: This is usually the name of the employee’s reporting manager.

  • User Designation: The name of the designation that applies to the user.

  • Last Active: This usually is in numeric format and denotes the timestamp of the user's last activity.

  • User Account Type: Usually, in text, this denotes whether the user account is an admin account or any other type.

  • Critical Apps Used: The number of critical apps the user uses is an attribute here.

  • Primary Source: The name of the app/apps used as the primary source for creating the condition.

  • User Department: The name of the user department.

  • Role: This is the name of the user role.

  • Created At: a number denoting the timestamp to be used as a condition.

  • Risk Level: A number denoting the risk level associated with the particular condition.

  • Apps Used: The number of apps used to set the particular condition.

  • User Status: a text denoting the current user status based on which the condition can be set.


  1. Add a playbook: Choose to run an existing playbook for the new rule.

  2. Add Delay: This is used to set a time delay after which the rule will be executed. Delays can be really helpful when working with multiple automation rules, as you might want to cascade automation rules. 


(For example, you may create an automation rule for providing access to general apps used across an organization when a New user is Onboarded, and this will run automatically immediately as soon as Zluri detects a new User marked for onboarding. 


For convenience, you can set the admin access time with a delay of 2 days after a New user is marked for onboarding. Then this automation rule can  give access to specific apps used by department users.)

  1. Save rule: You can save the rule once all the previous conditions have been set.



From the list of rules available, you can perform the following actions:


  1. Edit/Delete a rule by clicking on the 3-dot option next to each rule.

  2. You can change the status of a rule and set it to active/inactive by clicking on the toggle below the status column.

You can manually drag each rule by the arrow next to the rule name to put it above/below a rule. This will help you set the Order of the rule.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article