> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/forms/what-is-visual-forms/configure-read-only-fields-in-visual-forms.md).

# Configure read-only fields in Visual Forms

Read-only fields stay visible but cannot be changed.

Use them for values that employees should see but not edit.

### When read-only fields help

Use them for:

* autofilled values that should stay fixed
* calculated values
* summary or history fields

### Common read-only modes

#### Always read-only

Use this when the value should never be editable.

#### Never read-only

Use this when the field should stay editable.

#### Conditional read-only

Use this when the field should lock only in specific situations.

### Configure a read-only field

{% stepper %}
{% step %}

### Open the Visual Form

Open the form in **Settings → Forms**.
{% endstep %}

{% step %}

### Select the field

Click the field you want to configure.
{% endstep %}

{% step %}

### Choose the read-only mode

Open the field properties.

Then choose the right read-only mode.
{% endstep %}

{% step %}

### Add conditions if needed

If you use a conditional setup, add the rules that decide when the field locks.
{% endstep %}

{% step %}

### Save and test

Save the form.

Then test both the editable and locked states.
{% endstep %}
{% endstepper %}

### Read-only versus disabled

A read-only field stays visible and readable.

A disabled field is less interactive and can appear unavailable.

### Frequently asked questions

<details>

<summary>Can a read-only field still contain a value?</summary>

Yes.

That is a common use for autofill and calculated fields.

</details>

<details>

<summary>Can a field be both required and read-only?</summary>

Yes.

That can make sense when the value is filled automatically.

</details>

<details>

<summary>Should I test conditional read-only rules on mobile?</summary>

Yes.

That helps you confirm the behavior matches the process.

</details>

### Related topics

* [**Use the Visual Forms Configurator**](/marketplace-packages-and-power-ups/power-ups/forms/what-is-visual-forms/use-the-visual-forms-configurator.md)
* [**Use advanced mandatory rules in Visual Forms**](/marketplace-packages-and-power-ups/power-ups/forms/what-is-visual-forms/use-advanced-mandatory-rules-in-visual-forms.md)
* [**Use Visual Forms in the mobile app**](/marketplace-packages-and-power-ups/power-ups/forms/use-visual-forms-in-the-mobile-app.md)


---

# 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://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/forms/what-is-visual-forms/configure-read-only-fields-in-visual-forms.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.