RRecords Labs Help Center

Projects

A project groups chats, Creations, sources, and a team around one piece of work. Answers inside a project lean on the project's sources first and follow its AI instructions. Only members can see a project.

Creating a project

  1. Open Projects in the sidebar and click New project.

  2. Fill in the Name and an optional Brief ("One or two lines on what this project is for").

  3. Pick a Color and Icon.

  4. Choose a Retrieval scope: Project sources or All knowledge.

  5. Under Invite teammates, add people by name or email. They can see every chat inside.

  6. Click Create project.

Contributors and above can create projects. The creator becomes the owner. Color and icon cannot be changed later from the app; the name, brief, and AI instructions (Project context in Edit project) can.

The project page

The header shows the project name, counts of chats, Creations, and sources, a New chat button, and Project options (Edit project, Archive, Move to Trash). Five tabs:

  • Overview — the Project brief, the Project agent (new chats here open with it; existing chats keep theirs), the Retrieval scope toggle, AI instructions, and tiles for Chats, Creations, Sources, and Members with Recent chats.

  • Chats — chats shared with members. To bring an existing chat in, use Move to project from the chat's menu in the sidebar; you can move only your own chats, and only into projects where you can edit.

  • Creations — files and apps built from project chats. Each opens in Creations.

  • Sources — knowledge weighted in retrieval here. From knowledge picks existing items; Upload adds files that stay scoped to the project until you Promote them. Each source can be set to Exclude from answers or Include in answers, given a project label, or removed.

  • Members — people and teams with Can edit or Can view, pending invites, ownership transfer, and Leave project.

How a project changes answers

Start a chat with New chat on the project page. The chat carries a project chip in its header and uses the project's agent by default.

With Project sources scope, the project's sources are weighted first; answers still stay grounded in the wider knowledge, just focused. The project's AI instructions are read on every answer as guidance, not as a citable source. Files uploaded directly to the project are hidden from answers outside it.

With All knowledge scope, there is no boost and the AI instructions are not applied. Each chat keeps the scope it started with, so changing the project's scope affects new chats only.

Members and roles

  • Owner — created the project or was handed it. Only the owner can move the project to Trash, restore it, or transfer ownership.

  • Can edit — can chat, add sources, and edit Creations.

  • Can view — can read chats and Creations.

Members can read every chat in the project. Replying inside a chat someone else started requires that chat's owner to share it with Can respond; otherwise, start your own chat in the project. You cannot invite someone at a higher role than your own. Only the owner can change members' roles. People you invite by email address, rather than picking them from your organization, appear as Pending until they accept.

Archive and delete

Archive makes the project read-only; find it under Projects → Archived and Unarchive when needed. Move to Trash keeps it restorable for 30 days by default (an Admin can change this under Settings → Security → Data → Trash retention); answers stop using the project's sources and instructions immediately, and its chats and Creations keep working outside the project. The Trash view on the Projects page shows days left and a Restore button for owners.

Was this article helpful?
Related articles
Asking questions wellChat & creationsAPI changelogDevelopersAuthentication, keys and scopesDevelopersBrowser extensionDevelopers