> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/tellius-5.6/settings/application-settings/miscellaneous.md). # Miscellaneous Under **Settings → Application Settings → Miscellaneous,** admins can configure core behaviors for image rendering, sharing permissions, and CDN usage. These settings can improve performance, control user access, and define how shared content is handled.

Misc. Settings

### **CDN** **Use Internal vs External CDN for storing images** * **Internal**: Images generated by Tellius (e.g., charts) are stored within the internal server infrastructure. * **External**: Images are stored externally (e.g., in an Amazon S3 bucket or a similar CDN) for faster access and better scalability. Recommended when embedding or sharing content across users. ### **Collaboration** **Minimum effective role required for sharing** * Controls which users can share content (e.g., charts, reports) via public links or CDN-hosted images. * Select a minimum role and any user with a role **below** the selected role **cannot** share content externally. ### **Report Configuration** **Offline Render:** If enabled, rendering is done without requiring live access. Useful for scheduled jobs, exports, or PDF generation from backend services. **Public URL:** The URL used by external users or services to access shared or rendered content from Tellius. Click on **Update** to apply changes. **Internal URL:** Internal-facing service endpoint used for rendering within Tellius. Click on **Update** to apply changes. --- # 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://help.tellius.com/tellius-5.6/settings/application-settings/miscellaneous.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.