Overview
The recipes and trigger conditions you can use depend on your permission to data. The people to whom your automations will apply depend on your permission scope.
Remember that permissions are additive. If you’re assigned multiple permission profiles, the broadest permissions you have will be used to determine how you can set up automations.
Automations are a feature tied to your Rippling Platform tier.
Permission to data
Your permission to access the data in Rippling determines how you can set up the conditions that will cause an automation to trigger. Data you don’t have permission to access is grayed out and not selectable when setting up an automation.
You can trigger an automation using data associated with the Rippling apps and services you have permission to access. The employee data you can use is based on your permissions for personal and employment data.
Admins who only have permission to view individual employee data fields (as opposed to an entire sensitivity classification) and do not have any other permissions will NOT be able to set up automations using those fields. However, if you give someone any other permission, such as the ability to edit any field(s), permission to manage an app, the ability to hire and terminate, or the ability to view or edit Organizational Data, they’ll then be able to trigger automations using the individual employee data fields they have permission to view.
To use trigger events based on imported third-party data, you must have permission to view the data. If you’re using a pipeline, you must be assigned an object permission profile that gives you access to view the data. For more information, see Permissions for data in Rippling.
Permission scope
Your permission scope determines who the automations you set up will be triggered for. You may have the scope of:
- The entire company
- Your direct and indirect reports
- A custom scope
These fields are examples of how each data sensitivity classification is handled in an automation:
- Start date is classified as basic data, meaning everyone has the ability to view it for everyone else in the company. An automation that triggers on start date runs for every new hire at the company, even if the owner’s scope is only direct and indirect reports.
- Home address is classified as non-sensitive personal data. If the owner’s scope is direct and indirect reports, the automation will be triggered when one of the admin’s direct or indirect reports changes their home address.
- Annual compensation is classified as sensitive employment data. If the owner can view all sensitive employment data for the entire company, the automation will be triggered when annual compensation changes for any employee. If they only have basic and non-sensitive employment data, the annual compensation variable will be grayed out, so they will not be able to set up the automation.
Permissions and automation steps
The permissions outlined above only apply to automation triggers, not to steps.
- Permission scope doesn’t apply when selecting the recipients of an automation step. The admin who creates an automation can include anyone in the company as the recipient of an email, Slack message, task, etc., created by an automation.
- Permission to data doesn’t apply when including variables in an automation step. When an admin includes a variable in something like an email or Slack message, the recipient will be able to see the information, regardless of their permissions.
Say an admin includes the Annual compensation variable in an email message sent by the automation. The admin can include anyone in the company as recipients of the email. Everyone who receives the email will be able to view the compensation of the people for whom the automation was triggered.
Keep this in mind when you share automations to collaborate with other people.
Permissions to share automations
Automation owners can collaborate with others by sharing the automations they’ve created. Anyone with permission to create an automation can share that automation. The recipients will have access to the same automation variables as the owner.
When you share an automation, the person you share it with can use all of the same variables and events as you. This means that they might add fields to the automation that they normally can't access. However, they won't be able to see any field values while setting up the automation.
For example, if you have access to sensitive employment data, and you share an automation with someone who only has access to non-sensitive employment data, the collaborator will be able to add variables for sensitive data, such as annual compensation. The collaborator won’t be able to see anyone’s actual compensation while editing the automation. However, these variables could be shown to other people in steps such as emails or Slack messages.
You can only share automations with people who have access to Automation Studio.