# Add a teammate

Add a person when they need their own, accountable access to Forge. Give them an individual account and only the workspace membership they need. Shared accounts and shared passwords make it harder to understand who changed work and are not a safe substitute for membership.

## Check the person and workspace first

Open **Settings → Users** and confirm whether the person already has an active Forge account. An existing account can be granted workspace membership; a new person may need the account or invitation path used by your organisation. Check the workspace name carefully before changing access.

## Choose the smallest useful role

Forge workspace membership has three roles:

- **Viewer** can read workspace data but cannot modify it.
- **Editor** can make normal workspace changes.
- **Admin** can manage workspace settings and membership.

Choose the lowest role that enables the person's actual work. A workspace admin can manage ordinary membership, while platform-level administration has additional authority. Do not use a role change to work around a missing process or an unclear approval.

## Check and revoke access

After adding or changing access, ask the person to sign in with their own account and confirm the intended workspace appears. When access is no longer needed, remove that workspace membership. Removing membership does not require deleting the person's historic work.

## Prompts to try

```
List the members and roles for [workspace]. Identify who is an admin and do not change any access.
```

```
Before adding [person], show the workspace roles available and ask me to confirm the exact workspace and role. Do not create an account or grant access yet.
```

## Next steps

Review access whenever responsibilities change. If the request concerns another person's data, an account recovery or an uncertain deletion, use the privacy and recovery process first.

See [Privacy and recovery](/help/privacy-and-recovery) and [Connect your agent](/help/connect-mcp).