> 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/app-and-data-permissions/page-and-action-access.md).

# Control page and action access

Define what each audience can open and do before configuring the app.

## Write an access matrix

For a ticket app, start with an example like this and adapt it to your requirements:

| Audience      | Ticket list               | Update tickets            | Delete tickets            | Build the app |
| ------------- | ------------------------- | ------------------------- | ------------------------- | ------------- |
| Reviewer      | Allowed                   | Denied                    | Denied                    | Denied        |
| Support agent | Allowed                   | Allowed within scope      | Denied                    | Denied        |
| App builder   | According to admin policy | According to admin policy | According to admin policy | Allowed       |

This is a design example, not a claim about automatic defaults.

## Implement the rules

Apply the app's available page, component, and action controls for each team. In AI-generated apps, inspect the resulting implementation and the authorization applied to data requests. In Classic apps, use the page and conditional-action settings available in that builder.

See [Classic conditional add, edit, and delete](/classic-app-builder/design-and-structure/components-visibility/conditional-add-edit-and-delete.md) and [Classic component visibility](/classic-app-builder/design-and-structure/components-visibility/conditional-visibility.md) for those specific interfaces.

## Verify the result

Use [invited-user preview](/ai-app-builder/preview-and-troubleshoot/preview-as-an-invited-user.md) to inspect navigation and controls. Then test with the intended account:

* Open an allowed page.
* Attempt to open a restricted page directly.
* Run an allowed action against a test record.
* Attempt a denied action and verify the record did not change.

Include workflow actions and API requests used by the page. Continue with [record access](/access-and-sharing/app-and-data-permissions/record-access.md) so a permitted action cannot affect another user's records.


---

# 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/app-and-data-permissions/page-and-action-access.md?ask=<question>&goal=<user_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.