> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/trulyp/settings/advanced-settings.md).
# Advanced settings
Fine-tune system behaviour, rate limits, and feature flags.
The **Advanced settings** page is for administrators who need to configure system-wide behavior in Trulyp: AI features, security, diagnostics, HTTPS, data performance and Studio branding. You find it in **Settings** › **Advanced settings**.
Changes are not applied until you select **Save settings**. If you leave the page with unsaved changes, Trulyp asks you to confirm before leaving.
{% tabs %}
{% tab title="General" %}
#### AI features
Administrators see this section at the top of the **General** tab. It switches AI off for everyone in your Trulyp, independent of any [AI configuration](/trulyp/ai/getting-started.md).
**Disable AI in Trulyp**
Hides and blocks Vizzy, AI-assisted actions, dashboard generation and Studio authoring. The assistant on the home page and the **Ask Vizzy** button disappear, and so does the **Studio** tab of this page. If **Disable AI agents in Extensions** is still off, the **AI** menu remains and is called **Extension AI**.
Existing Studio apps stay available: you can still view them and download them as TREX files. Analytics apps and insights keep working, without the AI assistant.
**Default:** Disabled
**Disable AI agents in Extensions**
Blocks the AI agents that extensions such as SuperTables and PowerKPIs use. Studio extension management and the Vizzy assistant of Trulyp stay available.
**Default:** Disabled
{% hint style="info" %}
The two switches are independent. You can, for example, turn off AI agents in extensions and keep Vizzy.
{% endhint %}
#### User creation
**OAuth token host allowlist**
Restricts Snowflake OAuth token exchanges to trusted hosts.
Enter hostnames only, without a scheme or path. Separate multiple hostnames using new lines or commas.
Wildcards are supported. For example:
```
*.snowflakecomputing.com
```
**Default:** `*.snowflakecomputing.com`. If you clear the field, this default applies again.
**Auto-create user on SSO / OAuth login**
Automatically creates an account after a successful SSO or OAuth login when an account does not already exist.
Disable this option if administrators should create user accounts manually.
**Default:** Enabled
#### Diagnostics
**Enable query logging**
Writes database queries to the system logs for troubleshooting.
**Default:** Disabled
{% hint style="info" %}
Turn query logging off again after diagnosing an issue to avoid unnecessary log volume.
{% endhint %}
**Enable SSL verification on outgoing HTTP requests**
Verifies certificates for outbound HTTPS requests, including Tableau Server synchronization and workflow endpoints.
Keep this on. Turn it off only temporarily, when an outbound endpoint uses a certificate the server doesn't trust yet; better, make the server trust your internal certificate authority.
**Default:** Enabled
#### Security
**Trulyp whitelist** (**Allowed IPs**)
Restricts access to the Trulyp workspace to specific IP addresses.
Enter IP addresses separated by semicolons:
```
127.0.0.1;192.168.0.1
```
Leave the field empty to disable the restriction.
{% hint style="warning" %}
Make sure your own IP address or network is included before enabling the whitelist.
{% endhint %}
**Trusted proxies for Trulyp** (**Proxy IPs**)
Defines which proxy IP addresses are trusted to supply the `X-Forwarded-For` header.
Enter proxy IPs separated by semicolons:
```
10.0.0.1;10.0.0.2
```
Leave this field empty when Trulyp is not behind a proxy.
#### HTTPS and hostname
This section only appears on on-premises installations where Trulyp handles HTTPS itself. It's not shown on SaaS or in Docker.
Use it to configure:
* The local hostname and port
* An external proxy or load balancer
* An HTTPS certificate
Trulyp supports either:
* A `.pfx` or `.p12` certificate
* A matching `.crt` and `.key` pair
A PFX certificate may require a passphrase.
After configuring the settings, save them and select **Save and restart**. Trulyp restarts and opens the configured URL.
{% hint style="warning" %}
Avoid restricted or occupied ports. Trulyp validates the port and checks whether it is available before applying the configuration.
{% endhint %}
#### Extensions
**Add unique identifier to extensions URL**
Adds a company-specific identifier to hosted extension URLs so they can be scoped more tightly.
**Default:** Enabled
{% endtab %}
{% tab title="Data" %}
The **Data** tab holds the settings for performance and for data correction in WriteBackExtreme.
#### Chunk size (Records)
Defines the number of records the WriteBackExtreme extension fetches per request.
**Default:** `1000`
Reduce the chunk size when large datasets cause memory errors or too-many-attempts errors.
#### Rate limit (Requests/min)
Defines the maximum number of API requests per user per minute.
**Default:** `100`
When a request results in a 429 Too Many Requests, you can increase this to heighten the rate limit.
#### Data-service rate limit (Queries/min)
Defines the maximum number of dashboard data queries per user per minute. Analytics sends one query for every visual when an app opens and again whenever a filter changes, so large apps use many queries. Trulyp counts them separately, so they don't use up the **Rate limit** above.
**Default:** `600`
Raise this when large apps show rate-limit errors (429 Too Many Requests) while you open them or change filters.
#### Disable existing schema for data correction
Prevents users from generating data-correction schemas from existing database tables.
**Default:** Disabled
When disabled, the existing-schema flow remains available.
{% endtab %}
{% tab title="Studio" %}
The identity settings define the default visual style of visualizations made with [Studio](/trulyp/vizzy-studio/vizzy-studio-basics.md), when a request doesn't specify colors or fonts. They're applied when a visualization is built, so refresh existing visualizations after you change them.
#### Identity
**Primary color**
Defines the main accent color for charts and interactive elements.
Enter a hexadecimal color value, for example:
```
#2563eb
```
**Default:** Empty
**Secondary color**
Defines the supporting color used for elements such as secondary series, grid lines, and hover states.
For example:
```
#64748b
```
**Default:** Empty
**Font family**
Defines the font used for labels and text in generated extensions.
Use a web-safe font or a font available in Tableau, for example:
```
Inter
Arial
Tableau Book
```
**Default:** Empty
**Logo URL**
Defines the URL of an organization logo that generated extensions can use when requested.
**Default:** Empty
#### Script allowlist
The **Script allowlist** defines which third-party scripts generated Studio extensions are permitted to load.
Each entry requires:
* A name
* An `http://` or `https://` URL
HTTPS is recommended.
Scripts can be enabled, edited, or deleted.
{% endtab %}
{% endtabs %}
---
# 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.infotopics.com/trulyp/settings/advanced-settings.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.
