Automate provides comprehensive security and permissions controls to ensure automations execute safely and that users only see information they are authorized to access.
Automate is governed by the same security and permissions model as the rest of the platform. Users can only see and interact with the automations to which they have access. This ensures condition evaluation and effects always reflect the appropriate data access at the time when the automation is evaluated.
Understanding who has permission to see what is critical for secure automation design:
Manual executions bypass trigger conditions, so Automate does not perform trigger-object permission checks. The input object set is still evaluated with the permissions of the user who starts the manual run.
Learn more about how permissions work for different effect types in our Automate permissions documentation.
Automations can be configured with different scoping options that determine who can access the run history for action, Logic, and function executions:
Learn more about scoping options in our history visibility and scope documentation.
Automations can be owned by third-party applications instead of individual users. This ties execution history and permissions to the application's service user, preserving team continuity when an individual owner is unavailable.
Learn more about third-party application ownership.
Automate tracks execution history and activity to provide visibility into automation behavior while respecting security boundaries:
Learn more about execution events and retention in our Automation history documentation.