Security

No password in the office. A code required outside

The portal is installed in your infrastructure and plugs into Active Directory. Data, files and logs never leave your network.

Protection

How the portal protects you

Kerberos SSO

Password‑less sign‑in from a domain PC

The browser presents the domain Kerberos ticket and the employee is straight in. On personal devices the password is checked against Active Directory over secure LDAPS.

MFA · TOTP

App code for access from outside

Google Authenticator, Yandex ID or Microsoft Authenticator. One‑time backup codes if the phone is lost.

Contractors

External staff without a domain account

Self‑registration, email confirmation, administrator approval, a mandatory second factor and separate rights.

Audit

Security event log

Sign‑ins, failures and blocks with minimal personal data, filters and CSV export.

Roles

Role‑based rights

Publishers, calendar operators, agents and team leads, records clerks. Everyone sees only what they need.

Oversight

Remote session oversight

Every remote connection is recorded, recordings can't be downloaded, and every view is logged.

Questions

Security questions

Where is the data stored?

On your server: the PostgreSQL database, files and logs. The portal doesn't depend on external cloud services.

How are backups made?

Database and file backups run on a schedule with a system timer on the portal server.

Can external access be blocked?

Yes. Access from outside always requires an app code, and at the web server level it can be restricted or closed. Single sign‑on can be denied to specific people.

Bring it all into one window

We'll show every module on a demo stand with sample data, walk you through the local AI pilot and talk through installing it in your infrastructure.

[email protected]