> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/textual/guided-redaction/redaction-project-create-manage.md). # Creating and managing guided redaction projects ## Setting up projects


View the projects list View the list of guided redaction projects.	Viewing the list of guided redaction projects
Create a project Start a new guided redaction project.	Creating a guided redaction project
Set the project status Track the status of a guided redaction project.	Setting the project status
Assign tags to a project Use tags to further identify a guided redaction project.	Assigning tags to a project
Change the project name and description Give a guided redaction project a new name and add a more detailed description.	Changing the project name and description
Delete a project Remove a guided redaction project.	Deleting a project

## Configure entity types and access


Set the active entity types and values Identify the entity types to scan for. Add and exclude specific values.	Enabling and disabling entity types and values
Share access to a project Add users or groups to a guided redaction 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://docs.tonic.ai/textual/guided-redaction/redaction-project-create-manage.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.