> 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/project-list/creation.md).
# Creation
The user can create a new project and add documents intended for anonymization to it.
A project is a separate workspace where documents can be stored, analyzed, classification fields detected and edited, and anonymization performed.
To create a project, click the **Add project**.
The Add project button in the project list view.
In the displayed window:
* enter the project name;
* optionally add a description;
* select the users who should be granted access to the project.
* optionally assign **anonymization scheme**to be applied to documents in this project.
{% hint style="info" %}
**Important:** If an anonymization scheme is assigned to the project, when the document reaches the **Anonymization** stage, the system will automatically set the category sliders according to that scheme. The scheme assigned to the project takes priority over the global scheme.
{% endhint %}
After entering the data, confirm the changes with the appropriate button.
After completing the data, click the **Create project**. The project will be added to the list, and the assigned users will gain access to its workspace.
Window for creating a new project.
---
# 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/project-list/creation.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.
