Conflict definitions
Configure SoD controls.
Microsoft Dynamics 365 Business Central · Independent R&D
BC Access Auditor
Exploring access governance and Segregation of Duties in Business Central.
A hands-on BC extension for exploring TableData permission patterns, potential SoD conflicts and supporting evidence.
Developed by MJLS Plus · Independent R&D project
THE STARTING POINT
Why I started this project
The idea: make permission-risk reviews easier to run, understand and discuss.
Simple checks, defined in BCReview access against configurable SoD rules—without coding.
Easy to deploy and useInstall and work inside BC, without external reporting tools.
Shareable SoD ControlsExplore how SoD control definitions could be shared, reused and adapted to different Business Central environments and local requirements.
WHAT EXISTS TODAY
What BCAA does today
Capture permissions, check configured SoD patterns and inspect findings—all inside BC.
1
Permission snapshot
Capture user assignments and TableData grants.
2
Configurable SoD rules
Combine permission conditions using ANY / ALL.
3
Traceable evidence
See why a rule was matched.
4
Rule wizard
Define controls directly in BC.
LOOK INSIDE
See BCAA in action
A short walkthrough recorded in a Business Central sandbox, followed by screenshots of the application.
A brief look at configuring SoD rules, running access analysis and reviewing potential permission conflicts. Recorded in a sandbox environment for R&D demonstration.
Rule wizard
Set up rules in BC.
Conflict review
Review flagged risks.
Permission evidence
Trace permission evidence.
Overview
Review analysis results.
COMING LATER
Lessons learned
Building BCAA surfaced interesting questions about permission semantics, SoD assumptions and testing. I’ll share the practical lessons in a future post.
CURRENT STATUS · R&D / SANDBOX
Current status
Tested internally in BC28. Business control definitions and performance in large live environments still need external feedback.
Watch the recorded demo above, or get in touch if you would like to discuss the approach.
Scope, clearly defined
BCAA flags configured TableData permission patterns for human review. It does not establish whether a full business process can be executed.
Not a certified security audit or compliance solution. Evaluation is currently limited to R&D/sandbox use.
THE CONVERSATION I WANT TO HAVE
Let’s compare notes
I enjoyed building BCAA and would welcome candid feedback from BC consultants, AL developers and finance-control specialists.
- SoD controls: Which scenarios are useful in real businesses?
- Technical review: What would you challenge in the approach?
- Performance: How would it behave with real permissions at scale?
Behind BC Access Auditor
I'm Marcin, a NAV / Business Central consultant.
I built BC Access Auditor as a personal R&D project to explore permissions and Segregation of Duties in Business Central.
More about my consulting work at mjlsplus.com.
Working on Business Central permissions or SoD?
Happy to show BCAA, discuss controls and hear your perspective.
Start a conversation