> For the complete documentation index, see [llms.txt](https://docs.trustlogix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trustlogix.io/configurations/tenant-settings.md).

# Tenant Settings

Tenant settings are organization level settings that deal with cloud resource creation as well as data encryption.&#x20;

The following settings deal with cloud resource creation and they can be turned on or off using the toggle button.

1. Deploy Access Analyzer Resources
2. Deploy Access Governance Resources
3. Deploy Monitoring Resources
4. Deploy Real-Time Monitoring&#x20;

The following setting deals with data encryption at REST and it can be turned on using the toggle button and by providing the cloud provider specific encryption key

1. Encryption Key

NOTE : The Encryption Key toggle button cannot be turned off from the TrustLogix console.


---

# 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.trustlogix.io/configurations/tenant-settings.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.
