---
title: "Edit field security policy field setup"
slug: "edit-field-security-policy-field-setup"
description: "Define field security policies to control editing permissions for forms, tables, and fields, ensuring data integrity and security management."
tags: ["Task topic"]
updated: 2026-03-20T11:16:36Z
published: 2026-03-20T17:44:34Z
canonical: "docs.staedean.com/edit-field-security-policy-field-setup"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Edit field security policy field setup

Use a field security policy to define for which forms, tables, or fields editing is locked or allowed.

If the form mapping is recorded and applied to a field security policy, and you have edited the table setup, edit the related field setup.

In the field setup, you define the fields, controls, or dimensions to which the field security policy applies. You also define how the policy is applied to the fields, controls, or dimensions.

The security level defines how to set up the policy and how it is applied:

| Security level | Description | Field setup | Condition setup |
| --- | --- | --- | --- |
| Table | Editing is locked or allowed for the whole table. | Only define one field setup record if you want to apply conditions. For this field setup record, these fields must be empty: **Field name**, **Control name**, and **Dimension name**. The settings of the **Default action** field and **Skip** field are not considered. | You can only apply generic conditions, for example, on user or role. |
| Table field | Editing is locked or allowed for specific table fields. | Define the desired field setup records. The settings of the **Default action** field and **Skip** field are considered. > [!NOTE] > **Note** > > The field setup default action overrules the table setup default action. For example, to allow editing of a few fields of a table with many fields, set the default action of the: > > - Table setup to **Lock edit**. > - Field setup to **Allow edit**. | For each field setup record, you can define the desired conditions. You can only apply generic conditions, for example, on user or role. |
| Record | Editing is locked or allowed for the whole record. | Define one field setup record. For this field setup record, these fields must be empty: **Field name**, **Control name**, and **Dimension name**. The settings of the **Default action** field and **Skip** field are not considered. | Apply conditions to define the records to which the policy applies. Define the conditions based on record data. For example, editing a record is only allowed if the: - Record has a specific status. - Customer belongs to a specific customer group. - Item is within a range of item numbers. |
| Record field | Editing is locked or allowed for specific record fields. | Define the desired field setup records. The settings of the **Default action** field and **Skip** field are considered. > [!NOTE] > **Note** > > The field setup default action overrules the table setup default action. For example, to lock editing of a few record fields, set the default action of the: > > - Table setup to **Allow edit**. > - Field setup to **Lock edit**. | Apply conditions to define the records to which the policy applies. Define the conditions based on record data. For example, editing a record field is only allowed if the: - Record has a specific status. - Customer belongs to a specific customer group. - Item is within a range of item numbers. |

### Steps

1. Go to **Dynamic field security management (Preview)** > **Policies** > **All field security policies**.
2. In the list, click the link of the desired field security policy.
3. Click **Edit**.
4. Expand the **Table setup** section.
5. In the list, find and select the desired record.
6. Define to which fields, controls, or dimensions a table setup record applies.

If the table setup record applies to a specific field, only one of these fields is filled for a record:

If none of these fields is filled, the table setup record applies to all fields of the table or form.

Expand the **Field setup** section.

> [!NOTE]
> **Note**
> 
> When you apply the form mapping to a field security policy, the relevant field, control, or dimension is already filled in automatically. If the policy must apply to all fields of a table or form, remove the field setup records. If you want to apply conditions, keep one record with empty fields.
  - **Field name**
  - **Control name**
  - **Dimension name**
7. In the **Field name** field, enter or remove the value.
8. In the **Control name** field, enter or remove the value.
9. In the **Dimension name** field, enter or remove the value.
10. Choose one of these actions:

In the **Default action** field, select an option.
  - **Allow edit**: Editing of the field, control, or dimension is allowed.
  - **Lock edit**: Editing of the field, control, or dimension is locked.
  - **Hide**: Editing of the field, control, or dimension is locked and it is hidden.
11. You can (temporary) stop applying the field setup record. So, when the field security policy is applied, the field setup record is skipped.

Select the **Skip** check box.

> [!NOTE]
> **Notes**
> 
> You can only edit an inactive field security policy.

## Related

- [Edit field security policy](/edit-field-security.md)