> 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/structural.md).

# Structural

The Tonic Structural platform creates safe, realistic datasets to use in staging environments or for local development. Structural can be deployed either:

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

## Documentation

For comprehensive Structural feature documentation, go to the [Structural User Guide](/app/readme.md).

## Audit logs

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

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

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

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

[How to share logs with Tonic.ai](/app/admin/tonic-monitoring-logging/sharing-logs-with-tonic.md)

## Role-based access control (RBAC)

Structural supports a variety of user roles that allow customers to assign end-users the least privileges required.

Structural produces data products that might not require users to access the Tonic application at all.

[How to grant access to Structural workspaces](/app/workspace/workspace-access-management/workspace-sharing.md)

## Single sign-on (SSO)

Structural supports a variety of external identity providers that allow customers to:

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

Structural supports:

* AWS SSO
* Azure Active Directory
* Duo Security SSO
* Google Workspace SSO
* Keycloak
* Okta
* PingID
* Other SAML 2.0 compliant identity providers
* Other OIDC compliant identity providers

[Single sign-on (SSO) in Structural](/app/structural-user-access/single-sign-on.md)

## Password encryption

The Structural application hashes all user passwords when stored.

## Data encrypted at-rest

The Structural application encrypts datastore credentials using customer-provided encryption keys.


---

# 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/structural.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.
