# Your Team

> List your Mojeeb teammates and who can be assigned an agent's leads and conversations, with GET /v1/agents/{agentId}/members and GET /v1/organization/members. Read-only.

Two read-only calls show who is on your team. `GET /v1/agents/{agentId}/members` lists everyone and whether each can open the agent, and `GET /v1/organization/members` lists everyone with their role and the agents each can open. Use them to route leads to the right person, to show a name for a lead's `assigned_to` or a note's author, and to match teammates to the owners in your CRM by email.

## How do I find who can be assigned an agent's leads?

Call `GET /v1/agents/{agentId}/members`.

```bash
curl https://api.mojeeb.app/v1/agents/YOUR_AGENT_ID/members \
  -H "Authorization: Bearer mk_live_YOUR_KEY_HERE"
```

Assign a lead only to someone with `can_open_agent: true`: only they can be given the agent's leads and conversations, and Mojeeb refuses anyone else with `422 assignee_not_allowed`. See [Lead Assignment, Filters and Fields](./lead-assignment-and-fields) for assigning, and the [List teammates for an agent reference](../api-reference/list-agent-members) for every field.

## How do I list everyone in my organization?

Call `GET /v1/organization/members`.

```bash
curl https://api.mojeeb.app/v1/organization/members \
  -H "Authorization: Bearer mk_live_YOUR_KEY_HERE"
```

Each member comes with their role, their email and the agents they can open: `all_agents: true` means every agent, including agents added later; otherwise `agent_ids` lists the agents they were given. See the [List your organization's members reference](../api-reference/list-organization-members).

## How do I show a name for `assigned_to` or a note's author?

A lead's `assigned_to` and a note's `author_id` are a teammate's `user_id`. Read the members list once, keep it, and look names up there. When an id isn't in your copy, read the list again: someone may have joined since. An id that still isn't listed belongs to someone who is no longer in your organization.

## Common questions

### Why isn't someone in the list?

Only members are listed: someone you invited appears once they accept. A lead or note can still carry the id of someone who has left your organization; reassign those leads to someone with `can_open_agent: true`.

### Why is `agent_ids` empty?

Either `all_agents` is `true`, which covers every agent, or the teammate was given no agent this key can act on. A key limited to some agents shows only those agents in `agent_ids`, so the teammate may have others.

### Why is a name or email null?

Not every account has one on record.

### Can I get my teammates' phone numbers?

No. The API returns each teammate's name, role and email, never a phone number.

### Can a key invite or remove teammates, or change what they can open?

No. Both calls are read-only. Manage your team on the **Team** page of the dashboard, as the owner or an admin with every agent; see [Team Management](/docs/features/team-management).

### Which scope do these calls need?

`team:read`, which every key holds today; see [Authentication](../authentication). A key can read your teammates' emails, so keep it on your servers.