Skip to main content
Automations run OpenHands on a schedule or in response to events, such as reviewing a pull request when it opens. In OpenHands Enterprise, automations belong to an organization and are shared with every member of that organization. This page explains how automations behave inside an organization. To create, browse, run, and manage automations, see Managing Automations.

​
How Automations Work in OpenHands Enterprise

​
Automations Are Visible to the Whole Organization

All automations in an organization are visible to all members of that organization. Automations often power parts of the software development lifecycle, such as code review, issue triage, and dependency upgrades. Everyone who works in that lifecycle needs to understand what is automated, when it runs, and what it does. Sharing automations across the organization makes that behavior transparent.
Because every organization member can see an automation’s configuration and the conversations it starts, do not put secret values in automation prompts. Store credentials as secrets instead.

​
Automation Conversations Are Read-Only for Other Members

The conversations started by automation runs are also visible to all organization members. Members who did not create the automation see these conversations in read-only mode. They can follow the full conversation history, but cannot send messages to the agent or change the automation. For example, an automation that reviews GitHub pull requests may post a link to its conversation in the review comment. Any member of the organization can open that link to see the details of what the agent found.

​
Automations Run as the Creating User

Every automation run executes under a user identity. Currently, that identity is the user who created the automation. To see which user an automation runs as, open the automation and check the Automation Run field in its details.

​
Who Can Manage Automations

Who can edit, disable, or delete an automation depends on the user’s organization role: Owners and Admins can act on automations on behalf of other users. For example, an Admin can turn off an automation created by a user who is no longer available to maintain it.

​
Next Steps