> ## Documentation Index
> Fetch the complete documentation index at: https://docs.agentsfleet.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Key concepts

> Understand tenants, workspaces, fleets, tools, events, and runs.

# Key concepts

## What it is

`agentsfleet` groups your account into four main resources.

| Resource  | Purpose                                                    |
| --------- | ---------------------------------------------------------- |
| Tenant    | Owns identity, billing, provider settings, and workspaces. |
| Workspace | Groups fleets, secrets, connectors, and access.            |
| Fleet     | Handles one recurring outcome from one or more triggers.   |
| Tool      | Gives a fleet one named action, such as an HTTP request.   |

An event is one incoming delivery. A run is the fleet's work on one event.

## Why it exists

The hierarchy keeps billing, access, and secrets separate from each fleet's task. A workspace can hold several fleets that share approved secrets.

## How it behaves

You create a workspace. The tenant owns the workspace until an account administrator removes the account data.

You install a fleet in one workspace. The workspace owns the fleet, and an authorized member can stop or delete it.

A trigger creates an event. The fleet opens one run, calls allowed tools, and records results in the activity stream.

The fleet sees secret references. The credential firewall adds secret values only when an allowed network call leaves the sandbox.

## Limits

A fleet cannot call an undeclared tool. A fleet also cannot contact a host outside its network list.

Daily and monthly fleet budgets can block work. Provider and account limits can also block a run.

## Related pages

* [Fleet overview](/fleets/overview)
* [Workspace overview](/workspaces/overview)
* [Secrets](/fleets/secrets)
* [Run context](/concepts/context-lifecycle)