Data integrity depends on knowing who did what. Access management is the control that makes attribution possible, and it is also where shared accounts, forgotten leavers and over-powerful administrators most often turn up in inspection reports.
The regulatory baseline
Annex 11 expects physical and logical controls to restrict access to authorised persons, with the extent of control depending on the criticality of the system. It also expects the creation, change and cancellation of access authorisations to be recorded. The principles of attributable, contemporaneous and original data, summarised as ALCOA+, assume that every action traces back to one identifiable individual.
Build a role model, not a list of users
Define roles based on job function, document the privileges each role carries, and approve them through the quality unit. Pay particular attention to combinations that undermine independence, for example:
- An analyst who can also edit methods, delete data or change system time
- A reviewer who can approve their own work
- A process owner who also administers the application and its audit trail
- Developers or vendor staff with routine access to production
Control the full account lifecycle
Requests should be authorised and traceable, with training completed before access is granted. Leavers and role changes need prompt removal of rights, and inactive accounts should be disabled. Shared or generic logins are rarely defensible in GxP use; where an instrument or legacy application forces them, document the risk and put compensating controls in place, with a plan to remove the limitation.
Review privileged access regularly
Administrator accounts can alter configuration, users and in some systems the data itself. Keep them to the minimum number, separate them from everyday accounts, monitor their use, and review them periodically as part of the system’s periodic review. Periodic reconciliation of the user list against HR records and training status is a simple, effective check.
Documentation that earns its place
Aim for documents that people use. A concise system description, a traceability matrix from requirements to tests, a clear record of deviations during testing and a plain summary report are usually enough for a lower-risk system. Higher-risk systems justify more depth, but the principle is the same: every document should answer a question that an auditor, an inspector or a future colleague will realistically ask.
How PQRA helps
PQRA helps companies design role models, write access management procedures, and perform access reviews and gap assessments for GxP systems. We can also help prepare for inspection questions on shared accounts, administrator rights and segregation of duties.
Contact PQRA to discuss your computerised systems and data governance programme.


No responses yet