> For the complete documentation index, see [llms.txt](https://docs.zenlytic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zenlytic.com/embedding.md). # Embedding - [Embedding Overview](https://docs.zenlytic.com/embedding/embedding_overview.md): Embed Zenlytic content with private or signed access, depending on your users and authentication model. - [Private Embedding](https://docs.zenlytic.com/embedding/private_embedding.md): Embed Zenlytic for internal users who authenticate with their own Zenlytic accounts inside the iframe. - [Signed Embedding](https://docs.zenlytic.com/embedding/signed_embedding.md): Generate signed embed URLs for external users and apply row and column access controls. - [Permissions in Embedding](https://docs.zenlytic.com/embedding/permissions_in_embedding.md): Control embedded access with user attributes, access grants, and signed URL permissions. - [Embedding Styles](https://docs.zenlytic.com/embedding/embedding_styles.md): Customize the embedded experience with layout, navigation, and style options that match your product. - [Proactive Agents in Embedding](https://docs.zenlytic.com/embedding/workflows_in_embedding.md): Run proactive agents inside embedded Zenlytic experiences and pass users into reusable workflows. --- # 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.zenlytic.com/embedding.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.