Access to automation run history

Is there a way to allow access to automation run history for more than just the automation owner?

This will be especially helpful for the following user groups:

  1. Rest of the team to debug potential issues with automations and understand when they were last run
  2. Platform admins/governance managers to be able to dig into especially expensive automations to understand if there are opportunities for optimization

On the configuration settings, you should be able to add a list of Automate Administrators, who are able to be notified of failures and should be able to view the history.

status update for anyone landing here, this is now covered by the automation’s scope setting:

  • project scoped (the recommended mode): run history, including effect executions, is visible to every user who satisfies the markings on that run. it still runs as the owner. all resources the automation uses must be imported into the project
  • user scoped: only the owner sees run history. turning on shared trigger history lets others with access to the marked data see that runs happened, but effect executions stay owner only

automation administrators (from the reply above) control who gets warning and failure notifications, not who sees history

limits of project scope worth knowing before switching: no notification effects, no stateful functions (deployed python, aip chatbot functions, functions using a platform sdk), no cross-org workflows, and restricted view object types need the owner and viewers to have access to all rows