> 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/permissions.md).

# Permissions

Member versus Owner permissions on a team workspace. Who can edit projects, who can manage seats, who can change billing.

A team has two roles: Member and Owner. Members can do the work; Owners can do the work plus manage the team. Pick the right role per teammate at invite time. To change it later, an Owner removes the member and reinvites them with the new role.

## Watch

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

![The Invite team members dialog: a box for pasting email addresses, Upload CSV, and the role dropdown open on Member and Owner, with Member checked](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-9c7980f89bac9c25aa2d84a8946954c4fe70e66e%2Finvite-role-selector-01.png?alt=media)

## What does what

| Action                                   | Member | Owner |
| ---------------------------------------- | ------ | ----- |
| Open and edit projects                   | ✓      | ✓     |
| Render against the team's credit balance | ✓      | ✓     |
| Save assets to Team Assets               | ✓      | ✓     |
| Save custom styles at team level         | ✓      | ✓     |
| Share projects via email                 | ✓      | ✓     |
| See the whole team's usage               | –      | ✓     |
| Invite new team members                  | –      | ✓     |
| Remove team members                      | –      | ✓     |
| Add or remove seats                      | –      | ✓     |
| Change the team's plan                   | –      | ✓     |
| Manage payment methods                   | –      | ✓     |
| Buy credit packs                         | –      | ✓     |
| Restrict models to US/EU hosting         | –      | ✓     |
| Delete the team                          | –      | ✓     |
| Transfer team ownership                  | –      | ✓     |

The split is intentional: Members work, Owners administer. Most agencies have one or two Owners (the agency principal, the office manager) and the rest of the team as Members.

Owner-only actions are enforced server-side, not only in the UI. A Member who hits a billing or team-settings API route directly is rejected with a 401; the role check runs at the API layer.

### Project ownership transfer is gated by the project creator, not by team role

One action that lives outside the Member / Owner table: **transferring a project's ownership** to another member of the same team is restricted to the **project creator**, regardless of team role. A team Owner who didn't create a specific project can't transfer it; the creator (the user whose ID is on `projects.created_by`) is the only role that can. The enforcement runs in the server action, not the UI alone. Projects cannot move between workspaces (see [Workspaces](https://help.intangible.ai/teams-and-billing/workspaces.md)). See [Project ownership](https://help.intangible.ai/teams-and-billing/project-ownership.md).

## Choosing the right role

For each teammate:

* **Owner** if they need to manage seats, billing, or other team members.
* **Member** if they only need to work in the team's projects.

The default at invite time is Member. Promote to Owner deliberately, not by default; an over-permissioned team is a quiet way to lose track of who can do what.

For agencies, the typical pattern:

* Agency principal: Owner.
* Office manager / ops lead: Owner (for seat management and billing).
* Creative leads, producers: Member.
* Individual contributors: Member.
* Contractors: Member with deliberate scope; remove when the engagement ends.

## Changing a role

Roles are set at invite time. There is no in-product way to change a member's role after they join the team. To move someone between Member and Owner, an existing Owner removes the member and reinvites them with the new role.

This is a known UX gap; expect it to be addressed when the team-admin surface gets its next pass.

## Multiple owners

A team can have multiple Owners. The setting is unrestricted in count; pick what makes sense for the team's actual administrative needs. Common arrangements:

* **One Owner** for solo-led teams.
* **Two Owners** for partner-led teams or agencies with a clear principal-and-ops split.
* **More than two Owners** when the team's administrative load is genuinely distributed.

All Owners have equal authority. There's no "primary Owner" with super-admin status; every Owner can manage seats, billing, and transfers identically.

## Removing a member

Owner-only action.

1. Find the member's row.
2. Click the remove icon.
3. Confirm.

The member loses access to the team workspace immediately. Their authored projects remain in the team workspace; you can transfer ownership of specific projects via [Project ownership](https://help.intangible.ai/teams-and-billing/project-ownership.md) if needed.

A removed member's seat becomes available for a new invite. No partial-cycle refund.

## Hosting region

Some clients need their work kept on US or EU servers. An Owner can enforce that for the whole team with one switch.

1. Open the Team page from the team menu at the bottom left.
2. Find the **Hosting** section, above **Vendors**.
3. Turn on **Use only US/EU hosted servers**.

The switch reads "Hides models that run outside the US or EU from the visualizer for everyone on the team." With it on, the Singapore-hosted models drop out of every model picker for every member: all the Kling models, Wan 3.0, (SG) Seedance 2.5, (SG) Seedance 2.0 and Seedance 2.0 Mini for video, and Seedream 5 Pro for images. The US and German models stay, including (US) Seedance 2.5 and (US) Seedance 2.0. The pickers update without a reload. Turn the switch off to bring the hidden models back. See [Models](https://help.intangible.ai/visualize/ai-models.md#where-each-model-is-hosted) for where each model runs.

![The Hosting section on the Team page: the Use only US/EU hosted servers switch, off, with its description "Hides models that run outside the US or EU from the visualizer for everyone on the team." and the Vendors section below](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-d165e43fd1f3667ac22348608aeda8c0579707d4%2Fteam-hosting-region-01.png?alt=media)

The section appears only to Owners, and only on a shared team. A personal workspace has no Hosting section and always lists every model.

{% hint style="warning" %}
**The rule fails closed.** A model with no recorded hosting region is treated as outside the US and EU and hidden. New models can be missing from the picker on a US/EU-only team until Intangible records where they run.
{% endhint %}

A shot that was generated on a model the switch now hides keeps its record. When you regenerate it, a banner names the blocked model and a different model is selected for the new render.

## Limits and known issues

* **No granular permissions today.** A Member can edit any project in the team workspace, not just specific ones. Per-project access controls aren't exposed in the current UI.
* **No "view only" role.** Anyone in the workspace is at minimum a Member with edit access. For external reviewers who shouldn't edit, share the project via the email-share flow ([Sharing and collaboration](https://help.intangible.ai/learn-more/reference/sharing-and-collaboration.md)) without adding them as a member.
* **The last Owner cannot demote themselves to Member.** Self-demotion of the last Owner is blocked at the UI, server action, and RLS policy layers; the only path is to invite another Owner first, or delete the team entirely. Every team needs at least one Owner at all times.
* **No in-product role change today.** Roles are set at invite. To change a member's role, an Owner removes and reinvites them at the new role. See **Changing a role** above.

## Related

* [Workspaces](https://help.intangible.ai/teams-and-billing/workspaces.md)
* [Create and invite](https://help.intangible.ai/teams-and-billing/create-and-invite.md)
* [Project ownership](https://help.intangible.ai/teams-and-billing/project-ownership.md)
* [Sharing and collaboration](https://help.intangible.ai/learn-more/reference/sharing-and-collaboration.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/permissions.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.
