Microsoft Dynamics 365 | Integration, Dataverse...

What Role Privileges Are Required in Power Platform to View Business Rules in Forms?

(1) Share

Report

Posted on by luisafrancoj95

Hi everyone,

I'm configuring security roles in Power Platform and need to ensure that users can see and experience business rules on forms (e.g., field visibility based on values), but I want to manage this granularly by entity.

My questions:

What specific privileges should a security role have to allow users to see and execute business rules on forms?
What is the minimum level of Read access to the Process entity required for this?

Thanks in advance for your help

Categories:

Dynamics 365 general

Power Platform integration

I have the same question (0)

All responses (5)

Answers (0)

Tom_Gioielli 3,084 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!
Business rules are essentially low-code JavaScript added to forms in Dynamics CRM to perform actions, such as showing/hiding a field or changing a requirement level. While Business Rules can be set to run on all forms, specific forms, or even at the table level, they cannot be set to only run based on a user's security role. If the user has access to the form in question, and the form has a Business Rule on it, then the user will "experience" that rule being processed.

A few notes that might help you out in your requirement.

Form access can be controlled by security role, so you could have different forms based on security roles and only apply business rules to a singular form. Depending on your requirements, this could be a nightmare to maintain so I would be cautious.

If you want to control whether a user can see/edit a specific field on a table through security, then you should check out Column Security Profiles (Column-level security - Power Platform | Microsoft Learn)

Access to the Process entity is typically for users who are going to be modifying/creating business rules, workflows, and other processes. In about 10 years of work in CRM and through consulting, I don't know that I have ever needed to modify or tweak a standard user's access to the process table. Either they are a standard user who has whatever the OOB permission for the table is that comes from a pre-packaged role, or they are a System Admin or System Customizer who has the ability to modify the system.

Was this reply helpful? Yes No
luisafrancoj95 10 on at

Like (1)

Report
Copy link

Link copied!

@Tom Gioielli Thank you Tom.

The thing is that the user has full permissions to the table associated with the business rule.

They also have access to the form where the rule is applied, and permissions to the Process table in the environment. However, the business rule is not being executed when the user accesses the form with their assigned (secondary) security role.

I’ve confirmed that the rule works correctly when I test it using the System Administrator role — the fields are hidden as expected based on the rule’s logic. But when I switch to the secondary role, the rule is not triggered at all.

Any ideas on what specific permissions might be missing in the secondary role to allow the business rule to run?

Was this reply helpful? Yes No
Suggested answer

Ramesh Kumar 7,547 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

If I am not wrong Business Rules are client-side logic embedded in forms — they do not execute via server-side flows or process ownership. Below are 3 options or area I would double check. Power platform is has complicated permission ( Its my personal experience)

1. Not added to the user’s role with “Read” or “Write” access

2. Field-Level Security

3. Custom permission

Thanks

Ramesh

If this was helpful, please check the "Does this answer your question?" box and mark it as verified.

Was this reply helpful? Yes No
Suggested answer

Nachiket Saraph 6 on at

Like (1)

Report
Copy link

Link copied!

1. Business rule's scope in the solution explorer and ensure it's applied to the correct form(s).

2. Ensure all referenced fields are included in the form's layout.

3. Grant "Organization" read access to the "Process" entity for the affected security roles.

Was this reply helpful? Yes No
Suggested answer

DAnny3211 11,417 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Hi Luisa,

To allow users to view and execute business rules on forms, the security role should include at least the following:

Read access to the relevant entity, since business rules act on specific fields within that entity.

Read privileges on the “Process” entity (which represents business rules). The minimum required level is Read = User to allow users to see the rules applied to forms. However, if the rules are shared across multiple users or teams, a higher level (Business Unit or above) might be necessary.

Access to the form: the user must have access to the form where the rule is configured, otherwise they won’t be able to see its effects.

Lastly, keep in mind that business rules run on the client side, so no explicit execution privilege is needed—just the ones that allow users to view and interact with the fields and forms.

Hope this helps!

Best regards,
Daniele

Was this reply helpful? Yes No