> For the complete documentation index, see [llms.txt](https://docs.smaq.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.smaq.io/documentation/projects/manage-project-members.md).

# Manage project members

Every project has its own member list, separate from organization-level membership. Someone in your org can be a member of one project but not another — useful for agencies with multiple clients, and for teams that need information walls between business units.

> **\[Screenshot needed]** Project Management tab in Settings showing current members with their roles, pending invitations, and the invite form.

### Two pages in this section

* [Invite team members](/documentation/projects/manage-project-members/invite-team-members.md) — how to add people to a project.
* [Member roles and access](/documentation/projects/manage-project-members/member-roles-and-access.md) — what each role can and can't do.

### Quick reference

| To...                         | Do this                                                                                      |
| ----------------------------- | -------------------------------------------------------------------------------------------- |
| Invite someone to a project   | [Invite team members](/documentation/projects/manage-project-members/invite-team-members.md) |
| Change someone's role         | Settings → Project Management → click the member → change role                               |
| Remove someone from a project | Settings → Project Management → click the member → Remove                                    |
| Resend an expired invitation  | Settings → Project Management → Project Invitation section → Resend                          |
| Revoke a pending invitation   | Settings → Project Management → Project Invitation section → Revoke                          |

### Project vs Organization members

* **Project members** are added per-project. Their role controls what they can do **inside that project**.
* **Organization members** are added at the org level — typically your team. Org membership is required to access any project in the org, but doesn't automatically grant project access.

So the flow for adding a new teammate is:

1. Invite to the org (Owner action — see [Organization → Members & invitations](/documentation/organization/members.md)).
2. Invite to each project they need to work on, with a project-level role.

For external clients, you only invite them to the relevant project(s) — no org-level membership required.

### Roles overview

Five user-assignable roles, in order of access (most → least):

1. **Owner** — full access including billing
2. **Editor** — full content access
3. **Member** — read + chat
4. **Viewer** — read-only
5. **Chat User** — chat-only

There's also a sixth internal role (Demo Viewer) used for SMAQ demo accounts. It's not assignable through the invite UI.

See [Member roles and access](/documentation/projects/manage-project-members/member-roles-and-access.md) for the full permission breakdown.