Workflows
A workflow is a saved process for work you expect to repeat. It combines instructions, knowledge, and capabilities so the same job can be started with a simple request.
From a task to a workflow
Start by asking your AI to complete the task. Once the result and process are right, ask it to save the work as a workflow.
The workflow captures what should happen, which context matters, and which capabilities may be needed. It lives in HexaHQ instead of one conversation, so it can be found, reviewed, improved, and shared.
Running a workflow
When someone runs a workflow, HexaHQ uses that person's available knowledge, credentials, and permissions. The workflow does not give anyone access they do not already have.
Each capability still follows its current Allow, Ask, or Deny policy. A workflow can continue through allowed steps, pause for approval, or stop if a required action is denied.
Each execution creates a run, where you can see the steps your own work took.
Personal and shared changes
You can adjust a workflow for your own work without changing the version used by everyone else. Changes intended for the organization go through review before they become the published version. Unlike knowledge, a workflow change is never accepted automatically: a workflow acts on your systems under each person's own credentials, so publishing one to the whole team is always somebody's decision.
This lets people improve a process as they use it without quietly changing how the rest of the team works.