Back to LifeNexaONE BRAND. MANY POSSIBILITIES.
SECURITY

Security in everyday work

Access based on identity, role and organisation context.

01

Shared sign-in and session control

Sign-in uses the OIDC Authorization Code flow with PKCE. Account and authentication settings are managed centrally. Ending a session removes that session’s access; selected administrative actions require additional identity verification.

02

Context of each organisation

The selected organisation and role determine access to data and actions. Permissions are checked in the API and PostgreSQL rules. Switching organisations changes the working context; knowing a resource’s address does not grant access to it.

03

Documents and service configuration

Organisation files are stored privately and made available after permissions are checked. Service provider secrets are stored in encrypted form on the server. The dashboard shows configuration status without revealing stored keys.

04

Controlled changes and history

Versioning content, price lists and configuration helps detect concurrent edits. Significant actions leave an audit record. Selected billing and publishing operations require separate approval.

05

Clear scope of implementation

Before production launch, we agree on the scope of data, roles, suppliers, backups and organisational requirements. Declarations of certification, formal compliance or guaranteed service parameters require separate confirmation in the documentation and contract.

06

Report a problem

For security concerns, email kontakt@lifenexa.pl. Include the website address, time of the incident and observed symptoms. Do not send passwords, API keys or personal data unrelated to the issue.

CONTACT

Let's talk about your organisation.

We will introduce the platform and the systems for your sector.