Skip to main content

​
What this means

An action is work the workflow can perform: for example, reading evidence, preparing a draft, or proposing a change. Reading and drafting are different from sending a message or changing a business record. Availability depends on the specific workflow and its configuration.

​
What to configure and check

The Agents workspace uses agents:view for viewing and agents:manage for management. An administrator label alone is not the full access rule. Other parts of the product have their own permissions; Agents access does not grant access to every source or approval. Before changing a workflow, inspect its supported controls and the consequences of the change. The approval-policy screen is available only where its configurator is enabled and the required permissions are granted; see Approvals. Do not assume every workflow has the same action editor.

​
How it connects

Context supports the proposed work. Approvals are a separate decision on that work, not a substitute for permissions. A connection authorizes scoped system access; it does not by itself authorize a customer-facing send.

​
Example

A reviewer can inspect a proposed customer reply and compare it with the request and commercial evidence. That does not mean anyone who can view Agents can send the reply, alter pricing, or approve a lesson.

​
When access is denied

Ask the organization owner to check the required permission and account capability. Do not share accounts or retry the operation through another integration to bypass the denial.