> 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/dataset-configure-redaction/textual-datasets-synthesis-options.md). # Configuring entity type synthesis options {% hint style="info" %} **Required dataset permission:** Edit dataset settings {% endhint %} When Tonic Textual generates replacement values, those values are always consistent within the dataset. Consistency means that the same original value always produces the same replacement value. You can configure how Textual generates the replacement values for each entity type. You can also configure synthesis options from the [Textual Agent](/textual/textual-agent/textual-agent-about.md).


Enable consistency with Tonic Structural Generate the same values in both Textual and Structural.	Enabling consistency with Tonic Structural
Display the synthesis options Display the synthesis configuration panel for an entity type.	Displaying the synthesis options for an entity type
Provide replacement values Provide a single constant replacement value, or map original values to replacement values.	Providing specific replacement values
Synthesis options by entity type Configure additional synthesis options for specific built-in entity types.	Synthesis options for specific entity types
Configure synthesis for custom entity types Select and configure the generator to use to synthesize values for a custom entity type.	Setting the generator for custom entity types

--- # 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/dataset-configure-redaction/textual-datasets-synthesis-options.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.