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

# Members and roles

> Invite teammates to a Qodex project and choose whether they can only work inside it or also manage access and lifecycle settings.

# Members and roles

Each Qodex project has its own member list.

Inviting someone to one project does not give them access to every project in the workspace. This lets you share one app with a contractor, customer, or teammate without exposing unrelated projects.

## Sign in

Users can sign in with email, Google, or GitHub. Enterprise teams can also use Microsoft SSO, which a project admin configures in **Settings > SSO**.

If your project requires an extra email code at login, Qodex asks for the code after the normal sign-in step. This gives teams a project-level check before a user enters a workspace with scenarios, findings, auth profiles, and integrations.

## Roles

Qodex has two project roles: **Admin** and **Member**.

| Role | Best for | What they can do |
| - | - | - |
| Admin | People who manage the project. | Everything a member can do, plus manage teammates, integrations, plan, and project lifecycle. |
| Member | People who test, review, and triage. | Use the agent, run tests, edit scenarios, review findings, and update memory. |

Use **Member** by default. Use **Admin** only for people who should manage access, integrations, billing, or archiving.

## Admin permissions

Admins can:

* Invite teammates.
* Promote or demote roles.
* Remove teammates.
* Connect or disconnect integrations.
* Manage BYOK and project-level settings.
* Change the project plan.
* Archive the project.

## Member permissions

Members can:

* Read chats, scenarios, scripts, findings, and runs.
* Chat with the agent and start runs.
* Save and edit scenarios and scripts.
* Triage findings.
* Edit project memory.
* Create and rotate their own API keys for CI.

## Invite a teammate

**1. Open Team settings**

Open **Team** from the account menu at the bottom of the left navigation. Only admins see the invite form.

**2. Choose email and role**

Enter the teammate's email and select **Member** or **Admin**.

**3. Send the invite**

If they already have a Qodex account, they get access immediately. Otherwise they receive an invite email.

## Change a role

Open **Team** from the account menu at the bottom of the left navigation, choose the role next to a teammate, and select the new role.

Qodex does not allow a project to lose its last admin. Promote another admin before demoting or removing the final one.

## Remove a member or revoke an invitation

Open **Team** from the account menu at the bottom of the left navigation. As an admin, click **Remove** next to an active member and confirm **Remove**. Their access to this project is removed.

For a pending invitation, click **Revoke** and confirm **Remove**. The invite can no longer be used.

Qodex does not let the project have zero active members. Promote another admin before removing the final admin.

## Next steps

> [card] [Workspaces and projects](https://qodex.ai/docs/account-workspaces-and-projects.md)
>
> Understand the project boundary.

> [card] [Plans and pricing](https://qodex.ai/docs/account-plans-and-pricing.md)
>
> See which plan applies to a project.

> [card] [GitHub PR review](https://qodex.ai/docs/pr-review.md)
>
> Connect repos per project.

> [card] [BYOK](https://qodex.ai/docs/integrations-byok.md)
>
> Manage provider keys at the project level.


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