---
title: "Set up field security policy conditions"
slug: "set-up-field-security-policy-conditions"
description: "Define field security policies in D365 F&SCM to control editing access for forms, tables, and fields with inquiry and dynamic query conditions."
tags: ["Task topic"]
updated: 2026-03-20T12:29:00Z
published: 2026-03-20T17:44:34Z
canonical: "docs.staedean.com/set-up-field-security-policy-conditions"
---

> ## 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.

# Set up field security policy conditions

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 and field setup, define the applicable conditions.

In the condition setup, you define how the policy is applied.

To define a condition, you can use one of these options:

- **Inquiry**: Use a D365 F&SCM inquiry to define the condition.
- **Dynamic query**: Use a query from the **Dynamic query framework** to define the condition.

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. Expand the **Field setup** section.
7. In the list, find and select the desired record.
8. Expand the **Condition setup** section.
9. Sub-task: Set up inquiry condition.
  1. Click **Add**.
  2. In the **Description** field, type a value.
  3. In the **Query type** field, select '**Inquiry**'.
  4. By default, the query base table is the table of the selected policy. If desired, you can change it.

In the **Query base table** field, enter or select a value.
  5. Define the inquiry in the Inquiry dialog.

Click **Edit query**.
  6. Click **OK**.
10. Sub-task: Set up dynamic query condition.
  1. Click **Add**.
  2. In the **Description** field, type a value.
  3. In the **Query type** field, select '**Dynamic query**'.
  4. In the **Custom query** field, enter or select a value.
11. You can (temporary) stop applying a condition.

Select the **Skip** check box.

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

## Related

- [Set up dynamic queries - Master Data Management Studio](/set-up-dynamic-queries-dynamic-field-security.md)
- [Edit field security policy](/edit-field-security.md)