> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/access-and-sharing/overview/review-ai-changes.md). # Review AI-generated changes Treat AI-generated pages, queries, and workflows as changes that need an access review before release. ## Review the request State the audience, permitted data, and prohibited actions in the request. For example: > Add a ticket page for support agents. Agents may view and update tickets for their assigned customer. They must not delete tickets, change customer ownership, or access another customer's records. This describes an intended policy. It does not prove that the generated implementation enforces it. ## Review the result Inspect the pages, actions, queries, resource connections, and workflows affected by the change. Check: * Which identity each data request uses. * How the relevant customer or user identifier is obtained. * Whether reads and writes enforce the same scope. * Whether hidden UI controls have corresponding authorization. * Whether errors or logs expose credentials or unnecessary data. Use synthetic examples in prompts and attachments. Only include data the selected AI service is intended to process under your organization's policy. ## Validate and release Compare the implementation with the intended policy using [allowed and denied tests](/access-and-sharing/overview/test-access.md). Include a user from another customer and a user with missing access properties. Preview the app as the intended user, then test the published version with a separate test account through your release process. Record the version and results so later changes can be checked against the same expectations. --- # 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.jetadmin.io/access-and-sharing/overview/review-ai-changes.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.