IT · Access and operations
Trace access, integrations and changes
LabNote.Light brings people, roles, visibility, API access, webhooks and audit events together in clear administrative workspaces.
- Tenant-scoped records
- Capability-based roles
- Data stored in Frankfurt
In IT operations
Access needs to be explainable
Roles, exceptions, data flows and logs need to make sense together — especially during staff changes, integration failures and reviews.
Effective access is unclear
A base role, targeted overrides and visibility rules need to be reconciled for a specific person.
Integrations are hard to monitor
Secret, event selection, delivery and failure status need to be visible in one place.
Logs are hard to assess
Without filters, record details and integrity checks, assessment takes longer than it should.
Privileged access needs boundaries
Administrative and support actions need narrow scope, time limits and distinct records.
Access governance
From person to effective access
Organisational assignment, permissions and visibility stay separate. Their combined effect is visible in one place.
- 01
Organise
Assign people to departments and teams.
- 02
Set role
Choose a fixed role or build a custom role on a system role.
- 03
Inspect access
Review capabilities, additions and restrictions in the matrix and inspector.
- 04
Add visibility
Define cross-department visibility bridges only where they are needed.
People and access
Inspect effective permissions in one place
Custom roles combine a system base role with targeted capability additions or restrictions. The matrix and person inspector show the resulting access picture.
API and webhooks
Operate credentials and deliveries separately
API keys carry scopes and expiry dates. Webhook endpoints retain event selection, active state, tests, delivery logs and secret rotation. Signed deliveries use HMAC-SHA256.
Audit trail
Filter events, inspect records and verify the chain
The audit trail can be filtered by person, event and date range. Record detail, export and verification history support review; the hash chain is designed for tamper evidence and externally anchored.
Concrete capabilities
Controls that can be named and inspected
Tenant scope
Organisation records and API access are bounded by organisation and server-side access rules.
Administrative export
Organisation and data-subject exports follow separate purposes, permissions and technical limits.
Controlled support access
Privileged support access is time-limited, tied to strong authentication and recorded distinctly.
Operational status
Status probes and integration logs expose technical failures. They do not replace the customer's own monitoring setup.
Common questions
Does LabNote.Light support custom roles?
Yes. A custom role label builds on a system role and can add or remove individual capabilities. Fixed roles and server-side rules remain the foundation.
Is SSO available by default?
No. SSO depends on the identity provider and infrastructure plan. We assess it for each deployment; there is no general self-service or one-click option.
Is the audit trail immutable?
LabNote.Light uses a hash chain with external time anchoring to make later changes detectable. This is tamper evidence, not a blanket immutability or compliance guarantee.
Can LabNote.Light be self-hosted?
Self-hosting is not currently offered as a product commitment. The database, authentication, files and server-side functions are provided through Supabase on AWS in Frankfurt. Identity, data-flow and export requirements are assessed during early access.
Review IT requirements in early access
During early access, we assess roles, visibility, identity requirements, integrations, exports and audit review against your operating model. General release is planned for 2027.