# Teams and People

## What this is

This page explains how to manage team spaces, workspace members, and invites.

## When to use it

Use it when onboarding teammates, changing team ownership, or reviewing access boundaries for Proteges.

## What you need first

* Access to **Settings**
* Permission to manage workspace membership

## Steps

### 1. Manage teams

From the Teams view, you can:

* Review all teams
* Add a team
* Rename a team
* Remove a team
* Switch the active team context

### 2. Manage people

From the People view, you can:

* Invite a person by email
* Choose an initial team
* Review accepted members
* Review pending invites
* Update which teams a person belongs to
* Review a person's workspace role

### 3. Keep ownership clear

For each live Protege, make sure:

* A team owns it
* The right people can review Audit and Event Feed
* Changes are visible to the people responsible for support

{% hint style="warning" %}
Avoid orphaned automations. A Protege should always have a clear team boundary and at least one accountable owner.
{% endhint %}

## How to verify

* The intended teammate appears in the right team
* Pending invites match your expectations
* Team boundaries align with Protege ownership
* The active team context matches the Proteges and integrations you are reviewing

## Common failures

* Inviting a user to the wrong team
* Treating workspace access as the same thing as workflow ownership
* Deleting or changing teams without reviewing Protege ownership
* Editing team access while viewing the wrong active team

## Next step

* [Workspace settings](/workspace-settings.md)
* [Security and permissions](/workspace-settings/security-and-permissions.md)


---

# Agent Instructions: 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:

```
GET https://docs.tryprotege.com/workspace-settings/teams-and-people.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.