> 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/classic-app-builder/design-and-structure/components-visibility/conditional-add-edit-and-delete.md).

# Conditional read, add, edit & delete

Set conditions on who and what can be added, edited or deleted

Allowing users to add, edit & delete records can be very powerful, but sometimes you want to restrict this to only certain Pages or to certain Teams/Users. With conditional add, edit & delete you can do this.

To do this, you need to go to the Permissions tab of the specific Team settings to set up granular access to each page in the application:

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LQ08RFAKZvFADEiXKFy%2F-MjhdTSt_luPLR17EK7D%2F-Mjhgfwp4ZreT9piucYt%2Fimage.png?alt=media\&token=442b7cb0-b894-42e5-9a59-3eb718f19b37)

### Example 1: Make only certain pages visible (Full Access/No Access)

In case you need to configure access only to certain pages, you can set the No Access option for a specific page, in which case the user will not have access to this page by direct link, also it will not be visible to this user in the menu.

To do this, you need to go to the Permissions tab of the specific Team settings to set up granular access to each page in the application. Let's grant full access to only two pages: Admin Panel and Agent Task Management:

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LQ08RFAKZvFADEiXKFy%2F-MjhdTSt_luPLR17EK7D%2F-Mjhjr2EuNdtN2aDlBdx%2Fimage.png?alt=media\&token=ec1c9244-16c8-47de-a31e-dfc0c64ae885)

In this case, all users in that team will only see these two pages in the menu:

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LQ08RFAKZvFADEiXKFy%2F-MjhdTSt_luPLR17EK7D%2F-MjhkuFsfuNt3plZy0lE%2Fimage.png?alt=media\&token=deb849f2-c5da-43b0-8d08-21b618fa81e6)

If the user goes to this page through a direct link he will see that screen:

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LQ08RFAKZvFADEiXKFy%2F-MjhdTSt_luPLR17EK7D%2F-MjhlTrGA96SL6Y-fumn%2Fimage.png?alt=media\&token=5bb8d433-9108-478f-9233-8305d30a1539)

{% hint style="info" %}
Now any user on this team will have full access to these pages.
{% endhint %}

### Example 2: Let users read-only access on the specific page

You can grant read-only access to any page. In this case, performing any action on that page (unless your buttons are hidden based on visibility conditions) will be prevented and the user will see an error message:

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LQ08RFAKZvFADEiXKFy%2F-MjhdTSt_luPLR17EK7D%2F-MjhpPcy-UmJi6l_cKa9%2Fimage.png?alt=media\&token=6ad2874c-d5ed-423f-b3ba-d9d5e5c1337f)


---

# 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/classic-app-builder/design-and-structure/components-visibility/conditional-add-edit-and-delete.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.