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

# Manage your workspace

> Invite members, set their roles, cap their credits, and organize people and projects into teams on Enterprise.

A workspace is your organization in Preview: its members, its projects, and its credit balance. Admins manage who's in it and what they can do.

> [!NOTE]
>
> Managing members needs the **Admin** role. Everyone else sees a read-only list of who's in the workspace and their roles.

## Roles

Every member has one workspace role. It sets what they can do across all of the workspace's projects.

| Role | What they can do |
| - | - |
| **Admin** | Everything: manage members, teams, billing, and workspace settings. Reaches every project and every team. |
| **Member** | Create, edit, share, and delete projects. Can't manage members or billing. |
| **Commenter** | Open projects and comment. Can't change anything. |
| **Viewer** | Open projects and read comments. Can't comment or change anything. |
| **Guest** | No workspace-wide access. Only sees the projects they were invited to through [Share](/preview/sharing#collaborator-invites). |

A few mechanics worth knowing:

* Someone invited to a single project who isn't in the workspace yet joins as a **Guest**. They drop out of the workspace on their own once they lose access to their last project.
* A project invite can raise someone's access on that one project, but never lowers what their workspace role already gives them.
* Only Admins see **Billing**, **Invoices**, and **Usage analytics**. See [Credits](/preview/purchase-credits).

## Add members

**1. Open Members**

In the sidebar, click **Team**. On Enterprise, click your workspace's name at the top of the sidebar instead, then **Members**.

**2. Invite**

Invite them by email and pick a role.

**3. Wait for them to accept**

They get an email invitation and show as pending until they accept.

From a member's **…** menu:

* **Change role**: takes effect right away, across every project.
* **Resend invite** / **Revoke invite**: for pending invitations.
* **Remove from workspace**: they lose access to the workspace and all its projects.

> [!TIP]
>
> Filter the list by role (and on Enterprise, by team) from the filter button beside search.

## Credit caps

Admins can cap how many credits any one member spends, so a single person can't drain the workspace balance.

* **Standard workspaces**: open the **Caps** tab on the Team page, click a member's cap, and pick a **Daily**, **Weekly**, **Monthly**, or **Yearly** window and an amount. **Unlimited** removes the cap.
* **Enterprise**: click **Adjust credit cap** on the member's row.

## Teams (Enterprise)

On Enterprise, split the workspace into teams: groups of members that share their own set of projects and their own credit cap. Use one per department, client, or production.

### How team access works

* A project belongs to at most one team, or to none.
* A team's projects are only visible to that team's members, Admins, and anyone invited to the project directly. Other members of the workspace don't see them.
* Team members can edit their team's projects, even if their workspace role is Commenter or Viewer. Only Admins can delete a team's project.
* Admins can open every team and its projects without being added.
* Projects with no team follow the workspace roles above.

### Create a team

**1. Start a new team**

In the sidebar's **Teams** section, click **+**.

**2. Name it**

Give it a name and, optionally, a description. Team names must be unique.

**3. Add members and projects**

Pick its members, then the projects that move into it. Both are optional and can be changed later.

Everyone sees the teams they're in under **Teams** in the sidebar. Admins see every team.

### Manage a team

Open a team from the sidebar to see its projects, its members, and its remaining credit. Team members who can create projects can start one right in it with **New project**.

Admins manage the team from the **…** menu at the top of its page:

* **Add projects**: move existing projects into the team. A project already in another team moves out of it.
* **Edit**: rename it or change its description.
* **Duplicate**: copies the team's name, description, and members, but not its projects.
* **Manage members**: add or remove people.
* **Copy link**: a direct link to the team's page.
* **Delete**: members keep their workspace access. If the team still has projects, choose to move them to another team, move them to no team, or delete them along with the team.

> [!TIP]
>
> To move a single project, use **Move to…** from its card's menu on the team page. To change one person's teams, click the **Team** column on their row in **Members**.

### Team credit caps

Click **Adjust credit** on a team's page to cap what the whole team can spend from the workspace balance. The cap runs per calendar year, and **Remaining credit** on the team's page shows what's left.


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