Skip to content

Find and read an agent

Use the Agents page to find any agent that has reported to your organization, and its tabs to see who it acts for and which rules it runs under. Every role can read it.

The Agents page lists every agent in the organization. The figures at the top count all agents, the agents seen within the selected window, and the agents not seen within it. Search by name, owner, platform or host, and filter the list to narrow it.

The Agents page of the OpenLatch console, in the Crispy Pay demo organization.The Agents page of the OpenLatch console, in the Crispy Pay demo organization.
The Agents page: every agent in the organization, with its owner, control level and last activity.

Each agent carries a control level: Enforced, Monitored or Known. It tells you what OpenLatch can do with that agent, so you never assume an agent is controlled because it is listed.

To connect a new agent, choose Install an agent and run the command it shows on the machine. Install the client explains the commands.

Open an agent. Its Overview tab summarizes what it did over the selected window: its actions, the elevated ones among them, the endpoints it reached, and the anomalies it raised.

The Overview tab of an agent in the OpenLatch console, in the Crispy Pay demo organization.The Overview tab of an agent in the OpenLatch console, in the Crispy Pay demo organization.
An agent's Overview tab: its activity over the window and what needs a look.

The other tabs are covered by Investigate what an agent did, Review an agent’s configuration and Track an agent’s spend.

The Identity tab names the person accountable for the agent and where they sit in the organization. With a directory connected, the owner is resolved through a read-only lookup; see Connect a directory for owner lookup.

The Identity tab of an agent in the OpenLatch console, in the Crispy Pay demo organization.The Identity tab of an agent in the OpenLatch console, in the Crispy Pay demo organization.
An agent's Identity tab: its owner, and where they sit in the organization.
  1. Choose Why this owner? to see how the owner was resolved, from the signals the machine reported to the directory record they matched.
  2. If the owner is wrong, choose Override ownership and pick the right person. If that person is not in the directory, add them by hand with their email address and, optionally, their name and job title. For an agent that acts for a service rather than a person, name the service and the person accountable for it.

Overriding ownership needs the editor role or higher, and it is recorded in the audit trail.

The Autonomy Zone tab shows the effective zone the agent resolves to: the layers it inherits, from the organization down to its own unit, and the intent policies in force on it. An agent at the Known control level is listed with its zone, but its zone is not enforced on it.

The Autonomy Zone tab of an agent in the OpenLatch console, in the Crispy Pay demo organization.The Autonomy Zone tab of an agent in the OpenLatch console, in the Crispy Pay demo organization.
An agent's Autonomy Zone tab: the layers it inherits and the intent policies in force.

To move an agent to another zone, see Manage Autonomy Zones.

Delete agent, in the agent’s actions menu, permanently deletes the agent with every session and event recorded for it; the history cannot be recovered. If the client on that machine sends another event, the agent comes back with a new ID. Remove the client from the machine first if the agent should stay gone; see Operate. The same menu exports the agent as JSON.