You develop a model-driven app to manage customer information. You have the system administrator security role on all environments. You create a business process flow that is associated with the…

Question

Options

• AGrant users the Run Flows privilege.
• BIn the app designer, ensure that the business process flow is added to the app.
• CGrant users the Organization Read permission on the Process table.
• DOpen the business process flow and associate the flow with the user security roles by using the

• A
  9% (2)
• B
  4% (1)
• C
  4% (1)
• D
  83% (19)

Explanation

Option D is correct because business process flows (BPFs) require two separate security configurations: table-level permissions on the BPF entity and direct role association on the BPF itself. Granting Create/Read/Write on the entity only controls data access - the BPF must also be explicitly activated and associated with the users' security roles via the Security Roles button inside the flow editor, which is why the system administrator (whose role bypasses this restriction) can see it but regular users cannot.

Why the distractors are wrong:

• A - "Run Flows" is a privilege for Power Automate cloud flows, not business process flows; these are distinct concepts.
• B - The admin already confirmed the BPF is visible in the app, which rules out a missing app designer configuration.
• C - Users already have Read permission granted on the BPF entity, so adding Organization Read on the Process table is redundant and not the standard resolution mechanism.

Memory tip: Think of BPF visibility as a two-key lock - one key is the entity permission (Create/Read/Write), and the second key is the role association inside the BPF itself. Forgetting the second key is the classic trap this question tests.

No community discussion yet for this question.