Access Denied Error in SharePoint List Board View During Drag-and-Drop for some users

suggesting to raise a support ticket with respective teams by sharing what you did so far. it may require to troubleshoot the issue further. thanks for your understanding.

Hi dharam2​ , here is my answer

Why It Works with 'Edit' but Not 'Contribute'

1.'Contribute' vs. 'Edit' – Subtle Differences in Metadata Rights

While both Contribute and Edit allow users to read, add, and modify items, Edit also allows:

• Managing list metadata (columns, views, content types)
• Modifying items in ways that involve more than just the item's fields—such as updating system properties or triggering flows.

In drag-and-drop, the action may update internal metadata or fire Power Automate flows—which could require permissions beyond standard Contribute access, depending on how the flows are configured.

2.Power Automate Flow Permissions Could Be the Culprit

Since this list is connected to flows, here's what can happen:

• When an item is moved (dragged), a status column changes → triggers a flow.
• If that flow tries to:
• Modify the item again,
• Access restricted columns,
• Update system fields (like Modified By), or
• Run in the context of the calling user (not a service account),

...then the action may require Edit-level access.

This means the Access Denied error doesn’t come from the drag-drop action itself, but from the follow-up action, likely when the flow tries to run or update something under the Contribute-level user.

3.Why Other Lists Work Fine

• Other lists might not have flows, or
• Their flows might not perform additional actions requiring higher access, or
• They might be running under elevated service accounts (e.g., 'Run as Owner')

So the same user with Contribute can update those lists without triggering permission errors.

Troubleshooting Steps

1.Check Flow Settings

• Open each Power Automate flow connected to this list.
• Go to: Settings > Run only users
• Confirm whether the flow runs:
• As the user who triggered it (default), or
• As the owner or service account (recommended for stability and permission elevation)

Try switching the flow to "Run as Owner" if the owner has Edit or Full Control. This may resolve the Access Denied issue without changing the user's list permissions.

2.Audit the Flow’s Logic

• Check whether the flow:
• Modifies the list item again
• Calls SharePoint REST APIs
• Reads from restricted lists or lookup fields

If any of these actions require more than Contribute, they’ll cause issues unless elevated.

3.Create Custom Permission Level

If absolutely needed, you can create a custom permission level based on Contribute, and add just enough extra rights (e.g., "Manage Personal Views" or "Approve Items") without giving full Edit.