Run each plant's quarterly review across its GxP systems
- Each account matched to a person
- Late removals drawn against the limit
- Inspector questions before sign-off
A GxP user access review that matches each account in each GxP system to the person behind it, draws each leaver and mover against the SOP limit, and counts a removal only when the next account export shows it.
See one quarter's leavers drawn against the limit ↓Each GxP system keeps its own list of accounts. When someone leaves or changes job, the HR system knows at once and IT closes the directory account the same day. A chromatography data system with its own users, a vendor-supported LIMS or an instrument PC with a local sign-in depends on someone remembering it. Movers gain their new rights on time and keep the old ones.
The review that should catch this is often a spreadsheet per system, sent to managers and ticked in bulk. A closed removal ticket is taken as proof the account is gone, and shared instrument logins, analysts with administrator rights and role conflicts across systems stay out of scope because no single spreadsheet shows them.
One missed account is enough. A leaver's login that still works makes each action under it unattributable, and the access review becomes a deviation.
Built forAccess control analystsQC lab headsSystem ownersPlant QA heads
Every GxP system keeps its own list of accounts, and the one not tied to the directory is the one a leaver keeps.
Checked by hand each cycle
Built-in controls
When a client's auditor wants the last access review, each removal comes with the export that proves it.
One quarter's review of a drug substance plant's fourteen GxP systems, worked by the IT access control analyst, the QC lab head, system owners, a line manager and QA.
demoSample data: the plant, its people, accounts, systems and dates.
Who owns which part of one plant's quarterly review.
Run each plant's quarterly review across its GxP systems
Decide findings on their systems: roles, service and shared accounts
Own the lab's systems and decide what a late sign-in means
Approve the review and each request to keep flagged access
Network, LIMS and QMS closed inside the limit; the chromatography account stayed open and was signed in to four days after the last working day.
Its group name said viewer; the permission table showed the analysts sharing it could edit methods and start runs.
Three analysts held lab administrator in the chromatography system, and nobody had reviewed their administrator actions.
A service account between two lab systems allowed interactive sign-in and had been used that way twice.
Around the review: removals waiting for their export, the reviews of all five plants, rules, the audit trail and settings.
demoSample data, from the working solution.
Seven agents prepare the review; owners, managers and QA decide it.
Plans the review: systems due by risk, the period, the SOP limits and approved rules.
Matches HR records to accounts by employee number, email and name variants, each with a confidence.
Draws each line, measures each change against the SOP clock from the last working day, and reads the audit trail where the clock broke.
Finds administrator rights held by people who create GxP data, and role pairs that break separation of duties, from each system's configuration.
Sends each manager their people's list and routes a manager's own access to their manager.
Confirms each removal in the next account export and reopens a task whose account is still enabled.
Reads the draft the way an inspector would, the agents' own conclusions included.
A GxP user access review checks that only authorized people hold accounts and roles in each GxP system, as Part 11 and EU GMP Annex 11 expect. Here agents match each account to a person and measure each leaver and mover against the SOP limit; line managers, system owners and QA decide and sign.
On the cycle each system's risk sets in your SOP. Here high-risk systems such as the chromatography data system, LIMS, MES and the QMS are reviewed every quarter and the rest every six or twelve months, with low-risk reviews signed in a sampled batch.
FDA's data integrity guidance says shared credentials mean a unique individual cannot be identified, and accepts shared accounts for viewing only. The agents read each shared account's permission table rather than its group name, and send any that can change data to its system owner.
The lab head reads the audit trail rows, the shift roster and the badge log together, orders the account disabled through an urgent task to IT and raises a deviation. The agents state the account, the workstation and the time, and leave who it was to the investigation.
Only when the system's next account export shows the account disabled or the role removed. A closed ticket or a locked account does not count, and a task whose account is still enabled reopens to IT.
The system owner proposes keeping it with a written control, and the QA head of the plant decides; a keep the QA head proposes is decided by the company's head of quality.
A model goes live only on the inputs where it proved itself, and quality teams can read and sign its evidence.
1-min demoGxP IT Change & Patch Impact AssessmentSecurity fixes go in on their clock, and each function a patch reaches is tested with a reason an auditor can follow.
1-min demoComputer Software AssuranceTesting sized to each function's risk, every line linked to its source.
1-min demoSend one GxP system's account export and last quarter's leavers and movers; we will draw each line against your SOP limit.