> For the complete documentation index, see [llms.txt](https://help.intangible.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.intangible.ai/teams-and-billing/create-and-invite.md).

# Create and invite

Make a team, add seats, send invites. The full setup flow for a multi-user workspace from scratch.

Go from working solo to a team that shares one workspace: create the team, add a seat for each person, invite them by email, and set what each of them can do.

## Watch

{% embed url="<https://www.youtube.com/watch?v=GnBAbs3TmiM>" %}

## What it does

Bundles three things that used to be separate flows: create team, manage seats, send invites. They happen in the same panel, in order, so the setup feels like one task instead of three.

## How to do it

{% stepper %}
{% step %}

### Open the Team page

Click **Team** at the bottom of the left sidebar, then click **Create team**.
{% endstep %}

{% step %}

### Name the team

Use the actual name you'll refer to it as. "Acme Agency", "L'Oreal Q2 Campaign", "Internal R\&D". The name shows up in the workspace dropdown for every member.

![Create New Team modal with a team name typed in the Name field](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-7516974c85e1b8cbbccf50bbb4813a988fb87e36%2Fcreate-team-modal-01.png?alt=media)
{% endstep %}

{% step %}

### Upgrade to Business if you haven't

Multi-seat teams require a Business plan, and the flow prompts you to upgrade if your account isn't on one. Pick monthly or annual (annual carries a discount). Either way, a team's first subscription starts with a free trial. Card details get stored against the Business account.

See [Plans and billing](https://help.intangible.ai/teams-and-billing/plans-and-billing.md) for tier details.
{% endstep %}

{% step %}

### Add seats

The **Seats** section shows the current count and a stepper to change it. One seat per person you want on the team. Seats add to the Business plan's per-seat billing. Every add opens a confirm dialog with the exact charge, tax and discounts included, before your card is charged.

On a free trial, the trial covers one seat. Adding a second seat ends the trial on the spot; see [Adding seats during a free trial](#adding-seats-during-a-free-trial) before you add one.
{% endstep %}

{% step %}

### Invite teammates

**Add Member** opens the **Invite team members** dialog. It takes a list, not one address at a time:

* **Paste** addresses separated by commas, semicolons, spaces or new lines. Entries like `Sam Lee <sam@company.com>` work; the name is ignored.
* **Upload CSV** reads a .csv or .txt file under 1 MB. Only the cells containing an email address count, so a spreadsheet export with names and headers works as it is.

Before you send, the dialog shows how many people will be invited and lists anything under **Needs attention**: **Invalid email**, **Listed more than once**, **Already on the team**, or **Invite already pending**. Those are skipped, and don't count against the limits below.

![The Invite team members dialog with three addresses pasted: two will be invited, and one is listed under Needs attention as Already on the team. The Role select (Member) sits beside Upload CSV, and the button reads Send 2 invites](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-a232f2a1d9b6146d0f6300c44042f25044be8d06%2Finvite-members-bulk-01.png?alt=media)

Pick one role for the whole batch: Member or Owner.

* **Member** – can edit projects in the team, view shared assets, render against the team's credit balance. Can't manage the team's settings or billing.
* **Owner** – everything a Member can do, plus manage seats, invite or remove others, change the team's plan, modify billing.

Pick Owner for collaborators you trust with the team's settings. Pick Member for everyone else.
{% endstep %}

{% step %}

### Send

The send button counts the invites, such as **Send 3 invites**. It stays disabled when the list needs more seats than the team has open (**Not enough seats**), when it holds more than 100 new invites, or when more than 500 addresses were pasted at once.

The invites email out. If every one went, a toast confirms and the dialog closes. If any failed, the dialog stays open with a result per address and an **Invite more** button. An address that reads **Email failed. Revoke the pending invite, then try again** already has a pending invite: revoke it from the member list and resend.

Each invitee gets a link to accept; once they click and sign in, they appear in the team's member list and can switch into the team workspace.
{% endstep %}
{% endstepper %}

## Adding more seats later

Anytime, from the **Seats** section on the Team page. Set the new count with the stepper, then click the button below it.

* **Adding seats** charges your card today for the rest of the current billing period. A dialog titled **Add N seats?** shows the exact amount before you pay; click **Pay and add N seats** to confirm. The added seats count toward credit allocation from the next billing period.
* **Removing seats** is scheduled, not immediate. The button reads **Schedule removal of N seats**, and the change takes effect at the end of the current period with no partial refund.
* **You can't go below the people on the team.** The floor is your members plus pending invites. Try to go lower and the section shows "Cannot go below N seats": remove members or revoke invites first.

If your card is declined, the whole seat change is rejected and your seat count stays where it was. You see the card error, and the seat count stays where it was.

### Adding seats during a free trial

A free trial includes one seat. Adding any more ends the trial today and starts your paid plan:

* A new billing period starts now. Every seat, including the first, is charged at the full price for that period. Nothing is prorated.
* Your trial credits are replaced by the full allowance for the new seat count.

The Seats section says so up front with a banner, "Your free trial includes 1 seat". When you raise the count, the breakdown shows an **Estimated charge today** before tax and discounts, and the button changes to **End trial and add N seats**. Clicking it opens **End your free trial?** with the exact charge; confirm with **End trial and pay**.

### When seat changes are locked

Seat changes are refused while a plan change is already scheduled. The Seats section shows one of two banners and disables the stepper:

* **Cancellation scheduled**: "Seat changes are unavailable while your subscription is set to cancel. Resume your plan to change seats."
* **Plan change scheduled**: "Seat changes are unavailable until your scheduled plan change takes effect or is cancelled."

This protects the scheduled change. Adding seats would otherwise bill you for seats on a plan you already chose to leave.

## Inviting more teammates later

Same panel. **Add Member** opens the same **Invite team members** dialog, with the same list, preview and Member / Owner choice as above.

To remove a member: their row in the member list has a remove icon. Confirms before removing; the seat becomes available for a new invite.

{% hint style="info" %}
Removing a member doesn't delete their work. Projects they authored remain in the team workspace. To transfer ownership of a specific project before removing the member, use [Project ownership](https://help.intangible.ai/teams-and-billing/project-ownership.md).
{% endhint %}

## Limits and known issues

* **Email invitations expire** if not accepted. Today the team admin UI doesn't surface expired state, so every invite shows **Pending** regardless of whether it's still valid. If an invite is past its window, revoke it from the same panel and reinvite.
* **Pending invites count against your seats.** A seat is reserved when you send the invite, not when the invitee accepts. Cancel the invite to free the seat. Expired-but-shown-as-Pending invites still count toward the allotment, so prune the list when you're managing seat capacity.
* **Cards that need extra verification can't add seats.** If your bank asks for 3D Secure on the charge, the add fails with "Your card needs extra verification, which seat changes cannot complete." Update your payment method in Stripe and try again.
* **Free and Explorer tiers cannot have multi-user teams.** The Business upgrade is the gate; there's no path around it for teams of two or more.

## Related

* [Workspaces](https://help.intangible.ai/teams-and-billing/workspaces.md)
* [Permissions](https://help.intangible.ai/teams-and-billing/permissions.md)
* [Plans and billing](https://help.intangible.ai/teams-and-billing/plans-and-billing.md)
* [Project ownership](https://help.intangible.ai/teams-and-billing/project-ownership.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.intangible.ai/teams-and-billing/create-and-invite.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
