> 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/features/projects.md). # Projects In the Projects tab, the user can learn about project work capabilities in the system. Projects make it possible to organize documents by cases, clients, departments, or other work areas. In [**the project list view**](/en/features/projects/project-list.md) projects created by the user, projects to which they have been assigned, as well as an individual document space created by Quick Anonymization, are displayed. Each project shows basic information such as its name, creation date, and the number of documents it contains. The list can be sorted and filtered, which makes it easier to find the right workspace. [**Project view**](/en/features/projects/project.md) allows work with documents assigned to the selected space. From this level, the user can add new files, open documents, check their status, assign tags, sort and filter the content, and switch the display mode between icon and list views. Project settings include information about its name, description, assigned team, creation date, number of documents, and used tags. The ability to edit individual settings depends on the user's permissions. The section also covers creating and deleting projects, various ways of adding documents, and user access rules. Thanks to projects, documents can be organized by clients, cases, proceedings, departments, or other areas of the organization's activity. --- # 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/features/projects.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.