Table of contents
At a glance
How do you control administrator privileges in a GMP system?
Annex 11 section 12 requires suitable access controls and traceable granting, modification and withdrawal of rights. Assess administrator authority across the application, operating system, database and other relevant layers. PIC/S PI 041-1 discusses segregation of duties, including in smaller organisations. Separate accounts, activity records and competent review can support a justified approach. A small team is not automatically exempt from effective control.
- System privileges and authority to perform a task are separate.
- Personnel overlaps require specific, demonstrably effective controls.
- Direct database, file, and supplier access also fall within the scope of consideration.
1. Assess administrative authority rather than job title
A user account labeled "Support" may have greater authority than a so-called administrator with limited responsibilities. Therefore, assess exactly what actions the individual is actually authorized to perform: create users, assign roles, modify rules, edit records, or influence logging.
The framework considered here is Human Medicines-GMP based on the annex 11 January 2011. Its security section links the control density to the criticality. This does not follow a universal technical product specification. The concrete justification must fit the task and must not remain uncontrolled solely because of a trustworthy person.
2. Make all relevant access levels visible
A restrictive role assignment may be ineffective if the same individual can directly modify the database or replace an unsecured results file. Therefore, consider the application, operating system, database, storage, and, if applicable, identity management. External service providers may also hold extensive authorities through alternative access mechanisms.
Describe the key influence pathways together with IT and process responsibility. This does not involve copying each individual technical authorization into a lengthy SOP. What is required is a clear mapping between authorized activities, effective access, and control. Technical detail statements can be clearly referenced.
3. Combine authority, instructions, and evidence of compliance
The following matrix separates a technical possibility from the technically permitted use. An operating system administrator should, for example, be able to perform an approved maintenance, but thereby not receive his own material decision. Which activities are previously approved or processed in an emergency according to a regulated procedure determines your actual process.
Note in particular rights that allow control measures themselves to be modified. If logging is administratively disableable, this capability must be considered during control evaluation. A log that allows an executing personnel to make unobserved changes is accordingly limited as a sole evidence of activity.
| Authority | Intended use | Question to check the control |
|---|---|---|
| User management | Assign approved roles | Are the application, implementation, and actual rights comparable? |
| Configuration | Evaluated system settings changed | Is the order linked to old and new status? |
| Database administration | Ensure technical operation | Are direct professional data modifications restricted and detectable? |
| Protocol management | Defined technical maintenance | Can the individual inadvertently remove relevant traces without detection? |
| External Support | Limited authorized deviation addressed | Is person, target, start and end clearly traceable? |
4. Small teams without general exception are organized
PIC/S PI 041-1 § 9.5 describes as a rule an independence of the system administration of persons with interest in the data result. For smaller organizations, the guide also covers under conditions a designated person from quality or production with administrative access. Routine work should then take place with a second restricted access; administrative activities are recorded and approved in the quality system.
This passage does not constitute a general authorization of arbitrary role combinations. Verify that the selected segregation actually functions and ensure that individuals are qualified to assess activities appropriately. A second signature from the same person or a mere formal review of an incomprehensible report does not establish reliable independent control.
5. Example: User account switch with two accounts
Suppose a person in a small company supports both routine laboratory work and application administration. The example uses a routine account R-17 and a privileged account A-17. A-17 may implement approved role changes, while measurement analysis uses only R-17. Another appropriately qualified person reviews the administrative activity record.
The pre-defined expected behavior verifies not only whether both accounts exist, but also their actual impact and the traceability of an approved change. This example is not a manufacturer function. If an application does not support this separation, the remaining gap must be explicitly evaluated.
| Test scenario | Predefined expected result | Supporting record |
|---|---|---|
| R-17 attempts to change roles | Changes not permitted | Actual Rights and Observed Rejections |
| A-17 carries out authorized task assignment | Only pre-approved role for designated person | Task, Implementation and Resulting Authorization |
| Routine evaluation under A-17 | Does not comply with the authorized procedure | Identification and assessment of unauthorized use |
| A-17 obtains additional authorizations | Do not implicitly permit effectiveness. | Documented change and control pathway |
| Order completed | Activity evaluated with results | Reasonable expert assessment |
6. Review award and revocation up to the point of actual effect
An approved request does not constitute a correctly configured authorization. Compare the assigned role with actual access. Consider group memberships, local accounts, and other means through which the same individual may obtain rights. Upon resignation or role change, authorization must be effectively revoked.
The re-registration may show different rights than an already ongoing session. This is a technical property to be assessed in the respective system, not a general statement about a particular product. Define how withdrawal and remaining access options are checked and who acts in the event of contradictions.
7. Prepare for emergency accesses and activity reviews
In the event of a disruption, a special administrative access may be required. A controlled emergency procedure should specify the purpose, responsible decision-making, identifiability, authorized activities, and subsequent evaluation. It must not serve as a convenient substitute for the standard change management process.
Additionally, specify which records are required for task verification. A login list may indicate that access was used, but does not necessarily confirm that a relevant configuration change occurred. Link appropriate technical information to order and outcome. Frequency and depth should be risk- and circumstance-driven; a one-off annual review is not automatically sufficient.
8. Assess a specific administrative workflow
First, select a relevant activity, for example, user role assignment or modification of a critical parameter. Have the normal procedure and an emergency procedure explained to you. This enables you to more readily identify inconsistent authorizations than through an abstract comparison of role names.
QA, IT, and system responsibility should jointly determine which technical gaps are to be closed and where additional procedures are required. An organizational control must be practically feasible and effective. If a significant area of influence remains uncontrolled, it must be treated as an open question in the evaluation and not assumed to be resolved in the SOP.
- Administrative influence pathways through all relevant levels are recorded.
- Activities permitted by possible access rights differentiated.
- Routine and administrative use separated.
- Awarding, modification, and revocation balanced with actual rights.
- Define the emergency access procedure and who has the expertise to review that activity.
- Technical and organizational controls clearly documented.
Project experience and collaboration
Set practical, traceable rules for administrative actions
With system owners, we examine a typical administrator task. Who needs access, what can they change and what evidence remains? We then simulate an urgent support case. Distinct IT and business roles may be served by clear permission profiles and a controlled request process. In a small team, where one person performs several duties, approval and additional controls for administrative actions need particular clarity. The process should work outside a planned maintenance window as well.
Frequently asked questions about Administrator privileges
Can QA fundamentally not possess administrator rights?
A general statement would be too far. PIC/S describes independent administration as a rule case and a limited approach for smaller organizations. The conditions mentioned there and the concrete conflict of interests are to be assessed. A mere reference to the team size does not replace this evaluation.
Are two accounts allowed for the same person?
You can separate routine and administrative usage, but this alone does not constitute a complete control concept. Verify actual authorizations, permitted activities, and their assessment. Two differently named accounts with identical comprehensive rights do not fulfill the required function.
Sources: [3]
Must every administrative action be approved prior to QA?
Not every activity needs the same prior QA approval step. GMP-relevant system changes including configuration run according to the specified change procedure (Annex 11 No. 10); assignment, modification and withdrawal of access rights are recorded (No. 12.3). For small organizations, in which, for example, quality or production personnel are administered, PIC/S PI 041-1 No. 9.5 expects the registration and approval of all administrator activities in the quality system. Set an appropriate procedure for this purpose; the guide is not a universal requirement for an identical release dialog for each technical handle.
Which rights are frequently overlooked outside of the application?
Is multi-factor authentication always required?
No, the current Annex 11 version from 2011 does not mandate a specific technique for every access in Section 12. Controls must be risk-based. PIC/S PI 041-1 Section 9.5 references additional authentication for internet-based remote access to systems containing critical data. The 2025 consultation draft proposes multi-factor authentication (MFA) for remote access to critical systems from outside controlled areas (Section 11.6); this draft is not yet effective. Therefore, evaluate access, system criticality, and additional controls within the specific context.
How do we control a shared emergency account?
Is an audit trail sufficient by itself?
It may provide evidence of key activities. However, verify what it captures, who can influence it, and how it is compared against the authorized instruction. A technically available log does not replace the need for access restrictions nor the professional assessment of relevant changes.
How often must administrator rights be reviewed?
Establish appropriate triggers and intervals based on risk and change. Role changes, employee departure, emergency access, or new functionalities may trigger a review. Annex 11 does not provide a universal monthly or annual schedule that automatically ensures appropriate control in every environment.
Can an external service provider take over independent administration?
This could represent an organizational approach. However, roles, access rights, documentation, and responsibilities must be specifically defined and evaluated. Outsourcing alone does not eliminate potential conflicts of interest and does not demonstrate that the operator maintains effective technical oversight.
What do we start with when dealing with a growing right of ownership?
Sources and review date
Source date: 07.10.2026. The relevant area here is human medicinal product GMP. EudraLex incorporates Annex 11 and Chapter 4 as of January 2011; the consulted draft from 2025 is not considered a current regulatory requirement. The completed examples and tables are internal work aids and do not constitute official template documents.
- EU GMP Annex 11: Computerised SystemsRevision January 2011; Effective date 30.06.2011; Access date 07.10.2026. Citations: §§1–3, 9–13
- EU GMP Chapter 4: DocumentationRevision January 2011; Effective date 30.06.2011; Access date 07.10.2026. References: §§4.1, 4.8–4.10
- PIC/S PI 041-1: Good Practices for Data Management and IntegrityPI 041-1, 01.07.2021; Access date 07.10.2026. Citations: §9.5, p. 40–43, in particular p. 41, small organizations; §9.6
- European Commission: EudraLex Volume 4Status as of 07.10.2026: Human medicinal product section implements Annex 11 January 2011 and Chapter 4 January 2011; Access date 07.10.2026. Relevant provisions: Human medicines / Annex 11
- European Commission: Consultation 2025 on Chapter 4, Annex 11 and Annex 22Status as of 07.10.2026: closed; 07.07.–07.10.2025. Occurrences: details; revision of Annex 11; links explicitly marked as draft guidelines. Serves solely for status demarcation and is not considered an authoritative source of requirements.
- European Commission: Annex 11 – consultation draft 2025Draft consultation, no current version; No. 11.6 on remote access authentication, specifically reviewed on 18.10.2026.
Sources checked: .
Address the specific control and verification requirements
Daniel Herrmann Consulting supports you in adapting this procedure to your system portfolio, evaluating gaps, and preparing appropriate validation evidence. The scope and level of involvement are determined by your actual process.
- 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.

