> 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/proactive-agents/publish.md). # Publish Publish proactive agents so teammates can discover, run, and re-use approved workflows. By default, Proactive Agents are private to you, however, you can allow others in our organization to run and extend Proactive Agents when they are ready. The following image shows the *Publish* popover that appears after clicking "Private"/"Shared" in the Proactive Agent Builder Header. After pressing '+ Add Group', we can select a workspace 'group' and give the group an 'access level' of Viewer, Editor, and Owner. For example, I've given all users in my workspace the ability to View the following Proactive Agent. See the table below for more detail on Proactive Agent access levels.
Access LevelDescription
OWNERcan run, edit, and share the Proactive Agent
EDITORcan run and edit the Proactive Agent, but not share
VIEWERcan run the Proactive Agent, but cannot edit or share
--- # 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/proactive-agents/publish.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.