Release Notes
Simplified Sharing in Agent Builder
Now you’ll be able to share custom Workflow agents with clearer access levels—Run, View, Edit, or Full access.
What's New
Reminder: Workflows have been renamed to better reflect future agentic capabilities to come:
- Workflows > Workflow agents
- Workflow Builder > Agent Builder
We’ve made improvements to sharing options for custom Workflow agents so that assigning access levels is more clear and consistent.
Rather than assigning Build or Run access, Builders can now select from a single set of access levels aligned with sharing elsewhere in Harvey: Run, View, Edit, or Full access.

Important: Existing sharing permissions will remain as they are today. No access will be removed, and you won’t lose any functionality.
Key Updates
- Assign Workflow agent access using clear levels: Run, View, Edit, or Full access
- Instead of Build access use Edit or Full access
- Instead of Run access use Run or View access
- Designate which users should have access to the Workflow agent before publishing. They’ll still only be able to view and run the agent once it is approved and published, but this allows you to queue up sharing.
Why It Matters
The goal of these changes is to align sharing options across Harvey’s product areas, making sharing easier and more intuitive, while preserving the granular controls teams rely on.
How to Use
This update does not change the function of sharing Workflow agents, it should simply surface more clear options when sharing them. Refer to the chart below for an overview of the changes.
Before | After |
|---|---|
|
|
|
|
|
|
FAQs
Q: What’s changing from the current sharing model?
Workflow agent sharing will move away from managing Build and Run permissions separately. Instead, you’ll use a single set of access levels that match sharing patterns used across Harvey.
Q: Will existing Workflow agent permissions change when this launches?
No. Existing sharing permissions will not be changed or updated as part of this release. Users will not lose any functionality or see Workflow agents they should not have access to.