Skip to main content
Open an agent from its workspace’s Agents list. Older links to Releases, Identity, or Access open Settings, and a link that names Traces opens Sessions. Its profile brings together its registered definition and the evidence attributed to it. The tabs describe stored records. A linked skill or model does not prove the runtime used it in a particular run; check the trace for that run.

What the agent reads

The Overview’s Knowledge section lists the knowledge bundles the agent reads, each linking to the bundle’s page. An agent with no recorded bundles shows no Knowledge section. A run reads them through the registry when it needs them; they are not loaded into every run.

Identity and access

Each agent authenticates through its own identity. Identity, under Settings, shows its client ID when available. Rotate API key reveals a new key once; Rotate client secret replaces the secret Atlan Trident keeps. Each action replaces the named credential, so update applications that depend on it. See How agent identity works. Access to the agent follows its workspace. Who can reach it shows that scope, and Your permissions shows the actions available to the signed-in viewer. Credential changes require permission and are enforced by the service.
Revoke credentials invalidates both the API key and client secret on their next request. The app cannot undo this or rotate a revoked identity; new credentials require a new agent. Use rotation when you need to replace a working credential.

Profile actions

The More agent actions menu provides Edit agent and Archive agent. Editing keeps the machine name and workspace fixed. Archiving removes the agent from lists and stops its key from authenticating; review Archive agent before confirming.