Who this is for. Super Admins setting up or maintaining an Agent Co-worker. See the Roles and Access.
The Agent Co-workers page lists every Agent Co-worker in the tenant. Open it from the second icon down the left rail. The heading reads “Click Agents to view status, run, pause, stop, and configure”, and a Total count sits at the top right beside a Search for Agent Co-workers field.
Open the Agent Co-workers page
Figure 1. The Agent Co-workers page.
In the Workcenter left navigation, select the Agent Co-workers icon (the robot).
What the page shows
Agents are not listed flat. Each sits under the autonomous process it belongs to, and the group header carries a count of the agents in it.
A group can hold more than one agent. AP Helpdesk and AP Invoices are functions of SmartVendor, which sits under Autonomous Procure To Pay.
Each row shows the Agent Co-worker name and how many instances are currently running. The Search for Agent Co-workers box filters the list by name, and the Total counter at the top right shows how many Agent Co-workers exist across all groups.
There is no agent called “AP Helpdesk” on this page. AP Helpdesk work is done by an instance of SmartVendor, under Autonomous Procure To Pay. The list therefore shows SmartVendor rather than AP Helpdesk.
Running Instances popup
Select an Agent Co-worker to open its popup. Show Description under the name expands the Agent Co-worker’s description, and the Running Instances table lists one row per instance, with the columns described in Table 1.
Figure 2. The Running Instances popup for SmartVendor.
Instances
Selecting an agent name opens a panel listing its running instances. The row beneath the agent name reports how many are running, for example “3 instances running”. If your tenant restricts mailbox access, both that count and the panel show only the instances bound to a mailbox you have access to, unless you are a Super Admin. An instance someone else set up may not appear.
Table 1. Columns in the instance list
Column |
Holds |
|---|---|
Agent Name |
The name given to the instance on the Work scope step of the wizard. |
ERP |
The system-of-record connection the instance works on. |
Mailbox |
The connected mailbox the instance monitors. |
Status |
Whether the instance is running. |
Replies |
Whether replies are enabled for this instance. |
Actions |
Mailbox
The connected mailbox that feeds it.
Status
Running, with a status dot.
Replies
Enabled or otherwise.
Actions
Pause, Delete and Edit, one set per row. See Actions from the popup below.
One instance runs per mailbox. A mailbox already bound to a running instance is not offered again when a new instance is created.
The control at the foot of the popup opens the New AI agent co-worker wizard. It reads Create Agent. It creates a new instance, and it does not restart, pause or otherwise disturb the instances listed above it. It appears only for a role that can create Agent Co-workers.
Where every connected mailbox already has an instance, the wizard opens and says so, and you connect another mailbox before you can continue.
One Agent Co-worker, several instances
One Agent Co-worker can run more than one instance, one per ERP-and-mailbox pairing. The popup is where those instances are managed individually. The configuration wizard also works on one instance: whichever row you opened it from.
Actions from the popup
Figure 3. The Replies and Actions columns. Every instance carries the same three controls: pause, delete, and edit.
Create Agent opens the setup wizard so you can configure and start another instance. It appears only for roles with rights to create Agent Co-workers. Where every connected mailbox already has an instance, the wizard opens and says so, and you connect another mailbox before you can continue.
Depending on your permissions the Actions column holds up to three controls: the replies Pause toggle, Delete, and Edit. While replies are enabled, Pause and Delete are both red circles, so read the tooltip before selecting either. Once replies are paused the first control turns green, because it now resumes them. Delete carries a square glyph that reads as a stop control, but it deletes: it asks for confirmation and then removes the instance, so the row leaves the table rather than changing state. Status reads Running for every live instance.
Edit (the pencil) opens the Edit AI agent co-worker wizard, where the configuration articles in this set continue. Edit is per instance, so check the ERP and mailbox on the row before selecting. For more information, see Maintain Agent Co-workers.
You can pause an Agent Co-worker’s replies if your role has update rights on Agent Co-worker management. Pause is the first control in the Actions column, a red circle carrying a small bell, which is what ties it to the Replies column beside it. Its title reads Pause when replies are enabled and Resume when they are paused, and the Replies column then reads Paused instead of Enabled. The instance keeps processing; with replies paused it stops acting autonomously and no longer sends replies.
Check what an instance is bound to
The instance row is where a connection problem becomes visible. An agent cannot exceed what its connection allows, whatever is configured downstream.
Table 2. What to confirm on the row
Column |
Confirm |
|---|---|
ERP |
That it is the intended environment. The system of record cannot be changed after the instance is created. |
Mailbox |
That it is the mailbox you meant. One instance per mailbox. |
Status |
Running. Every instance in the list reads Running. A stopped instance is removed from the table rather than shown as stopped. |
An agent cannot exceed the permissions of the account its connection authenticates as. A read-only integration user cannot post to the system of record, and no autonomy level, threshold, or rule overrides that. The row shows the ERP, mailbox and status, not what the connection account is permitted to do. Where nothing posts whatever the configuration says, ask the Super Admin who created the connection to confirm the integration user has write access to the system of record.