Getting started with Projects

Projects keeps the chats, files, knowledge bases, agents and skills for an engagement in one place. Use a project for work that shares the same sources and team, such as a client engagement, research topic or internal initiative.

Before you start: For enterprise workspaces, a tenant admin can enable it under Tenant settings → Feature Controls → Projects. Your workspace’s resource-sharing policies still apply.

1. Create your project

1. Open Projects from the sidebar and start a new project.
2. Give it a name your team will recognize.
3. Optionally, select agents or skills to share with the project. You can add them later.
4. Select Create.

You don’t need to build an agent before starting. Once the project exists, you can add sources, invite colleagues and start chatting.

2. Invite your colleagues

1. Open the project and select Share.
2. Enter your colleague’s email address or select a suggested colleague.
3. Choose their role and confirm.

• Member: Can chat in the project and add or remove project sources.
• Manager: Can also invite and remove people, change roles, manage project settings, and archive or delete the project.

Projects are members-only. Sending someone the project link doesn’t grant access; they must also be added to the project.

Check the audience: Project sources are shared with the project’s members. Only add material that everyone in that project is allowed to use.

3. Add files and knowledge bases

Open Knowledge bases from the project header. You can upload files, link an existing knowledge base or create a new one.

Upload files for this project

1. Select Upload files.
2. Select Choose files and pick the files from your device.
3. Wait for processing to finish and check that the files appear in the project.

These uploads are added to the project’s own knowledge base, making them reusable in project chats. Check any processing or availability warnings before asking the agent to work from them.

Link an existing knowledge base

1. Select Add existing.
2. Search for the knowledge base you want to use.
3. Select one or more knowledge bases, then confirm with the Link button.
4. Open a linked knowledge base from the project to browse its files.

Linking uses the existing knowledge base rather than creating a separate copy. You can link knowledge bases you own or can use through access granted to you, your team or your organization. Access available only through another project or an agent can’t be passed on this way.

Linked access depends on the person who added it: Project access to a linked knowledge base depends on that person remaining a member and retaining their underlying permissions. Linking can also allow members to browse or edit the original knowledge base where those permissions are available. Treat it as a shared resource, not an isolated project copy.

Create a new knowledge base

1. Select New knowledge base.
2. Complete the creation dialog.
3. After it’s linked, open it inside the project and add your material.

Use project uploads for engagement-specific files. Link an existing knowledge base when the team needs an established reference library.

4. Add and use agents or skills

1. Open Agents & skills from the project header.
2. Choose the Agents or Skills tab.
3. Select Add existing.
4. Find the resource and select Share. Its status changes to Shared.
5. Select Done.

To use a shared agent, select Chat on its card. Shared skills are available in the project chat’s skill picker; select the skill you need for the task. You can also create an agent or skill from this page where your workspace permissions allow it.

You can share your own agents and skills, plus eligible resources shared with you. For someone else’s resource, you need permission to both use it and read its configuration or instructions. Run-only access isn’t enough.

Know what you’re sharing: Project members can use shared agents and skills and inspect their configuration or instructions. Project sharing doesn’t grant permission to edit, delete or re-share the original resource. Using an agent or skill you own in a project chat can also share it with the project, even if that chat is private.

Adding an agent makes it available to the team. To start a chat with a particular agent, use its card or select it in the composer; don’t assume every agent added to the project runs automatically.

5. Start a chat and check its context

1. Return to the project’s main page and enter your question, or start from a shared agent’s card.
2. Check the selected agent before sending.
3. Open Show context to inspect the project material available to the chat.
4. Name the sources you want used and ask for citations when the answer needs supporting evidence.

For example:

Use the project’s interview files to summarize the recurring issues. Cite the supporting sources and tell me which files you couldn’t review.

Available sources aren’t proof that every file was read. For a review covering all documents, ask the agent to state what it consulted and identify missing or partial coverage.

6. Share conversations and build on a teammate’s work

New projects default to sharing newly started project chats with members. Check the Shared or Private label beside your conversation.

• To keep your conversation private, open its menu and select Make private.
• To share a private conversation, select Share with project.
• To build on a colleague’s shared conversation, open it and select Continue in my own chat.

Continuing creates a separate copy you can write in. Your colleague’s original conversation stays unchanged.

Quick checks when something’s missing

• Projects isn’t in the sidebar: Ask your tenant admin to check the Projects switch.
• A knowledge base isn’t listed: Search by name and check your underlying access. A knowledge base available only through another agent or project can’t be linked onward.
• An agent or skill isn’t available to share: Check that you can both use and read it. Run-only access won’t qualify.
• You can’t add sources or invite people: Check your project role, workspace sharing policy and whether the project is archived.
• A colleague can’t see a chat: Check that they’re a project member and that the chat is shared.
• A source stops working: Check its processing status and whether the person who linked it still has access and belongs to the project.