Skip to main content
NodePad Enterprise gives administrators complete visibility into what’s happening inside their deployment and precise control over who can do what. The audit log captures a record of every user action, and role-based access control (RBAC) lets you define permissions at a granular level — down to individual canvas operations like forking and merging. Both systems are designed to satisfy the requirements of compliance reviews without requiring custom integrations or external tooling.

Audit logs

Every action taken in NodePad is written to the audit log. This includes user authentication events, canvas operations, model interactions, administrative changes, and access control modifications.

What gets logged

  • User sign-in and sign-out events
  • SSO authentication attempts (successful and failed)
  • Session creation and expiration
  • Password or credential changes (if applicable)
  • Canvas creation, deletion, and sharing
  • Node creation, editing, and deletion
  • Fork and merge actions, including which nodes were involved
  • Sticky note creation and modification
  • Model selections per message
  • Prompt submissions (metadata — timing, model, user — not necessarily content, depending on your configuration)
  • Role assignments and changes
  • User provisioning and deprovisioning events
  • SSO and SCIM configuration changes
  • Audit log export events

Exporting audit logs

Audit logs are exportable for use in compliance reviews, security investigations, or ingestion into your SIEM or log management infrastructure.
Because NodePad is self-hosted in Enterprise deployments, audit log data is written to your own infrastructure. You can configure log forwarding directly to your existing log aggregation system — no export step required if you prefer to stream logs in real time.
The audit log is immutable from within the NodePad application. Users and administrators cannot delete or modify log entries through NodePad’s interface.

Role-based access control

RBAC in NodePad lets you define exactly what each user or group can do. Roles are assigned to users directly or inherited through your identity provider’s group mappings when SCIM is configured.

Built-in roles

Viewer

Can read canvases and nodes they have been granted access to. Cannot create, edit, fork, merge, or administer.

Editor

Can create and edit nodes, fork threads, and merge results within canvases they have access to. Cannot administer.

Collaborator

Full read and write access within their assigned canvases, including forking and merging. Can share canvases with other members of the organization.

Administrator

Full access to all canvases and nodes in the deployment. Manages roles, configures SSO and SCIM, and accesses audit logs.

What RBAC controls

Roles govern access to the following operations in NodePad:
OperationViewerEditorCollaboratorAdministrator
Read canvasesYesYesYesYes
Create and edit nodesNoYesYesYes
Fork threadsNoYesYesYes
Merge threadsNoYesYesYes
Share canvasesNoNoYesYes
Manage rolesNoNoNoYes
Access audit logsNoNoNoYes
Configure SSO / SCIMNoNoNoYes
Role definitions above represent the default configuration. The Enterprise team can work with you to adjust permissions to match your organization’s access control policies.

Compliance-ready by design

NodePad Enterprise is built so that compliance reviews don’t require you to build custom tooling or ask NodePad to produce records on your behalf. Because your deployment runs on your infrastructure, your security and compliance teams have direct access to:
  • The audit log data store
  • Log export pipelines to your SIEM or compliance system
  • Role configuration and change history
  • Identity provider integration records
If your organization undergoes regular compliance reviews (SOC 2, HIPAA, ISO 27001, or similar), share this page and the self-hosting documentation with your compliance team early. Most evidence requirements can be satisfied directly from your own infrastructure without involving NodePad.

Get started

Audit log configuration and RBAC setup are handled as part of your Enterprise onboarding. Contact the team to discuss your compliance requirements and access control policies.

Contact the Enterprise team

Tell the team about your compliance framework and access control requirements, and they’ll configure NodePad to match.