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.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 theAutomation 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
- Managing Automations - Browse, run, enable, disable, export, and import automations.
- Automations Overview - Learn about automation triggers and use cases.
- Conversations and Sandboxes - Understand conversation lifecycle and read-only conversations.