Regulations and compliance · Practical guide

GxP tenant isolation: do data and permissions stay within the right boundary?

Selecting a company at login is only one part of tenant segregation. Reports, interfaces and administrative functions may follow different data paths from the standard user interface. Define the permitted boundaries for a human medicines GMP process and test cases that should succeed alongside those that should be refused.

Table of contents

At a glance

How do we demonstrate that a GxP system keeps tenants reliably separated?

Define the data and actions permitted for each tenant, role and technical access path. Test those boundaries through the interfaces, reports, exports and screens actually used. Successful access to your own tenant does not establish isolation from another. Include cross-tenant privileges, operations functions and changes. The evidence must fit the GMP process and agreed architecture.

  • Define clients, roles, and authorized cross-functional responsibilities first.
  • The interface, export, and integration points may require different controls.
  • Shared infrastructure is neither automatically unsuitable nor does it require a segregation justification.

1. Who is considered the client in your system

Sources checked on 7 October 2026. In GMP for human medicines, Annex 11 requires suitable physical or logical controls against unauthorised access. It prescribes neither a uniform tenant model nor a separate database for every company.

A client may represent a legal entity, a site, a customer segment, or an organizational group. Such boundaries are not interchangeable. Two sites belonging to the same company may deliberately share data; two separate customer segments may, however, be expressly prohibited from doing so.

Therefore, document not only the names of the areas, but also the intended rules: Who is authorized to read, create, modify, release, or export data? Which tasks are explicitly intended to be cross-functional? Only with this clarity does a segregation of duties test establish a clear "should."

Sources: [1]

2. Map roles to data flows

A permission matrix becomes more meaningful when it includes the data pathways actually used. A role-based screen filter provides no indication regarding a background report or a technical integration access. Assess the actual impact of these on GMP data.

The following matrix serves as a reference tool. It does not claim to cover all possible technical attack vectors. The validation evidence for the intended use and a separate security assessment address related but distinct objectives.

Expert Responsibility Matrix for Functional Scope Boundaries
Data pathwayDefine allowed usageAppropriate evidence question
User interface Laboratory role sees orders within its own scope Is the area still correct when opening a single process?
Report and Export Release contains only the authorized data set Does the same limitation apply to pooled deliveries?
Interface Technical access is granted for agreed customers. Is the client and target object reviewed jointly?
Overarching Role The central office may explicitly be granted read access to multiple areas. Are reading, editing, and release actions separately described?
Operational function Securing or restoring follows agreed scope Are data assignments and access rights correct after operational intervention?

Sources: [1] [2]

3. Evaluate architectural evidence appropriately

Request a clear description of the relevant separation mechanisms and their limitations. Unfiltered internal details from the supplier are not required; sufficient information is needed to evaluate the intended use and required validation evidence.

A supplier may operate shared infrastructure and separate logical areas. Conversely, physical separation of a database does not automatically prevent incorrect authorizations or misdirected exports. The architecture is part of the evaluation; what remains critical is the functionality of controls within the intended workflow.

Supplier tests can demonstrate certain mechanisms. Verify the version, configuration, and covered data pathway. Internal roles, cross-functional analyses, and customer-specific integrations remain to be considered separately, provided the existing evidence does not cover them.

Sources: [1]

4. An authorized access and an unauthorized access constitute a single issue

The following test example utilizes only approved test areas A and B with test assignments A-01 and B-01. The laboratory role LA is permitted to read and edit within area A. A central role Z is authorized to read both areas, but is not permitted to modify results in area B. These rules constitute the technical specifications of the example.

Evaluate both permitted and explicitly prohibited actions. A blanket denial of all access would not constitute a successful implementation of the requirements, as legitimate work must also remain possible. Document the specific user, role, access pathway, and exact action.

Perform testing only in environments that have been officially authorized and with agreed-upon data. Technical validation does not require access to external customer areas. If a supplier conducts testing of specific platform boundaries internally, evaluate the associated documentation and remaining application-specific considerations.

Example: Should be configured for two test customers
Role and ActionObjectiveExpected behaviourRequired documentation
LA opens own request A-01 over surface Reading allowed Correct order and correct area displayed
LA opens foreign test assignment B-01 over agreed test route Access denied No content from B visible
LA generates a consolidated report Orders from A and B Only authorized stock from A Release includes A-01, not B-01
Z reads both orders A-01 and B-01 Reading allowed Both processes clearly distinguishable
Z attempts to alter result B-01 Changes are withheld Value of B remains unchanged
Integration interface from A has been submitted Process for B Rejected according to defined rule No unauthorised creation in the target area

Sources: [1]

5. Preserve the tenant identifier throughout the process

A dataset may be generated in the correct context and later incorrectly assigned. Therefore, verify whether interfaces, reports, and downstream processing maintain the required identity. The addition of a column only at export does not prove that the upstream selection was correct.

Particularly relevant are identical local identifiers. If both areas, for example, permit an order 001, the linkage must take into account the respective requirements of each area. Otherwise, a technically successful import may update the wrong functional dataset.

Manual corrections or administrative assignments may influence the boundary. Define appropriate authorizations, traceable decisions, and suitable documentation. Not every technical event is automatically GMP relevant; however, relevant changes must be assessed according to their significance.

Sources: [1] [3]

6. Cross-functional responsibilities for controlled operation

Support and administration personnel may require more extensive rights than laboratory users. Describe their purpose, allocation, and restrictions. A broad right is not automatically inappropriate, but must not become part of routine workflow without proper oversight.

Assess changes to roles, tenant assignments, integrations, and report templates. A platform update may impact unchanged customer-specific functionalities. The required evaluations depend on the impact and existing documentation, not solely on which program file was modified.

For assurance and recovery, it must be clearly defined which unit can be restored and the implications this has for other areas. Do not confuse the technical recovery unit with the professional client boundary.

Sources: [1] [2]

7. Separation Proof Checklist

With this checklist, you can jointly review the technical requirements and the existing body of evidence. It is particularly useful prior to establishing additional work areas, customer segments, or central roles.

  • Customer term and permitted data relationships clearly defined.
  • Review, modify, release, and export functions evaluated separately.
  • Overall responsibilities with authority clearly defined.
  • All actually used surfaces, reports, and interfaces are captured.
  • Positive and negative test cases derived from specific role rules.
  • Test areas and data for review are explicitly authorized.
  • Supplier documentation verified for version, configuration, and coverage.
  • Obtain customer identification and professional identity along relevant data pathways.
  • The impact assessment covers operational interventions and changes.

Sources: [1]

8. Questions that the company itself must answer

The supplier may describe the technical capabilities. However, which units are permitted to share data and who shall have overarching decision-making authority must emerge from your process. This professional judgment should not arise randomly from a pre-defined administrator profile.

For a small and medium-sized enterprise (SME), a concise list of responsibilities and a limited number of meaningful edge cases is often more practical than an extensive list of incomprehensible right designations. The selection must nonetheless cover the relevant pathways. A single surface test is insufficient when daily operations involve consolidated reports and integrations.

Document open boundaries clearly. If export is possible only through a central role, describe the actual controlled workflow. Do not assume the same automatic segregation as in individual user scenarios if such segregation does not exist.

Sources: [1] [2]

Project experience and collaboration

Verify tenant separation during export and role changes

With the process team and IT, we prepare controlled records in separate test tenants. We test access boundaries in the interface, search, export, background processing and role changes. Separate applications may need different evidence from shared services. We select the checks according to the actual data path and document which boundary was tested and which additional controls belong to the supplier or your operations team.

Frequently asked questions about Tenant isolation

Does Annex 11 require a separate database per client?

No. Annex 11 requires appropriate controls against unauthorized access, but does not specify a particular database model. Assess the specific architecture and effectiveness of controls for your data, roles, and workflows.

Sources: [1]

Is a client the same as a user role?

No. The client describes a data or organizational area, specifying the roles and authorized tasks. A user may possess different rights within a single area or be assigned a specifically defined cross-area role. Both dimensions must be evaluated together.

Sources: [1]

Is a test of the screen view sufficient?

Only when the relevant scope of use is actually covered. Reports, exports, and interfaces may utilize alternative mechanisms. Review the pathways used in the GMP process and do not assume that a correct view applies to any other output.

Sources: [1]

How do we test unauthorized access without third-party customer data?

Use authorized test tenants with fictitious datasets and pre-defined rules. For platform boundaries that are not directly accessible, appropriate supplier evidence may be required. The review must not involve unauthorized access to real, external areas.

Sources: [1]

Can a central QA role serve multiple clients?

Yes, if it is professionally justified and controlled. Describe the scope, for example, reading without modification or a targeted, cross-cutting decision. A universal ban on central roles cannot be derived from Annex 11.

Sources: [1]

What is important regarding identical order numbers in two areas?

The unique assignment must take into account the relevant scope. Specifically review import, search, and reporting functions. A local number alone is insufficient if it refers to different processes across multiple tenants.

Sources: [1] [3]

Are supplier certificates for the separation sufficient?

You may cover part or a specific mechanism. Verify alignment with version, configuration, and usage pathways. Custom roles, integrations, and subject-matter-specific rules require additional evidence, where applicable, if not already included.

Sources: [1]

Must every technical administrator intervention be recorded in the professional audit trail?

Not at all. Evaluate which interventions influence GMP-relevant data or their controlled use and how they remain comprehensible. Technical safety protocols and technical change histories can fulfill different detection tasks.

Sources: [1]

What should we test when adding a new tenant?

Assess new roles, data mappings, cross-reporting capabilities, and integrations, along with their impact on existing areas. Derive appropriate positive and negative cases from this analysis. A software version remaining unchanged does not eliminate configuration risks.

Sources: [1] [2]

Is a successful separation test a comprehensive security certification?

No. It proves the tested rules under the documented conditions. Further safety issues and ongoing operational controls remain to be dealt with separately. Therefore, describe the scope and limits of the proof clearly.

Sources: [1] [2]

Sources and review date

Source date: 7 October 2026. Human medicinal products – GMP; professional mandates and authority boundaries. No general security certification and no instructions for access to third-party customer data. Tables and case studies are internal reference tools, not results of completed product testing. Draft versions do not establish enforceable additional obligations.

  1. European Commission: EU GMP Annex 11, Computerised SystemsJanuary 2011 revision, applicable from 30 June 2011. Sections 1, 3, 4.2–4.3, 4.7, 5, 7 and 9–12 cover risk-based scope, third-party evidence, boundary testing, data flows, changes and access control.
  2. EMA/ICH: Q9(R1), Quality Risk ManagementEMA/CHMP/ICH/24235/2006 Corr.2; Publication date 31.01.2025; Q9(R1) effective from 26.07.2023; Sections 4.3–4.6 and 5.1: risk-based scope of testing and decision-making
  3. European Commission: EU GMP Chapter 4, DocumentationJanuary 2011; effective from 30.06.2011; §4.1 and §§4.8–4.10: Relationships, legible records, and data integrity

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Deriving client boundaries from the actual process

We support you in defining authorized data pathways, evaluating supplier evidence, and selecting relevant test cases. Throughout, your roles and professional boundaries remain central.

  • Cloud and SaaS validation →

    Maintain the validated state of cloud and SaaS systems as suppliers issue new versions. We define the boundary between your responsibilities and the supplier’s and agree how each release will be assessed.

Send a project enquiry Customer testimonials →