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

# Members and permissions

> Invite colleagues, assign member, editor and manager roles, and distinguish project, Assistant, group and file access.

Project permissions control who can read shared materials, edit work and manage collaboration resources. Use **Configuration → Manage members** to add people, change roles or remove members.

## Roles

These capabilities apply to ordinary operations in an active project. Business applications can impose additional rules on the objects they manage.

| Role | Read project and materials | Use connected, authorized Assistants | Edit files, instructions, skills and ordinary tasks | Manage members, Assistants, team connectors and scheduled tasks |
| - | - | - | - | - |
| Owner | Yes | Yes | Yes | Yes |
| Manager | Yes | Yes | Yes | Yes |
| Editor | Yes | Yes | Yes | No |
| Member | Yes | Yes | No | No |

Assistant use remains subject to publication, access authorization and tool availability. Members can participate, but project editing rights are required to change tasks or record acceptance decisions.

## Add organization members

1. An owner or manager opens **Manage members**.
2. Select an organization user and assign Member, Editor or Manager.
3. Save and confirm the role in the list.

People selected during project creation join as Members. A manager can subsequently grant editing rights where needed.

## Invite by email

A project manager with the corresponding organization invitation permission can enter an email address, choose a project role and send an invitation. The recipient must complete acceptance before becoming a member; a pending invitation does not grant access.

Review pending invitations in the dialog and revoke those no longer needed. If the email invitation entry is unavailable, check organization invitation permissions.

## Manage three separate relationships

| Relationship | What it controls |
| - | - |
| Human project membership and role | What a user can do in the project |
| Connected Assistants | Which Assistants can participate within the project |
| Group membership and selected project participants | Which group Assistants can receive formal task dispatches |

The group owner needs project management rights to connect an existing project. Joining a group does not make a user a project editor. Connecting an Assistant does not grant project members permission to edit that Assistant in Studio.

## Files, results and archived projects

Project files follow project access rules. Assistants, execution records and delivered files also enforce their own resource access. A visible historical card does not guarantee that its linked execution or download remains accessible.

Archived projects retain readable content but cannot be used, edited or managed. Manage the lifecycle of application-linked projects through the owning application. After membership or authorization is revoked, subsequent operations and automatic continuation recheck access; historical records do not grant continuing permission.

If a project is missing or unavailable, first check the organization and filters, then ask its manager to verify your membership and role. See [Troubleshooting](../help/troubleshooting).


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