# Team and roles

> Invite teammates to your org and see what org admins and members can each do.

Everyone on your team works inside one **organization**. Each person has one of two roles there: **admin** or **member**. This page covers inviting people and what each role can do.

## Invite a teammate

**Step 1: Open the members page**

Go to **Org settings → Members** (org admins only).

**Step 2: Send an invitation**

Enter their email and choose a role. They get an email with an invite link and a notification if they already have an account.

**Step 3: They accept**

The link opens an accept or decline page. Accepting gives them access to the org straight away.

Invitations expire. If a link has expired, re-send it from **Org settings → Members → Invitations**. Your plan sets how many members an org can have; see [Plans and limits](https://www.trackagoat.com/docs/guides/limits.md).

## What each role can do

| | Member | Admin |
|---|:---:|:---:|
| See every project, creator, video, campaign and goal in the org | ✓ | ✓ |
| View payouts and the payout tracker | ✓ | ✓ |
| Approve posts in the Inbox, edit campaigns and the notes on creators, videos and campaigns | ✓ | ✓ |
| Edit the organization, project and payout documents | | ✓ |
| Record and void payments, unassign payout structures | | ✓ |
| Remove creators and videos, delete campaigns | | ✓ |
| Re-enable auto-disabled creators | | ✓ |
| Trigger **Update Now** and change update intervals | | ✓ |
| Create, change or reveal the PIN of a creator page | | ✓ |
| Invite and remove members, change roles | | ✓ |
| Create and revoke API keys | | ✓ |
| Get scraping, privacy and limit notifications | | ✓ |

Admin rights apply across every project in the org.

## API keys and roles

An API key acts as one member: the admin who created it, or the member the admin picked under **Acts as**. Everything the key does is attributed to that member, and it can never do more than they can in the table above. If that member is removed from the org, the key stops working. A key an admin made for someone else also stops working when that admin leaves, is changed to member or is suspended, since they have seen it. If the member a key acts as is changed from admin to member, the key loses admin-only actions. See [Authentication and API keys](https://www.trackagoat.com/docs/api-reference/authentication.md#who-a-key-acts-as).

> **Tip:**
>
> For a teammate's coding agent, have them sign in over MCP with their own account, or create a key that acts as them. For long-running integrations, have an admin who will stay in the org create the key, acting as a member who will stay too.

## READMEs

Every member has a README, their personalization document: who they are, their job in the program and how they want AI agents to help. Edit yours in **Settings → My README**. Everyone in the org, and their agents, can read every member's README, as well as the organization, project, campaign, creator, video and payout documents, so keep anything private out of them. Only you can edit your own. Your teammates' READMEs are listed on the organization's README page. On every README page (yours, the organization's, a project's, a campaign's, a creator's or a video's), if the document changes while you're editing it, saving stops and asks you to reload, and your unsaved draft is kept so you can copy it back in. See [Notes and documents](https://www.trackagoat.com/docs/agents/notes.md).

## More than one org

You can belong to several orgs, with a different role in each. Switch between them from the app sidebar. Your plan's **orgs per user** limit caps how many orgs you can create.

---
Source: https://www.trackagoat.com/docs/guides/team