IT systems · Practical guide

Business Central: testing GxP permissions

In Business Central, combined permission sets can allow more than a role name suggests. Define business activities in a matrix, such as reading master data, changing a critical parameter or posting a quality-relevant transaction. Map them to technical permissions so a failed test can be explained in terms of the work affected.

Table of contents

At a glance

Which permission tests does Business Central need for GxP use?

Test effective Business Central access for the specific user, company and business process. Include permission sets, additional assignments and extensions. Demonstrate that permitted tasks work and unauthorised changes or approvals are prevented. A suitable role profile displayed in the interface alone is insufficient.

Scope and Applicability

This article addresses customer-specific access control. License rights, surface profiles, and functional authorizations are not equivalent. The relevant objects and additional functions depend on the installed application version in use.

Sources: [1] [2]

Assess the actual effect rather than merely the assignment

Multiple permission sets may collectively extend further than individually anticipated. Therefore, review the future overall configuration. Particular attention should be paid to broad administrative rights and functions from extensions that lie outside the original standard matrix.

Corporate boundaries are defined by individual test cases. Identical user interfaces may display data from different companies. A user must not be permitted to modify a critical dataset solely because their access in another company grants them permission for the same function. Document the enterprise, user, and tested action in the traceability record.

Sources: [1] [2]

From Business Process to Authorized Action

Start with quality-related activities: update master data, set status, record inventory, accept results, or release an order. For each activity, describe the required role and the permitted data scope. A role name such as "Quality" does not yet specify whether a user is authorized to modify data across all companies or is restricted to reading only within a defined business area.

Business Central distinguishes between permission sets and the actually effective permissions. Microsoft defines the concept of effective permissions, including origin and security filters. Consider the impact of the license as well. A screen role or hidden menu is not equivalent to an effective access restriction. Therefore, verify the action itself.

Capture direct and group-based assignments, administrative rights, and access for implementation partners. Document assignment to the organization and exceptions. A test of a artificially restricted example user may fail despite a real employee having additional permission sets. Therefore, use representative actual role combinations and controlled test accounts.

Sources: [1] [2]

A permission matrix with positive and negative cases

The matrix links action, user, data area, and expected reaction. First, define the technical rule; only thereafter is it assessed which permission setting enables its implementation. Excessive grant of rights should not be justified by a properly worded requirement after the fact.

For critical actions, a negative test is particularly informative. A user should read a master data set, but not change its quality-relevant parameters. Check allowed display and rejected change separately. If API, import or extension open further write paths, these belong to the scope considered. An examination of the interface alone does not automatically cover it.

Internal Work Aid: A permission matrix with positive and negative cases
Action in own exampleIntended roleExpected limit
Read article header Production Access within the required organization
Change quality attributes Named master data owner No changes made by pure production role
Set release-relevant status Named professional responsibility No uncontrolled self-release in the selected procedure
Perform import operation Technical identity designation Only agreed-upon objects and data areas
Rights granted Administrator Controlled distribution and traceable modifications

Sources: [1] [2]

Example: an additional group inadvertently expands access privileges

User U-17 is intended to view quality-related items within Company A. However, an additional, group-based permission set grants modification capabilities. A role-based test using an isolated test user fails to detect this combination. An audit of actual assignments reveals the source of the additional permission. The extended access results from system configuration; this example does not indicate a defect in Business Central and is not a completed product test.

For the test, a representative combination of U-17s is simulated in an appropriate test environment. Initially, an authorized read access is achieved. Subsequently, a critical parameter change attempt is performed. The expected professional reaction is rejection. If the change succeeds, a finding is documented and the root cause is assessed. Any correction must not unverifiedly obstruct other necessary activities.

After adjustment, both positive and negative cases are repeated. Additionally, Company B is reviewed if no authorization is specified therein. The evidence links user assignment, actual scope of rights, actions performed, and the resulting outcome. A screenshot of the corrected group membership alone does not constitute proof of impact on the business process.

Own work aid – Example: an additional group inadvertently expands access privileges
TestActionExpected evidence
Authorized access Review articles in A Correct dataset visible
Prohibited Change Change critical parameters Changes will be prevented according to the selected rule.
Wrong company Attempt similar action in B The proposed corporate boundary remains effective.
Additional Assignment Check representative combination Extended access is detected
After correction Positive and negative cases are repeated Work remains possible, unauthorized changes are not permitted.

Sources: [1] [2]

Administrators and technical identities are handled separately

Administrators may require enhanced rights for system setup and incident resolution. Describe the purpose, assignment, usage, and review of these access privileges. An administrative access should not serve as an unexplained default solution for routine business tasks. Verify that appropriate records and organizational controls enable traceability of access usage.

Technical identities follow the associated data pathway. Query which objects a interface must read or write, and which actions it does not require. Also assess the handling of access credentials, error messages, and responsibility during system failure. A functional import with broadest privileges does not prove that access is appropriately restricted.

Consider incorporating enhancements and partner solutions. Additional objects or workflows may be utilized. Modifications to these can impact authorization requirements and testing scope. Therefore, document the verified state of installed enhancements. A general statement regarding Standard Business Central does not automatically cover customer-specific enhancements.

Sources: [1] [2]

Maintain and review rights during ongoing operation

Link access, role changes, exit, and substitution to a controlled rights process. In particular, role changes may result in the accumulation of old and new authorizations. Therefore, regular verification should compare actual users, their responsibilities, and active rights. A static role name alone is not sufficient evidence of unchanged authorization scope.

Assess changes to permission sets and user groups. Microsoft notes that modifying a permission set affects all associated users. Therefore, identify the impacted usage prior to the adjustment. Appropriate regression tests can cover critical allowed and unauthorized actions, rather than performing a full revalidation of every interface.

Appropriate handover requires a well-maintained matrix, named responsible parties, and traceable test examples. The internal team should be able to justify why a particular role is authorized to perform an action and clearly identify the source of that authorization. This ensures that subsequent changes are controllable and reduces dependence on a single implementation partner for review.

Sources: [1] [2]

Draft: Assess actual user permissions

Select a representative user and document their actual task. Capture direct permission statements, relevant groups, assignment to the organisation, and exceptions. Then, compare the effective rights with the task. The review should explain the source of a critical permission and the action it enables.

Use the matrix as a dialogue between the technical and administrative functions. The technical department outlines the required activities; the administrative side demonstrates the technical implementation. If the two perspectives remain separated, a formally clean export may inadvertently contain extensive access rights. Therefore, document specific permitted and prohibited actions.

When a permission is revoked, perform both the negative scenario and the required work. Otherwise, a successful block may prevent another necessary task. Assess additional users with the same assignment source. Correcting a group rule may impact a larger user group than the initially reviewed user.

Sample filling example – internal work aid
Evaluation fieldExample entryTest reference
Task Read articles in Company A and perform routine production tasks. Positive technical workflow.
Unnecessary action Critical quality attributes change. Negative change attempt.
Assignment source Direct role plus additional security group. Consider combinations rather than individual rolls.
Area No appropriate access in Company B. Test the organisational boundary.
Exception Temporary representation with specified end date. Revocation confirmation upon end of period.
Evidence Task, effective authorization, and actual outcome. The decision remains explainable at a later stage.

Sources: [1] [2]

Next steps

  • Define activities, organizations, and critical data.
  • Determine effective rights including extensions.
  • Perform positive and negative tests with realistic assignments.
  • Organize changes, withdrawal, and regular rights review.
Further reading:

Project experience and collaboration

Reconcile permitted tasks with effective access

A role list becomes meaningful when tested against real actions. With process owners, we define what a user must be able to do and what must be prohibited. IT confirms effective assignments and extensions in the affected company. We can then determine whether individual excess permissions should be removed or the role model redesigned. Before execution, we specify permitted and prohibited test actions. We also identify who assesses later role changes and exceptions in operation.

Frequent Questions on Business-Central Permissions

Does the "Accountant" or "Administrator" profile suffice as evidence?

No. A profile does not fully describe the authorized permissions for your GxP process. What matters most are the effective accesses.

Sources: [1] [2]

Must an update trigger new role-based tests?

When functions, permissions, or relevant enhancements are affected, corresponding evaluations are required. An unchanged label of the permission set does not prove unchanged functionality.

Sources: [1] [2]

Can a test be performed using SUPER?

SUPER is unsuitable for role assignment validation when subsequent users do not possess those rights. The test may demonstrate basic technical functionalities but conceals missing authorizations and does not verify whether undesirable actions are restricted. Review the intended role combinations; administrative tests are to be conducted separately.

Sources: [1] [2]

Does hiding a page constitute an access control?

No. Hiding a page can simplify the interface while leaving access to data or actions unchanged. Test permissions and relevant alternative paths. Use representative accounts to demonstrate an allowed and a prohibited activity. Distinguish the interface, licensing and effective access.

Do we need to test each individual user credential?

Not automatically. Suitable representative role combinations should cover common permission models. Individual exceptions, additional groups, and administrative rights must be identified and appropriately assessed. Testing an idealized standard role is insufficient when actual users hold different combinations. Justify the selection and obtain alignment with the real user base.

How do we account for temporary project access?

State the purpose, scope, authorized duration, and responsible parties. Verify actual authorizations and the potential for future revocation. A planned end date alone does not confirm implementation. Also consider dependencies or expansions established upon access that may still be required after access has ended.

Sources and review date

The sources provide the technical foundation. Tables, checklists, and examples are derived methodological tools, not verbatim regulatory requirements. Manufacturer information must be referenced to the specific version and configuration in use.

  1. European Commission: EU GMP Annex 11, Computerised Systems (2011)Current version as per EudraLex inventory as of 14.10.2026. Application, risks, operation, and data lifecycle; specific testing proposals are derived independently.
  2. Microsoft: Granular permissions in Business CentralSupplier source for product functionalities. Availability and behavior depend on version, edition, license, and configuration; no general compliance certification.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Verify permissions in Business Central appropriately

We support you in assessing the current situation, clarifying responsibilities, and implementing appropriate evidence within operations. The type of support that is most effective depends on your system, your team, and the specific objective.

  • Computer system validation →

    Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

Send a project enquiry Customer testimonials →