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

> ## Agent Instructions
> Use the exact commands, endpoints, and product terms in these docs. Commands that start with `pctx` mean the Port of Context platform CLI installed from pctx.ai, not the open-source tool of the same name.

# People and roles

> Roles, invitations, joining by email domain, and teams.

Manage people under **Admin** → **Teams**. Only admins can open the Admin area.

## Roles

| Role | Can do |
| - | - |
| Admin | Everything a member can, plus manage people, teams, services, policies, and every node on the context map. Sees the **Admin** and **Curation** tabs. |
| Member | Use the gateway, add to the context map, add indexed sources, and suggest changes to nodes they do not own. |
| Reader | View only. Cannot add to the map or suggest changes. |

To change a role, open the **Members** card and pick a role from the dropdown on that person's row. The change applies to their next request. You cannot change your own role.

## How someone gets in

![Someone invited by an admin joins with the invited role. Someone with a work email on your domain joins as a Member. Anyone else with a work email starts their own workspace.](https://mintcdn.com/pctx-ai/WE3Xcw3fMJQ2fO1G/images/people-join-light.svg?fit=max\&auto=format\&n=WE3Xcw3fMJQ2fO1G\&q=85\&s=a2a6cb4e3565312f4592d8f7aba06780)

## Invite someone

1. On the **Members** card, select **Invite**.
2. Enter their work email and choose a role. Check the role before you send: the dialog starts on Admin.
3. Select **Send invite**, then copy the link. It is shown once.

Invitations follow these rules:

* The address must be a work email. Personal addresses are refused.
* The link works once and expires after 7 days.
* The person must sign in with the exact address you invited.

Open invitations are listed under **Pending invitations**, where you can **Revoke** them. An invitation sent from a team's page always gives the Member role.

## Joining by email domain

Your workspace's domain comes from the email address of the person who created it. After that:

* Someone who signs in with a verified address on that domain joins automatically as a Member, if a seat is free.
* If no seat is free, or their address is not verified, they send a request to join and wait.

Requests appear under **Requests to join**. Choose a role and select **Approve**, or select **Deny**. A person you deny does not join automatically later.

The Free plan has 5 seats. Team and Enterprise have no seat limit.

## Remove someone

Select **Remove** on their row. They lose access right away: their sessions end and their agents are signed out of the gateway.

Their Person entry stays on the context map and is reused if they rejoin. You cannot remove yourself, and a workspace always keeps at least one admin.

## Teams

A team is a Team entity on the context map. The **Teams** page is another view of the same teams, so one you add here appears on the map.

* **Create a team:** select **Add team** and name it.
* **Add people:** open the team and use **Add people** to search by name or email.
* **Delete a team:** this removes it from the context map along with its membership and its service access. It cannot be undone.

Adding a person who has no login puts them on the team on the map only. They still need an invitation to sign in.

Teams are used for two things: choosing [which services a team gets](https://docs.pctx.ai/administration/access-and-sharing.md), and sharing an indexed source or a map node with a team.


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