> For the complete documentation index, see [llms.txt](https://brixxbox.gitbook.io/brixxbox-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://brixxbox.gitbook.io/brixxbox-documentation/client-api-reference/functions/excludefromreadonly.md).

# excludeFromReadonly

In our doc for **readOnlyMode**, we have seen how we can use it to disable all app controls or some of them. For that we will always have to make a call to **readOnlyMode** function, if we want anything to change. **excludeFromReadonly** function provides the functionality of excluding controls from being affected by the readOnlyMode. For example, we can set this function in appStart event then it will effect all **readOnlyMode** function calls after that. It means if we have set some controls to be excluded for readONly Mode function at app start, they will always be excluded from it influence during app life time and we do not have to make calls to this function again and again. If user wants to update **excludeFromReadonly** controls list then a new call to **excludeFromReadonly** will overwrite the previous setting.

#### Exaample

```javascript
   brixxApi.excludeFromReadonly(["myFirstControl", "mySecondControl"]);
```

### Parameters

1. Control array - It is a json array of control ids.

### Example Usages

As we have seen in **ReadOnlyMode** the example of address app and how we disabled every control using it without options. Now let say we want "Address Number" and "Name" controls to stay enabled. For this purpose, we will need to add these controls to our **excludeFromReadOnly** function and put this code in appStart event.

```javascript
   brixxApi.excludeFromReadonly(["adrNumber", "adrName"]);
```

As we can see in snapshot below Address number and name controls are editable after the app is started. We can use this functionality with any number of apps.

![](/files/io0BcZSSOYuyfu1AFszP)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://brixxbox.gitbook.io/brixxbox-documentation/client-api-reference/functions/excludefromreadonly.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.