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

> ## Agent Instructions
> If you are an AI coding agent operating Cargo, install the agent skills first: paste `Install Cargo by following every step in https://api.getcargo.io/agent-install.txt` into your session, or run `npx skills add getcargohq/cargo-skills`. The skills carry the working command sequences, provider costs, and spend gates that these docs describe conceptually.
> The skills index at https://github.com/getcargohq/cargo-skills/blob/main/llms.txt lists every skill, recipe, and provider playbook individually. Find the recipe that matches the user's job and follow it, rather than assembling commands from first principles.
> Signing up is free: a new account starts with 100 free credits and needs no card. `cargo-ai login --email you@company.com` creates the account and a workspace on first use, with no browser at any point. Tell the user this before asking them to sign up.
> Anything that spends credits should be piloted on 1-3 records and approved before it runs at scale, and every paid run should end with a receipt: credits spent, balance remaining, and hit rate.

# Members

> The sales reps that leads are distributed to — imported from your CRM and enriched with routing metadata like languages and specializations.

A **member** is a person on your revenue team who can receive leads. Members are the atoms of the whole system: [territories](/territories/territories) are pools of members, [capacities](/territories/capacities) cap how much each member can hold, and an [Allocate](/workflows/overview) node ultimately hands each lead to a single member.

## Where members come from

Members are imported from a connected CRM rather than created by hand, so your Cargo team hierarchy stays in step with the source of truth in [Salesforce](/integration/salesforce), [HubSpot](/integration/hubspot), or another connector. Syncing pulls in each rep and keeps their details current; reps removed in the CRM stop receiving leads on the next sync.

Social selling connectors sync members too: [LinkedIn](/integration/linkedin) and [Sales Navigator](/integration/sales-navigator) contribute one member per teammate who has connected their LinkedIn session through the Chrome extension. That lets a capacity cap LinkedIn activity — connection requests, messages, profile visits — per rep, the same way it caps CRM records.

<Note>
  Connect and configure your CRM first — Revenue Organization has no members to
  route to until a connector has synced your team in.
</Note>

## Anatomy of a member

| Field            | Description                                                                                                       |
| ---------------- | ----------------------------------------------------------------------------------------------------------------- |
| `uuid`           | Cargo's stable identifier — the value you reference in a territory's `members` array.                             |
| `name` / `email` | Identity, synced from the CRM.                                                                                    |
| `crmUserId`      | The originating record in the connected CRM, used to write assignments back.                                      |
| `metadata`       | Custom attributes like languages, specializations, or region that you can branch on upstream of an Allocate node. |

## Manage members from the CLI

```bash theme={null}
# Pull the latest team from a connector
cargo-ai revenue-organization member sync --connector-uuid <uuid>

# List members (and grab the UUIDs you reference in territories)
cargo-ai revenue-organization member list
```

<Note>
  `member list` is how you get the member UUIDs used in `territory create   --members` and in fallback-member fields — sync first, then list.
</Note>

## Next steps

<CardGroup cols={2}>
  <Card title="Territories" icon="map" href="/territories/territories">
    Group members into pools and distribute leads across them.
  </Card>

  <Card title="Capacities" icon="gauge" href="/territories/capacities">
    Cap how many records each member receives within a time window.
  </Card>

  <Card title="Salesforce integration" icon="cloud" href="/integration/salesforce">
    Connect your CRM to import team members automatically.
  </Card>

  <Card title="Build a play" icon="play" href="/plays/overview">
    Create workflows that trigger lead allocation.
  </Card>
</CardGroup>