> For the complete documentation index, see [llms.txt](https://vendorspace.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vendorspace.gitbook.io/docs/settings/team-management.md).

# Team management

As your events grow, you will likely need more people helping out. Vendor Space lets you invite team members and control exactly what each person can access.

***

## Inviting a Team Member

1. Go to **Settings** in the left sidebar.
2. Click the **Team** tab.
3. Click **Invite Member**.
4. Enter the person's email address.
5. Select a role from the dropdown.
6. Click **Send Invite**.

The invited person receives an email with a link to join your organization. Once they accept, they appear in your team list with their assigned role.

***

## Roles and Permissions

Vendor Space has four roles, each with a different level of access:

| Permission                     | Owner | Admin | Editor | Viewer |
| ------------------------------ | ----- | ----- | ------ | ------ |
| View events, vendors, and data | Yes   | Yes   | Yes    | Yes    |
| Create and edit events         | Yes   | Yes   | Yes    | No     |
| Create and edit vendors        | Yes   | Yes   | Yes    | No     |
| Send messages and emails       | Yes   | Yes   | Yes    | No     |
| Manage tasks and check-in      | Yes   | Yes   | Yes    | No     |
| Change organization settings   | Yes   | Yes   | No     | No     |
| Manage team members            | Yes   | Yes   | No     | No     |
| Connect and manage Stripe      | Yes   | Yes   | No     | No     |
| Access billing and plans       | Yes   | No    | No     | No     |

### Owner

Full access to everything, including billing and subscription management. Every organization has at least one Owner. This is typically the person who created the account.

### Admin

Same access as the Owner, except they cannot view or change billing and subscription details. Ideal for trusted team leads who help manage the entire operation.

### Editor

Can create and manage events, vendors, tasks, and communication -- but cannot change organization settings, manage the team, or access payment configuration. Great for team members who handle day-to-day event operations.

### Viewer

Read-only access to everything. Viewers can see events, vendors, documents, and analytics but cannot create, edit, or delete anything. Useful for stakeholders, sponsors, or part-time staff who need visibility without the ability to make changes.

***

## Managing Existing Members

From the **Team** tab in Settings, you can see all current members and their roles.

### Changing a Member's Role

1. Find the member in the team list.
2. Click the role dropdown next to their name.
3. Select the new role.
4. The change takes effect immediately.

### Removing a Member

1. Find the member in the team list.
2. Click **Remove** next to their name.
3. Confirm the removal.

Once removed, that person loses access to your organization immediately. Their past actions (created events, sent messages, etc.) remain in the system.

### Resending an Invite

If someone did not receive or lost their invitation email:

1. Find the pending invite in the team list.
2. Click **Resend Invite**.
3. A new invitation email is sent to the same address.

***

## Best Practices

* **Use the minimum role needed.** Give team members only the access they require. You can always upgrade a role later.
* **Keep at least two Owners or Admins.** This ensures someone can manage the account if the primary owner is unavailable.
* **Remove members promptly.** When someone leaves your team, remove their access right away to keep your account secure.
* **Use Viewer for volunteers.** Event-day volunteers often need to see vendor information but should not be able to change anything.

> **Tip:** Before a big event, review your team list to make sure everyone who needs access has it, and anyone who should not have access has been removed.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://vendorspace.gitbook.io/docs/settings/team-management.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.