Skip to main content
A deployment is one agent on one store. An agent can run on many stores, and each deployment has its own mode, its own status and its own history. An agent starts its schedules, and can be chatted with, only once it is deployed. Deploying and managing deployments needs agent:write.

​
Deploy an agent

1

Open the deploy dialog

On the agent’s page, choose Deploy. Or go to Agents → Deployments → Deploy agent and pick the Agent.
2

Pick the stores

Choose one or more Stores. Stores it already runs on are not offered.
3

Deploy

Deploy to 1 store (or more). The deployment starts in the agent’s own mode, which is Act for every agent created in the dashboard.
To start on a store in a lower mode, deploy it, then change the mode on the deployment’s Settings before its first scheduled run.

​
Find a deployment

Agents → Deployments lists every deployment: the agent, the store, its mode and status, and when it last ran. Filter by Agent, Store or Deployment status. An agent’s own Deployments tab lists just its own. A deployment’s page has four tabs:

​
Modes

The mode says how far an agent may go on its own, on one store. Change it on the deployment’s Settings, then save with the save bar.
Choosing Act needs the agent:mode permission, which only the Owner and Admin roles have by default. Anyone with agent:write can lower a deployment to Recommend or Observe.
The Fraud agent’s order checks read what the buyer did on your storefront before ordering. If storefront events are not reaching Glood, the deployment’s Settings says so; see Set up storefront events.

​
Deployment actions

The header of a deployment holds what its status allows: Pause is the way to stop one store’s checks while the agent keeps running elsewhere. To stop the agent everywhere, archive it.