Access controls
Unique individual accounts, documented authorization, role-based permissions and a managed account lifecycle covering joiners, movers and leavers.
Applicability comes first: not every system falls in scope, and treating every spreadsheet as a Part 11 record wastes effort that belongs elsewhere. Where it does apply, we build the access, audit-trail and record-protection controls and the evidence that shows they work.

For each electronic system that touches regulated activity, the first question is whether Part 11 applies at all — and that is a decision for your QA and system owners, informed by intended use. Applying full Part 11 controls to every piece of exploratory scientific information is a common and expensive mistake. So is discovering late that a system in scope has shared logins.
Where Part 11 does apply, the areas below are what we implement and evidence on the infrastructure side.
Unique individual accounts, documented authorization, role-based permissions and a managed account lifecycle covering joiners, movers and leavers.
Where used: attributable to one individual, linked in a controlled way to the corresponding record, and carrying a documented meaning such as approval or review.
Configured, where the system supports it, to capture who, what happened, when, and the previous and new value where appropriate.
Records that stay accessible, legible, retrievable and protected throughout the required retention period.
Day-to-day acquisition and processing, without rights to alter the system itself.
Operational oversight of laboratory activity and assignment.
Review and approval, separated from the people producing the data.
Study-level responsibility where the work calls for it.
Application configuration, separated from infrastructure administration.
Infrastructure and security operations — deliberately without the ability to alter approved scientific results.
Access to inspect without the ability to change anything.
Normally no. Equally, IT administrators should not be able to modify approved scientific results simply because they administer the server. Separating infrastructure administration, application administration, laboratory operation and QA approval is what supports segregation of duties, and it is one of the first things an assessor probes.
Then that is recorded as a gap with compensating controls rather than papered over. Audit trails are enabled where technically available and required; where they are not available, the risk is documented and addressed through procedural and access controls, and factored into the system's replacement plan.
No. That assessment belongs to your QA and system owners, and depends on intended use and regulatory context. We support it with accurate system inventories and technical detail, then implement and evidence the controls that follow from your decision.
Pracoda provides technical infrastructure implementation and documentation support. Regulatory interpretation, GxP applicability decisions, Part 11 applicability determinations, validation approval, SOP approval, data review and final quality release remain with the client's authorized QA, system owner or qualified regulatory and validation specialists. We do not represent that implementing these controls alone makes a client or a system compliant.
Tell us which systems you think are in scope and what your current access model looks like. We will tell you what we would tighten first.
Share the problem, the platform and the deadline. We will come back with an approach, a team and an estimate.