Distribute to clients
Send agents, workflows and other resources to client workspaces, deploy managed agents, push updates and revoke access.
You build once in your agency workspace and distribute to many clients. There are two ways to hand something over: send it as a resource the client can use, or deploy it as a managed agent or workflow that your agency maintains.
Distribute resources
Open Access in the agency console. The Resources tab lets you push agents, workflows, schedules, skills, rules and connections to your client workspaces. The same page has Models and Features tabs for one client at a time: choose the client with Pick a client.
Choose a resource type
Use the tabs along the top of Resources: Agents, Workflows, Schedules, Rules, Skills or Connections.
Choose the client
Pick the client to distribute to ("Step 1 — choose the client to distribute to").
Tick what to send
Your own resources are listed. Tick a resource to distribute it to that client; untick it to revoke the distribution. You can also use Select all and Deselect all.
On a client's page, the Resources tab lists what you distributed, with Revoke.
A distributed agent, workflow, skill or rule is an independent copy in the client's workspace. Later edits to your original are not sent automatically; see "Push an update" below for agents. Sharing a connection is different: clients inherit your integration.
Deploy a managed agent or workflow
A managed agent is one your agency maintains inside a client's workspace. To deploy one, open the client's page, go to Resources and choose Deploy managed resource. You can also deploy to several clients at once.
Pick the resource
Choose Agent or Workflow from your agency's own workspace. Build it there first if needed.
Set client access
Choose Read-only (recommended): the client can run the agent and change its inputs, model and connections, but not its configuration, so your agency stays in control. Or choose Client can edit, which lets the client's admins change the configuration themselves. Switch on Client can see automated runs if the client's admin should see runs the agent starts on its own.
Deploy
Confirm with Deploy. Each client gets its own copy, and the agent shows as managed in their workspace.
You can change client access later with Allow editing or Make read-only on the managed resource. If a client is on the Free plan, the dialog warns that runs may hit Free-plan limits; it does not block the deploy.
From the managed resource you can also Change the owner to a person in the client's workspace (you keep managing it), or Delete permanently, which removes it from the client's workspace for good while past runs stay in the history.
Push an update
When you improve the original agent, open it and choose Push update to client. The dialog lists each deployed copy and whether it is In sync, Client edited this copy or has No baseline recorded.
- Skip those clients (recommended) only pushes where the copy is unchanged.
- Overwrite their changes pushes everywhere. A restore point is saved first, so the previous setup is not lost.
Each client then shows its result: Updated, Skipped or Failed. If a client asks to roll a managed agent back to an earlier version, the request appears under Restore requests on their page and you choose Approve or Decline.
Who pays
When you deploy, billing defaults to the client's own balance. You can change who pays, and set your prices, per agent afterwards from the client's Resources tab. See Agency billing.
Standard agents and templates
Standard agents lets you enable or disable the platform's catalogue agents for each client. Templates holds agents you have published from your agency workspace with Save as template.