CurNext
Audit trail
CurNext keeps a project-bound record of who did what, when - from access and admin actions to readiness decisions, device lifecycle, and GDPR-oriented events.
This page describes the product audit trail buyers and site teams use in the CurNext platform. It is not a live log viewer. Open the dashboard for your project history.
Why it exists
Handover evidence
Show clients and consultants what was measured, when readiness changed, and who acknowledged alerts - without rebuilding spreadsheets after the fact.
Accountability
Invite-only access, RBAC, and privileged MFA sit behind actions that matter. Sensitive operations leave a trail tied to identity and time.
Claims and compliance conversations
Leak events, curing packages, and drying decisions stay mapped to the project structure so insurers, auditors, and owners can review a coherent story.
What gets recorded
Event coverage grows with the platform. Publicly we describe categories - not every internal field name.
| Category | Examples |
|---|---|
| Access & identity | Invites, sign-in outcomes, role changes, permission denials, session-sensitive admin steps |
| Project & membership | Project creation, member add/remove, subscription and seat-related admin actions where applicable |
| Devices & OTA | Provisioning and verification themes, assignment to spaces, firmware stage and apply outcomes at the edge |
| Readiness & ops | Status transitions, alert create/acknowledge/resolve, exports and report generation where offered |
| Privacy / GDPR | Structured audit events for access, export, and erasure paths - secrets are not written into logs |
How the trail is shaped
Bound to the building
Events sit in project and BIM context - buildings, spaces, and devices - so a sensor dump is not the whole story.
API-visible where licensed
Professional integrations can list audit events via the REST API and SDKs for scripts and internal tools.
Integrity themes
Cloud design targets append-friendly, integrity-conscious records. Hash themes (for example SHA-256) support audit integrity in the security architecture.
Retention with purpose
Retention follows product and contractual needs. Some security and GDPR audit streams may be append-only or pseudonymized rather than casually rewritten.
Who can see what
CurNext is invite-only and does not onboard product users under 18 under internal policies. New Google or email accounts do not auto-provision into a project without an invite or existing membership.
Project roles
Visibility follows RBAC on the project. Site and company admins see broader history than read-only collaborators.
Privileged actions
Elevated admin and security-sensitive steps expect stronger authentication and leave clearer accountability.
Tenant isolation
Audit history is scoped to your organisation and projects - not a shared public feed across customers.
Related
Security or privacy questions:[email protected][email protected]
Translations are provided for convenience. Where a signed agreement exists, the English instrument controls.