Skip to content
AIDA

01Enterprise

How AIDA separates the data of two organisations, checks every access and logs every change – and what operating it requires.

02

Access
& Audit

Who may do what – and who did what. Both are enforced on the server and in the database, not in the interface.

Roles and permissions

The organisation itself decides who may see, change, approve or delete what.

  • Ten role templates that can be adapted per organisation; custom roles are possible
  • Four levels per module: read, write, approve, delete
  • Project-level access: you see the projects you are a member of
  • Checked on the server – in every page, every action and every export
Role templatePurpose
Organization OwnerFull access including subscription and roles.
Organization AdminManages organisation, members and all modules – without billing.
Project ManagerRuns construction projects: claims, permits, invoicing, safety.
EngineerWorks on assigned projects and modules.
Quality ManagerOwns quality cases, traceability, instruments and standards.
Safety ManagerOwns inspections, hazards, briefings and incidents.
Maintenance ManagerOwns equipment, maintenance, spare parts and energy.
Finance ReviewerReviews and approves invoices and claims.
External ContractorSees assigned projects only; reports hazards and works on own tasks.
Read-Only AuditorRead access to all modules and the audit log.

Tenant isolation

The data of two organisations is separated on three layers.

  1. Layer 1

    every query names the organisation explicitly

  2. Layer 2

    the data client is bound to the tenant and sets the organisation scope itself – a forgotten filter opens nothing

  3. Layer 3

    row-level security in PostgreSQL – the application role sees only rows of its own tenant

Audit log

Who changed, approved or exported what, and when.

  • Immutable at database level: the application's database roles may only append and read entries, and a trigger rejects changes
  • Searchable with filters and exportable as CSV
  • Readable only with a separate permission; the history of every record comes from the same log

Sign-in

Email and password, with a second factor if required.

  • Two-factor sign-in with one-time codes (TOTP) and recovery codes
  • Session management: view and end active sessions
  • Temporary lockout after repeated failed attempts, attempt limits per address
  • Passwords stored as scrypt hashes, session tokens stored only as hashes

Single sign-on via SAML/OIDC is planned and not yet available.

03

Data
& Operations

Where files are kept, how you meet your data protection obligations and what the operator may do.

Document storage

Files are kept separately per organisation, with traceable versions.

  • Every version with a SHA-256 checksum
  • Confidentiality levels “internal” and “restricted”
  • File-type validation via the file signature on upload; no virus scanner is connected
  • Local or S3-compatible storage

Data protection functions

Tools that help an organisation meet its obligations.

  • Organisation data export as a ZIP archive
  • Per-person disclosure: the data stored about a person as an export
  • Anonymisation of former members
  • AI services are switched off until the organisation explicitly approves them

Platform administration

The operator manages organisations, plans and system status. Support accesses an organisation's business data only with its approval.

  • Support access only on request and after approval by the organisation
  • The approval is time-limited (1, 8 or 24 hours) and can be revoked
  • Support access is read-only – write actions are blocked

Operations

AIDA is prepared to run in containers: application, background service and PostgreSQL, plus S3-compatible storage.

  • Container image (Docker) and a Compose description for database, application and background service
  • PostgreSQL as the database, including full-text search and row-level security
  • Background jobs such as reminders and text extraction via a separate service
  • System status from real checks in the platform administration

Hosting provider and region are determined by the operator and agreed per deployment. Production operation in a target environment is still to come.

04

No Badges.
Just Facts.

AIDA currently holds no certification such as ISO 27001 or SOC 2 and has not been externally audited.

Hosting region, data processing agreement and retention periods are agreed per deployment. This page describes the current state of the application. What is only prepared or planned is listed in the interfaces table – in exactly those words.

05

Interfaces

What is available today, what is prepared in the code and what is planned – without embellishment.

  • Availablebuilt in and usable
  • Preparedpresent in the code, not connected
  • Plannednot yet implemented
InterfaceStatusWhat that means
File import (CSV, XLSX)AvailableModules with an import function validate every row before it is applied.
Export (CSV, PDF, ZIP)AvailableLists as CSV, reports as PDF, application pack and data export as ZIP – each within the access limits of the exporting person.
REST API v1AvailableRead access to projects, tasks and document metadata using API keys; described as OpenAPI.
Email delivery (SMTP)PreparedInvitations, password links and notices via the operator's SMTP server. Present in the code but not yet exercised against a real mail server. Without SMTP, messages are stored locally and not delivered.
File storage (S3-compatible)PreparedObject storage chosen by the operator. Present in the code but not yet exercised against a real storage service. Without it, files are kept on the server's file system, separated by organisation.
AI servicePreparedThe connection to Anthropic or an OpenAI-compatible service is present in the code. No service is configured by default; it has not yet been proven with a production service. A service is used only after the organisation approves it.
Stripe (payments)PreparedPrepared in the code, not connected. Subscriptions are managed manually; there is no online payment.
NormenKompassPreparedInterface for synchronising the standards register foreseen, no service connected. Standards are maintained manually.
Single sign-on (SAML / OIDC)PlannedSign-in through the company's identity provider. Not yet available.
SAP S/4HANA / ERPPlannedSynchronise projects, purchase orders and cost centres with the ERP.
Microsoft 365PlannedBring in documents from SharePoint/OneDrive, notifications in Teams.
BIM / IFCPlannedLink elements and quantities from IFC models to projects and bills of quantities.
OPC UA / MQTTPlannedTake machine and meter data directly from the plant. Until then: file import.
Vector search (pgvector)PlannedNot implemented. Search uses PostgreSQL full-text search, exact identifiers and typo tolerance; the database image already contains pgvector.

See AIDAat Work

We clarify questions about operations, hosting or data protection in a conversation – and show the functions described here in the demo environment.