Roles and permissions
Access to modules, lists, objects and operations can be limited according to user responsibility.
Security
Ingenes Studio QMS combines access control, secure sign-in, change history and data immutability mechanisms to support production, audit and regulated environments.
Access to modules, lists, objects and operations can be limited according to user responsibility.
The system can use external identity providers such as Google, Microsoft and Microsoft Entra ID.
Two-factor authentication and identity provider access policies increase user account security.
Important operations can be recorded with information about who changed what and when.
For data requiring special protection, we provide an immutable change history standard. Events can be preserved in a WORM model, write once, read many, using immutable Azure Blob Storage.
The immutable change history model supports GMP requirements for data integrity, operation accountability and retrospective record review. It helps meet ALCOA+ principles: attributable, legible, contemporaneous, original, accurate, complete, consistent, enduring and available data. This is especially relevant for quality records, deviations, CAPA actions, audits, reviews and approval decisions.
Communication uses secure connections and data is protected at the infrastructure level.
Backup and recovery strategy can be adapted to organizational requirements and data criticality.
Permissions limit data visibility between departments, locations, roles and processes.
Logs and system events support unusual activity detection and incident analysis.
We will show how to configure roles, sign-in, audit trail and immutable change history for your scenario.