> For the complete documentation index, see [llms.txt](https://bluurdoc.bluur.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bluurdoc.bluur.ai/en/getting-started/quick-start/key-features/project-work.md). # Project work Projects are used to organize documents and enable collaboration among multiple users within separate workspaces. [**Project**](/en/features/projects.md) may correspond to a specific case, client, proceeding, department, team, or another area of the organization's activity. Projects are used to organize documents and enable user collaboration within separate workspaces. A project may correspond to a specific case, client, proceeding, department, team, or another area of the organization's activity. Documents can be added to a project, users can be assigned, and joint work on classification and anonymization can be carried out. The user sees the projects they have created as well as the projects they have been assigned to. Only people authorized to work in a given workspace, according to their access rights, have access to the documents. Project work makes it easier to organize a larger number of documents, distribute responsibility, and maintain continuity of work among users. Detailed information can be found in the sections [**Project list view**](/en/features/projects/project-list.md) and [**Project view**](/en/features/projects/project.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://bluurdoc.bluur.ai/en/getting-started/quick-start/key-features/project-work.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.