> 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/vizzy-studio/script-allowlist-and-branding.md).

# Script allowlist and branding

Want every Studio visualization to look like your brand, or let Vizzy use a charting library such as D3.js? Administrators set this up once, for all visualizations.

### Branding

In **Settings** › **Advanced settings** › **Studio**, under **Identity**, set the **Primary color**, **Secondary color**, **Font family** and **Logo URL**. Vizzy uses them whenever a request doesn't ask for specific colors or fonts. See [Advanced settings](/trulyp/settings/advanced-settings.md).

Branding is applied when a visualization is built. After you change it, open your existing visualizations and click **Refresh** (and **Save**) to apply it.

### Script allowlist

By default, visualizations can't load scripts from the internet. The **Script allowlist** lists the third-party scripts they may load, such as a charting library. Vizzy also knows about the allowed scripts, so it can use them, for example `window.d3` for D3.js.

You manage it in two places with the same list:

* **Settings** › **Advanced settings** › **Studio** (administrators).
* **Studio**, at `https://<your-trulyp>/backend/vizzy-ai/settings/script-allowlist`, or ask Vizzy to open the script allowlist (Vizzy studio creators).

<figure><img src="https://2312557015-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWbWxEBax8PKTjFYRLWgi%2Fuploads%2Fgit-blob-42fcc448ad4d2848e2ff6e176f46d320e324e24d%2FStudio_Allowlist.png?alt=media" alt=""><figcaption></figcaption></figure>

Click **Add script**, enter a **Name** (for example `D3.js`) and the **URL** of the script (must start with `https://` or `http://`), and click **Create script**. Use the switch to turn a script on or off, and the icons to edit or delete it. Click **Save allowlist** to save your changes.

<figure><img src="https://2312557015-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWbWxEBax8PKTjFYRLWgi%2Fuploads%2Fgit-blob-88af62bd5ddc1c906efdb40605e344137e924701%2FStudio_Allowlist_Create.png?alt=media" alt="" width="560"><figcaption></figcaption></figure>

Like branding, allowed scripts are added when a visualization is built: refresh existing visualizations after a change.

### What generated code can't do

To keep your data safe, Trulyp checks the code Vizzy writes. Visualizations can't make network requests, use browser storage or cookies, load remote images or styles, or add their own `<script>` or `<iframe>` elements. If Vizzy's code breaks one of these rules, the build fails with "Generated renderer code was rejected because it contains …". Ask Vizzy to fix it, for example by drawing the image or styling inline instead.


---

# 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/vizzy-studio/script-allowlist-and-branding.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.