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

# Team

> Invite your team, and who can do what.

Everyone in an organization sees the same lanes, leads and usage. One login works across Intent Leads and DBEE.

## Roles

| | Member | Owner |
| - | - | - |
| Lanes, keywords, checks, exports, leads | ✓ | ✓ |
| Standard API keys | ✓ | ✓ |
| Change plan, billing page | | ✓ |
| Invite people, change roles, remove people | | ✓ |
| Admin API keys | | ✓ |

An organization always keeps at least one owner: the last owner can't be removed or made a member.

## Invites

Invite people from **Team** in the dashboard, or with an admin key through `POST /api/v1/team/invites`:

```bash theme={"theme":{"light":"github-light","dark":"github-dark"}}
curl -X POST https://intentleads.si/api/v1/team/invites \
  -H "Authorization: Bearer $INTENT_LEADS_ADMIN_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email": "sam@example.com", "role": "member"}'
```

The response has a single-use invite link. Send it to the person yourself. The link:

* works once, then stops working;
* expires after 14 days;
* can be revoked any time before it's used (`DELETE /api/v1/team/invites/{id}`).

The person signs in or creates an account, accepts the terms, and joins your organization. The `email` on an invite is a note for you; whoever opens the link joins.

<Warning>
  Treat invite links like passwords until they're used. Anyone with the link can join your organization.
</Warning>

## Terms

Each person accepts the Intent Leads terms once: when they create an account, join through an invite, or first open the dashboard. The terms cover all use, in the dashboard and through the API, CLI and MCP. Read them at [intentleads.si/terms](https://intentleads.si/terms).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.