From the Automations dashboard—available from the settings icon () > Automations tab—you can view, filter, and manage your workflows.
You can view all Automations for your fleet from the settings icon () > Automations tab. To find specific automations, you can search for the automation or filter by name, trigger type, status, action, or owner. For each automation, you can view the following information:
|
Field |
Description |
|---|---|
|
|
Toggle the automation on or off as needed. |
|
Automation |
The name or identifier of the automation workflow configured in Samsara. This represents the specific rule set or process that executes actions based on triggers. See Samsara documentation for automation concepts. |
|
In Progress |
The number of automation runs that have been triggered and are actively executing but have not yet finished. Represents workflows that are still being evaluated or whose actions are not complete. |
|
Complete |
The number of completed automation runs. A completed run means all defined actions executed successfully following the trigger conditions. |
|
Failed |
The number of automation executions that did not complete as expected due to an error condition or unmet dependencies. |
|
Last run |
The timestamp indicating when the automation was most recently executed. |
|
Last Edited By |
The user or account that most recently modified the automation configuration. Useful for auditing changes or identifying ownership. Form more information, see Transfer an Automation to Another Owner. |
|
more actions ( ••• ) menu |
Additional actions that you can perform on an automation. Actions differ by permissions and rule ownership but can include Edit, Duplicate, Delete. The View History option can also help you Troubleshoot Automation Issues. |
The user who creates an automation is its owner. Ownership does not change automatically. If responsibility for maintaining an automation shifts to another user, you must manually recreate the automation under the new owner’s account.
-
Only users with the same or broader scope permissions than the current owner can edit an existing automation.
-
Automations always execute using the original creator’s permission scope.
-
If an automation is edited to include entities (for example, drivers, vehicles, or tags) outside of the original creator’s scope, the automation may fail at runtime.
Example: If User A (Tag A) creates an automation, User B (Tag B only) cannot edit it. A user with access to both Tag A and Tag B can edit it. However, the automation will still run under User A’s permissions unless ownership is effectively transferred.
Consider transferring ownership in the following scenarios:
-
The original owner changes roles or leaves the organization.
-
Administrative responsibility for the automation shifts to another team.
-
The automation requires expanded scope beyond the original owner’s permissions.
Because ownership cannot be reassigned directly, use the following process to transfer responsibility:
-
Log in as the new owner.
-
Identify the automation you want to recreate.
-
From the more actions ( ••• ) menu, select Duplicate.
-
Review and Save the automation.
-
Toggle the automation status to the
off position to Disable the original automation and prevent duplicate or conflicting runs.
You can also request that the original owner Delete the original rule.
-
Validate that the new automation functions as expected and has the correct scope.
Comments
0 comments
Please sign in to leave a comment.