> 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/trust-center/tonic.ai-applications/textual.md).

# Textual

Tonic Textual provides a single tool to allow you to put your file-based data to work for you.

You can also use Textual to do simple redaction and synthesis of sensitive values, to produce files in the same format to use for development and training. Each original file becomes an output file in the same format, with the sensitive values replaced. 

Textual can be deployed either:

* Self-hosted by the customer
* In Tonic Cloud, which is a managed service that Tonic.ai provides

## Documentation

For comprehensive feature documentation for Textual, go to the [Textual User Guide](/textual/tonic-textual-guide.md).

## Audit logs

The Textual application saves log files that can be used to:

* Diagnose issues
* Troubleshoot bugs
* Help to identify when performance can be improved
* Generally improve Textual and its features

On-premise customers can aggregate these logs into their logging solution or SEIM for analysis and monitoring.

Customers can also share logs with Tonic.ai so that our staff can help to handle errors.

## Single sign-on (SSO)

For self-hosted instances, Textual supports a variety of external identity providers that allow customers to:

* Centrally manage users
* Define authentication criteria to log in to Textual

Textual supports:

* Azure Active Directory
* Github
* Google Workspace SSO
* Okta

[Single sign-on (SSO) for Textual](/textual/textual-install-administer/user-access-textual/textual-sso.md)

## Password encryption

The Textual application hashes all stored user passwords.


---

# 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/trust-center/tonic.ai-applications/textual.md?ask=<question>&goal=<user_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.