Teams and workspaces
Share one balance, one set of API keys and one bill with your team. Roles, invitations, seats, and how requests are attributed.
A workspace holds your credits, plan, API keys, monitors and webhook endpoints. Every account starts with a personal workspace. Invite teammates to a workspace and they spend the same balance and share the same bill, each with their own sign-in and their own keys.
Credits, plans and payment methods belong to one workspace and are billed to it. Credits can't be moved between workspaces yourself; if you bought credits in the wrong one, contact support and we can move them. The first-purchase bonus applies once per person, in their personal workspace.
Anyone in a workspace signs in with Google, GitHub, or email and password, and can add two-factor authentication (an authenticator app plus backup codes) from Settings.
Create a shared workspace
Your personal workspace is enough for working alone. A shared workspace is useful when a team, client or project needs its own balance and bill.
- Click the workspace name at the top left of the dashboard to open the workspace switcher.
- Choose New workspace.
- Type a Workspace name and create it. You're its owner.

A new workspace starts empty, with its own balance, keys and bill. You can own up to 5 shared workspaces besides your personal one, and create up to 3 in a day. Names must be 2 to 60 characters and can't include Social Fetch, Stripe or "official", imitate them with look-alike letters, or use a reserved name.
The switcher is also how you move between workspaces. All workspaces lists every one you belong to, along with any invitations waiting for you.
The Team page
Open Team in the top menu to see the workspace you're in: your role, how many seats are used, the members, and invitations that haven't been accepted yet.

Roles
| Role | What they can do |
|---|---|
| Owner | Everything, including billing, the plan, ownership and closing the workspace. |
| Admin | Manage people, API keys, monitors, webhooks and the workspace name, and buy credit packs. Can't change the plan, cards or auto-refill, and can't make anyone an owner. |
| Member | Use the API and the dashboard. Members manage only the keys, monitors and webhook endpoints they created. |
| Billing | See usage, buy credits and manage payment. Can't use the API and doesn't take a seat. |
A person can hold more than one role. A workspace always has at least one owner.
To change someone's role, open the menu at the end of their row under Members and choose Change role. Remove from workspace is in the same menu.
Custom roles
Workspaces with the custom roles add-on, and Enterprise workspaces, can add their own roles beside these four. An owner builds one under Team → Custom roles by ticking the permissions it should hold, then gives it to someone when inviting them or with Change role. Custom roles are an add-on on Scale ($49 a month), turned on from Billing → Add-ons, and included with Enterprise.
A custom role can grant API keys, monitors, webhooks, connected AI apps, usage, request logs, viewing billing and buying credit packs, the activity log, and seeing who is in the workspace. It can never grant workspace settings, adding or removing members, invitations, single sign-on, directory sync, managing the plan and cards, or exporting the activity log. Like Members, people with a custom role manage only their own keys, monitors and webhooks. A custom role that grants none of keys, monitors, webhooks or AI apps takes no seat. A role that someone still holds can't be deleted.
Invite a teammate
Owners and admins can invite people.
- Open Team and click Invite member at the top of Members.
- Type the person's Email address.
- Choose their Role, then click Send invitation.

The person gets an email with a link. They open it, sign in or sign up with the same address it was sent to (Google, GitHub, or email and password), and click Accept invitation. Someone signed in with a different email can't accept it. Invitations expire after 7 days.
Until it's accepted, the invitation waits under Pending invitations. Resend emails it again and restarts the 7 days; the earlier link stops working. Cancel withdraws it, and you can invite the person again later.

Workspaces with the single sign-on add-on on Scale, and Enterprise workspaces, can also add people through single sign-on and directory sync.
Seats
How many people a workspace can hold depends on its plan: just you on Pay as you go and Starter, up to 5 on Growth, and up to 25 on Scale. Enterprise contracts set their own limit. Buying credits doesn't add seats.
Need more seats on Growth or Scale? An owner can add them from Billing → Add-ons with the Extra seats add-on. It costs $5 a month per seat, or $54 a year, and you can buy up to 100 extra seats yourself. Contact us if you need more than that.
More seats are charged now, prorated for the rest of the billing period. Fewer seats are credited on your next invoice, and you can't go below the number of seats in use. Pay as you go and Starter are single-seat plans and can't buy extra seats.
Every member and pending invitation uses a seat. The Billing role never does, so you can add someone to handle invoices even when the workspace is full.
If you move to a plan with fewer seats than people in the workspace, or cancel to Pay as you go, you're asked to confirm first. Nobody is removed, but you can't invite anyone new until you're back within the limit.
API keys and spending
Keys belong to the person who created them and act in the workspace they were created in. Requests made with a key spend that workspace's credits, and GET /v1/balance returns that workspace's balance. GET /v1/whoami always returns a workspace object (id, name, role, isPersonal) saying which workspace the key acts in.
Once more than one person or key has made requests, Usage shows spend by teammate and by key, and Export CSV downloads it.
Owners and admins can cap what one key spends in a calendar month: on API Keys, click Limit on the key's row and set Credits per month.

A key at its limit is refused with 402 insufficient_credits and a message saying it has reached its monthly limit. Your balance isn't touched.
When someone leaves a workspace, the keys they made for it stop working straight away. Requests with them get 403 forbidden with a reason field:
reason | Meaning |
|---|---|
key_owner_removed | The person who created the key is no longer in the workspace. Create a new key. |
key_owner_role | The role of the person who created the key no longer allows API use (for example Billing). Create a new key as someone whose role does. |
workspace_suspended | The workspace has been suspended. |
workspace_deleted | The workspace no longer exists. |
workspace_unavailable | The workspace can't be used right now. Contact support. |
AI apps (MCP)
If you belong to more than one workspace, you choose which one an AI app spends from when you connect it. Requests from that app use that workspace's credits. Removing someone from a workspace also disconnects their AI apps from it.
Monitors and webhooks
Monitors and webhook endpoints belong to the workspace and are billed to it. Owners and admins manage all of them; members manage their own. The HTTP API for monitors and webhooks needs an owner or admin key; members use the dashboard.
A monitor created with an API key follows that key. Its checks count against the key's monthly limit and are skipped, with a notice, when the limit is reached. If the key is deleted, disabled or expires, the monitor is paused with a notice; resume it to run on the workspace's credits. Monitors created in the dashboard aren't tied to a key.
Activity log
Owners and admins can see who invited, removed or changed the role of a teammate, and when. Open Team and click Activity log at the top right.

Entries are deleted after 90 days, or a year on Scale.
Leave, hand over or close a workspace
Anyone can leave a shared workspace, except its only owner.
To hand a shared workspace over, an owner chooses Transfer ownership from a member's menu or from Danger zone at the bottom of Team. The new owner must already be a member; you stay on as an admin. The previous owner's saved cards are removed from the workspace and auto-refill is turned off, so the new owner must add a payment method; until they do, subscription renewals fail.
To close a shared workspace, an owner chooses Close workspace under Danger zone, types the workspace's name and, if it still has credits, ticks the box agreeing that they'll be forfeited. The person who created the workspace can close it straight away while they're an owner. Any other owner sees Request close instead: the creator can decline the request, and it can be confirmed 24 hours after it was made. A closed workspace can be restored for 30 days; within that time an owner can contact support to restore it or move its credits. After that its remaining credits are forfeited.
Closing a workspace, transferring ownership and similar sensitive actions need a sign-in from the last 10 minutes. If it's been longer, you're asked to Sign in again first.
An account can't be deleted while its personal workspace still has teammates, or while it's the only owner of a shared workspace. Remove the teammates, or transfer or close the shared workspace, first.
Troubleshooting
What each Ad Tracker message means and what to do: brands that won't match, checks waiting for credits, missing ads or files, briefs, exports, emails, webhooks and team access.
Single sign-on and directory sync
Let a team sign in with its company identity provider and keep membership in step with your directory, using OpenID Connect and SCIM 2.0