Collaborate in projects
Projects bring members, files, agents and conversations together for a shared piece of work. The feature must be enabled on your instance. The projects you can see depend on your membership and role.
Project creation with both collaboration types
Example instance with sample data. Available controls depend on your role and configuration.
Create a project
- Open Projects.
- Select New project.
- Enter a name and optional description.
- Choose the project type carefully.
- Create the project, then add members under Members.
| Project type | Conversations | Files |
|---|---|---|
| File sharing | Conversations are private by default. Their owner can explicitly share them in the project. | Project files are shared with members. |
| Fully shared | Project members can see project conversations. | Project files are shared with members. |
The type determines conversation visibility, so check it before starting confidential work. The creation dialog explains the reach.
Work in a project
Open a project card. Its detail view contains the available areas for conversations, files, agents and members. Select New Conversation under Conversations to start in the project context. The header shows the project name and type. In File sharing projects, use Share in project on a conversation you own when members should see it. You can remove that project sharing again; review any separate direct sharing too.
Project files keep document retrieval within the intended working area. An assigned agent keeps its own instructions and tools; it still needs an available model, approved tools and any required personal integration connections.
Members and roles
Open Members to see who belongs to the project. Project roles apply within that project, independently of an instance-wide administrator role.
| Project role | Available management actions |
|---|---|
| Owner | Maintains members, changes member/admin roles, manages assignments and can delete the project. |
| Admin | Helps manage files and agents and can add people or remove ordinary members. Cannot remove the owner or another admin through the member controls. |
| Member | Uses the project's accessible content; does not manage membership or settings. |
To add someone, search the account by name or email under Members, choose the offered project role and select Add member. The person must belong to the permitted workspace. This adds access to an existing account; it is not a way to create a new account or invite an arbitrary external address. Trial workspaces can be restricted to one person.
Only the owner can change another non-owner's project role. Remove people who no longer need access, then review separately shared chats and agents. Removing project membership cannot retrieve content already copied or downloaded.
Assign agents
Use the add action in the project's agent area. The picker contains only agents that you can see and assign. Only a private agent's owner can assign that agent. The confirmation explains the effect of sharing it in the project. Membership of somebody else's private agent is insufficient. Global or configuration-provided agents can be assigned where your project role permits. Removing a project assignment does not delete the original agent.
Files attached to a project
Example instance with sample data. Available controls depend on your role and configuration.
Manage files
- Open the project's Files area.
- Use Attach existing file to select a file already in your account, or use the upload area to add a new file.
- Check its processing state before asking about it. Partial or Truncated means that some content is missing from search.
- Start a conversation from the project so the project context is applied.
Project management controls allow files to be removed from the assignment. Removing an assignment is different from deleting the file itself under Files. Check both the intended audience and the correct action before removing material.
Project settings
Owners and project admins see Settings. Its document-processing controls can inherit instance settings or override how project knowledge is divided for search. They are technical retrieval settings, not a control for who can see conversations. Keep inherited values unless a specific retrieval problem justifies a change, and ask the administrator how existing files should be reprocessed.
The owner can delete the project from Members, after confirmation. Before doing so, identify the conversations and files you still need and review their separate retention and sharing. Deleting a project is not a substitute for deleting every underlying file or downloaded copy.
Troubleshooting
- The project is missing: Check membership or whether Projects is enabled.
- Colleagues cannot see a chat: Check whether the type is File sharing rather than Fully shared.
- An agent cannot be added: You lack access or the administrator restricts its reach.
- A file is not found: Check project assignment, Ready and File search.
- Members cannot be changed: This action is limited to project managers or administrators.