Learn how projects, source context, chats, review requests, and permissions fit together.
Projects organize work for a job. A project contains its own documents, Rus conversations, project memory, and QA/QC requests. Check the active project before uploading files or starting a review.
Context is the set of sources selected for a Rus conversation. Choose a code bundle, project document folders, and/or Firm Data folders that match your question. Project Memory can supply background, but it does not replace selecting code or folders to start a new chat. See Rus context.
Project Documents are files for one project. Firm Data is the organization's reusable document library. Wait for uploaded PDFs to finish processing before expecting their folders to be useful in Rus.
Chats hold questions and answers. A live share link lets eligible project members view a conversation; opening a project chat to the organization can let teammates participate. See Share a chat and Group chats.
QA/QC requests are separate from chats. Add a drawing package, choose checks, and run the request to produce review tickets. A saved draft has not started the run. See What is QA/QC?.
Your organization and project permissions determine which workspaces and actions you can use. A shared review grants access to that review according to its invitation; it does not grant every workspace in the host project.