> For the complete documentation index, see [llms.txt](https://docs-v3.toucantoco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-v3.toucantoco.com/visualizations-and-layouts/apps/customizing-apps.md). # Customizing Apps Toucan, we believe that customization of data applications is a key success factor for analytics adoption. In Toucan customization can serve three main purposes: * **Perfectly blend analytics design with your branding and product design guidelines** so the analytics look just like they come out of your team * **Storytell your data** with shapes, colors, and texts that add meaning & impact to your insights * **Improve and guide the user experience** through custom redirections, messages, and tutorials Find out more about our app customization capabilities in this section


	Customizing chart color elements	Customizing chart color elements
	Customizing the app's font	Customizing the app's font
	Adding Assets	Adding Assets
	Adding Glossary	Adding Glossary
Setting up, Managing and testint custom visibilities		Setting up, Managing and testing custom visibilities
Customizing the "no data error" message		Customizing the "no data error" message
Creating a dynamic background based on an Filter's column		Creating a dynamic background based on an Filter's column

--- # 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-v3.toucantoco.com/visualizations-and-layouts/apps/customizing-apps.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.