Role-based access
We map user groups and access needs. Service accounts and integrations receive particular attention so that access matches its purpose.
Document security from design to operation
Sensitive documents need more than a password. We bring permissions, identities, traceability, backup and administration rules into the system design.
History and operational visibility
We define which events to record and who reviews them. Logs should help reconstruct an operation without unnecessarily exposing sensitive information.
Backup, recovery and change
We agree backups, recovery checks and upgrade procedures with the operations team. Security remains part of day-to-day running.
Cloud or your own infrastructure
The operating model follows the data, interfaces and organisational requirements. Public-sector cloud projects also need a check of the specific offering and its conditions of use.
Users and applications / Identity and roles → Document API / Application services → Availability and scaling / Data and document layer → Backup and recovery / Access and audit. High availability does not replace backups or tested recovery.
Frequently asked questions
Who can see sensitive documents?
Access is configured by role, group and application. Checks should include previews, exports, service accounts and role changes. Hiding a menu link is not an access control.
Will our documents be used to train AI?
That depends on the service, contract and configuration. Before deployment, establish the processor, data location and retention, access controls and permitted use of inputs. The design should answer these questions explicitly.
Cloud or on-premises?
Consider data sensitivity, availability, integration, operating capacity and cost. Compare backup, recovery and exit arrangements as well. Public-sector projects also need to check the rules for the specific cloud offering.
Is long-term preservation the same as backup?
No. Backup primarily supports recovery after loss or failure. Preservation also addresses readability, metadata, provenance and controlled handling over time. Both are needed, but they serve different purposes.
What support response times do you offer?
Response times, service hours, priorities and escalation are defined in the support contract. They reflect the system's importance and responsibilities shared by the customer, ALTAIR and other suppliers.