š Note: The screenshots and settings shown in this article may not match what you see in your own platform, as Rosterfy is highly customisable. If you need guidance specific to your setup, please contact our support team.
Marking an Automation as inheritable passes the workflow from a parent account to all sub-accounts. This keeps your processes consistent and saves time by removing the need for duplicate setups.
IN THIS ARTICLE:
Enable the Automation Inheritance Setting
Click Organization Settings > Advanced > Enabled Automation Inheritance.
Toggle the Use Default option off.
Click the dropdown and select Yes, as shown above.
Click the Save button.
Configuring the Automation to be Inheritable
Create an Automation.
Check the Allow automation to be inheritable box to allow the automation to be inheritable. This is unchecked by default.
The Apply to all Subaccounts checkbox appears. It is checked by default.
Click the Save button.
Specify Subaccounts to Inherit the Automation
Uncheck the Apply to all Subaccounts checkbox. The Target specific accounts field appears:
Click the dropdown and enter the subaccounts you wish to include.
Click the Save button.
Actions That Can Be Inherited
While all Automation tasks can be inherited to the aubaccounts via the above settings, only the following Actions can be inherited:
Email
Email to Specific Email Address
Email to Email Attribute
Email to Event User
Email to Event Leader
Email to Shift User
Email to Shift Leader
Email to Referee/Consenter
Email to Account Contact
Email to Notifiers
User Attribute - Update
User Checkpoint - Update
Inventory Item - Assign
Update Shift User Status
If any other Actions other than the above are added to an inherited Automation, the Action will be highlighted red in the Actions list. They will still run on the parent account, but will be skipped when the Automation runs on a subaccount.
Automations can be marked as inheritable regardless of whether the subaccount has been created already. The inherited automations will appear in subaccounts as read-only.
Actions in inherited Automations that use branding will adopt the branding of the subaccount once inherited.
Automation inheritance is backwards compatible, meaning if the inherit automations checkbox is unticked, all inherited automations will be removed from subaccounts.