WorkflowIT & Data

GxP User Access Review

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 ↓
Watch with transcript →
The problem

The chromatography account a leaver kept is the one no directory knew about

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

The Problem Today

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

  • User lists
  • Chasers
  • Tickets
  • Bulk ticks
  • Shared logins outlive leaversOne instrument password survives each departure
  • Analysts with admin rightsThe people who make the data can change its settings

The Solution

  1. Each account, one personAccounts in each system matched by number, email and name variant
  2. Lines against the limitEach leaver and mover drawn from the last day to each account's close
  3. The evidence, as printedA late sign-in laid out with audit trail, roster and badge log
  4. Proven in the next exportA removal counts only when the system's own export shows it

Built-in controls

  • Disabling acts at once; keeping access waits for QA
  • No manager certifies their own access
  • The agents state the account, never who used it

What You Get

When a client's auditor wants the last access review, each removal comes with the export that proves it.

  • A standing controlHigh-risk systems reviewed each quarter on their own cycle
  • A new analyst, an inspector's eyeThe inspector's questions built into each review
  • One map of people to accountsReused by audit trail and data integrity work
Features

GxP user access review of one plant's quarter, leaver by leaver

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.

  1. 01Exit line

    Leaver and mover access removal measured against the SOP limit

    • One line per person who left or moved. From the last working day or move date to the moment each GxP account closed, so a late removal shows at a glance.
    • Clock starts on the last working day. A termination date pushed back by leave hides no late close, because the rule counts from the day work stopped.
    • Steered in plain words. Contractors hired through a project and kept outside the HR system join the run when the analyst asks for them.
  2. 02One leaver

    Orphaned accounts found system by system for a single leaver

    • Each account, change and time. Directory, LIMS, QMS and the chromatography system in one table, each with the export it was read from.
    • The system with its own accounts. The one account not tied to the company directory is the one that stays open, and it is flagged by name.
  3. 03Matches

    Accounts matched to people by employee number, email and name variant

    • Name variants read. A second LIMS account or a shortened name on an instrument PC still resolves to the person behind it.
    • Weak matches wait for a person. Below the threshold the analyst opens both records and decides; two people are kept apart until someone confirms.
    • Accounts with nobody behind them. Shared, generic, installation and interface accounts are listed apart, each a question for its system owner.
  4. 04Late sign-in

    A sign-in after the last working day, laid out with audit trail and badge log

    • Records as each system prints them. Audit trail rows, the shift roster and the badge log sit together, so the lab head decides on the records.
    • Account, workstation and time only. Naming who it was belongs to the investigation; the screen states what the records hold and stops there.
    • Ordered disabled, deviation raised. The QC lab head orders the account disabled through an urgent task to IT and raises the deviation under their own session.
  5. 05Inspector

    Shared login accounts challenged by an inspector agent, its own draft included

    • An inspector's likely questions. Who signed in, who reviews administrator actions and who worked here outside HR are raised before anyone signs.
    • Its own mistake corrected. A shared account called read-only because of its group name could edit and save methods; the permission table proved it, and the draft changed.
    • Each answer owned. A question goes to the person who can answer it, such as the lab head through the deviation.
  6. 06Findings

    Privileged access review and segregation of duties conflicts for each owner

    • Administrator rights held by analysts. People who create GxP data and can also administer the system are named for the system owner to decide.
    • Role pairs across systems. A recipe author who also approves batch records is found even when no record shows the conflict was used.
    • Remove at once, keep on a control. A removal goes to IT immediately; keeping access needs a written control and the QA head's approval.
  7. 07Certify

    Periodic user access review certified row by row by each line manager

    • Only their own people. The supervisor sees the analysts they manage and decides each row after opening it; their own access goes to their manager.
    • Flags on each row. Leavers, shared accounts and administrator rights are marked before the manager decides.
    • A remove reaches IT. Each removal becomes a task carrying owner and due date, or joins the task a finding already opened.
  8. 08Sign-off

    GxP user access review sign-off gated on removals shown in an export

    • Six gates before anyone signs. Systems read, matches, findings, inspector questions, certifications and export-confirmed removals must all hold first.
    • Prepared by the analyst, approved by QA. QA approval comes only after the review record and the export are opened; otherwise the review returns to the analyst with a reason code.
    • Changes after signing undo it. A steer, a match or a setting changed afterward removes both signatures and marks the evidence pack unsigned.

The analyst runs it, owners decide, managers certify, the QA head signs

Who owns which part of one plant's quarterly review.

IT access control analysts

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
System owners

Decide findings on their systems: roles, service and shared accounts

  • Findings with the records to open first
  • Removals that act at once
  • Rulings kept as approved rules
QC lab heads

Own the lab's systems and decide what a late sign-in means

  • Audit trail, roster and badge log together
  • An urgent disable task to IT
  • The deviation raised under their session
Plant QA heads

Approve the review and each request to keep flagged access

  • Removals proven in the next export
  • A review that unsigns itself on change
  • Low-risk reviews signed after a sample

A shared login read as read-only could edit and save methods

A leaver's account still active

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.

A shared account mislabeled read-only

Its group name said viewer; the permission table showed the analysts sharing it could edit methods and start runs.

Analysts with administrator rights

Three analysts held lab administrator in the chromatography system, and nobody had reviewed their administrator actions.

An interface account used by a person

A service account between two lab systems allowed interactive sign-in and had been used that way twice.

More screens

Low-risk reviews are signed in one batch only after the QA head opens a sample

Around the review: removals waiting for their export, the reviews of all five plants, rules, the audit trail and settings.

A ticket marked done is not proofRemoval tasks go to IT operations with owner and due time; the closure checker counts a removal only when the next account export shows it.
Each system on its own risk cycleGxP systems reviewed on their own cycles, quarterly for high risk; low-risk reviews are signed together once the QA head has opened their sample.
A system owner's ruling, proposed as a ruleRulings from earlier reviews, such as starting the clock on the last working day, apply as rules only once QA approves them.
From the late sign-in to the deviation, loggedEach step, a person's or an agent's, with why it was taken, what the signature meant and the session; exportable for an auditor.
Limits that loosen only with QA's signatureLeaver and mover limits, review cycles, the dormant threshold, the bulk-sign sample and the systems read; a tighter setting applies at once.

demoSample data, from the working solution.

The identity matcher leaves weak name-only matches to a person

Seven agents prepare the review; owners, managers and QA decide it.

Review planner

Plans the review: systems due by risk, the period, the SOP limits and approved rules.

  • Changes no scope silently
  • Applies no proposed rule
Identity matcher

Matches HR records to accounts by employee number, email and name variants, each with a confidence.

  • Merges no two people
  • Leaves weak name-only matches to the analyst
Rule checker

Draws each line, measures each change against the SOP clock from the last working day, and reads the audit trail where the clock broke.

  • Judges no one's use of an account
Duty-conflict finder

Finds administrator rights held by people who create GxP data, and role pairs that break separation of duties, from each system's configuration.

  • Removes no role
Certification chaser

Sends each manager their people's list and routes a manager's own access to their manager.

  • Certifies nothing
Closure checker

Confirms each removal in the next account export and reopens a task whose account is still enabled.

  • Takes no closed ticket as proof
Inspector

Reads the draft the way an inspector would, the agents' own conclusions included.

  • Leaves each point open for its owner

Read from HR, each system's account export and the lab's own logs

HR systemLeavers, contractors and movers, with last working day and move date.
Account and role exportsFrom the chromatography data system, LIMS, MES and eBR, the QMS and ERP quality modules.
Instrument PCsLocal accounts on lab instrument workstations, with their permission tables.
Audit trails, rosters and badge logsRead only where a clock was broken, laid out as each system prints them.
SOP limits and approved rulesRemoval limits, review cycles and the rulings QA has approved.

What QA and IT compliance ask about user access review

What is a GxP user access review?

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.

How often should a periodic user access review run?

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.

Are shared login accounts allowed?

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.

What happens when a leaver's account was used after they left?

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.

When does a removal count as done?

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.

Who approves keeping access that was flagged?

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.

Bring one system's
account export.

Send one GxP system's account export and last quarter's leavers and movers; we will draw each line against your SOP limit.