> 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/textual-install-administer/configuring-textual/enable-and-configure-textual-features.md). # Enable and configure Textual features The following configuration settings are used to enable and configure Textual features. ## Text and file storage and processing


Enable PDF and image processing	Enabling PDF and image processing
Enable dataset text search	Enabling dataset text search
Enable uploads	Setting the S3 bucket for file uploads and redactions
Required IAM role permissions for Amazon S3 Required permissions for specific uses of Amazon S3 in Textual.	Required IAM role permissions for Amazon S3

## LLM providers and models


Select a default LLM provider and model	Configuring the default LLM provider and model
Connect to LLM providers Configure and verify connections to the available LLM providers.	Configuring connections to LLM providers
Enable model-based custom entity types	Enabling model-based custom entity types
Enable the Textual Agent	Enabling the Textual Agent
Configure the Request Auditor	Configuring the Request Auditor

--- # 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/textual-install-administer/configuring-textual/enable-and-configure-textual-features.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.