Permission Set for Log Views

Unlock the full potential of secure, role-based access to Log Views in Nodinite. This page guides you through configuring permission sets, empowering you to control who can view, download, resend, or repair messages—ensuring compliance, security, and operational efficiency.

• ✅ Granular, role-based access control for Log Views
• ✅ Empower users with self-service options while maintaining security
• ✅ Advanced features: view, download, transform, resend, and repair messages
• ✅ Flexible permission inheritance and global settings

Nodinite features robust role-based security. The Permission Set allows you to grant or revoke end-user rights to interact with Log Views.

Example: The Economy role with configuration options for Log Views.

The following permissions are available in the Log Views permission set:

Visual overview: Permission relationships for Log Views in Nodinite

Global Permissions

The global Access Log permission controls whether a user can access the Log functionality at all. This is the highest-level permission and must be set to Allow for users to see any Log Views.

Log Permissions tab showing Global permissions (Access Log) and individual Log View permissions.

Access Log

To access Nodinite Log Views, a User must belong to a Role with Allow access to the Log.

Access rights configuration for Log Views

1. The Role is set to Allow access to the Log.
2. The Role can have different access rights to individual Log Views.
   • Allow – Log View is visible and accessible to the end-user.
   • Deny – Log View is NOT visible or accessible to the end-user.

Note

If a User is a member of any Role where access to the Log is denied (Deny), the user is blocked from accessing ALL Log Views.

Log View Permissions

The following permissions can be configured individually for each Log View:

View Context

Granting the View Context permission in Log Views enables end-users in Roles to access the Context Values tab.

The Context Values tab in a Log View

• Inherited – Context data is visible if the global setting is Allow; otherwise, it is not.
• Allow – Context data is visible and accessible.
• Deny – Context data is NOT visible or accessible.

To further protect sensitive context data, Nodinite can mask values for end-users. See the ProtectedContextValues guide for details.

View Body

With the View Body permission, end-users in Roles can view the message Body in Log Views.

The View message Body action menu in a Log View

This permission also enables users to Download the body/payload. Various download options (single, multiple, etc.) are available in the Web Client.

Single download example

• Inherited – The Body (RAW data) is visible and downloadable if the global setting is Allow; otherwise, it is not.
• Allow – Log View is visible, accessible, and downloadable.
• Deny – Log View is NOT visible, accessible, or downloadable.

View Transformed

Nodinite can render the payload (Body) in alternative formats using a Stylesheet. This feature helps your business better understand message content and filter or mask sensitive data.

• Inherited – Transformation is available if the global setting is Allow; otherwise, it is not.
• Allow – Transformation is available to the end-user.
• Deny – Transformation is NOT available.

Resend

With the Resend permission, end-users in Roles can resend the message Body from Log Views.

The Resend action menu in a Log View

Users can Resend the body/payload with various options in the Web Client.

• Inherited – The Resend feature is available if the global setting is Allow; otherwise, it is not.
• Allow – Log View is visible, accessible, and downloadable.
• Deny – Log View is NOT visible, accessible, or downloadable.

Note

The AllowResubmit System Parameter must be set to true; otherwise, the Resend feature is disabled.

Repair

Granting both Resend and Repair permissions allows end-users in Roles to repair the message Body.

Repairing and resending messages is an advanced feature. To Repair a Log Event, first click View Details.

View details action button

A new tab opens in the Client Browser. On this page, click Repair and resubmit.

The Repair and resubmit menu button

The Repair and Resubmit modal for a selected Log Event

With this grant, end-users can Repair and Resubmit the body/payload using the Web Client.

• Inherited – The Repair and Resubmit feature is available if the global setting is Allow; otherwise, it is not.
• Allow – The Repair and Resubmit feature is visible and accessible.
• Deny – The Repair and Resubmit feature is NOT visible or accessible.

Note

The AllowResubmit and AllowRepair System Parameters must be set to true; otherwise, the Repair and Resubmit feature is disabled. The Resend permission must also be set to Allow.

Note

The Nodinite Administrator role can be configured to Deny access to the Log and all related permissions. This allows you to limit even the built-in administrator role with specific permissions while restricting access for others to sensitive log data.

• This is possibly dangerous and should be used with caution. Always ensure that at least one user has access to the Log and related permissions to avoid being locked out of critical log data.
  
  Example of the Nodinite Administrator role with Deny access to the Log and all related permissions.

Permission Inheritance and Summary

The net assigned rights for a User are determined by the combination of all their assigned Roles. If any assigned Role has Deny access to the Log, the user is denied access to all Log Views regardless of other permissions.

Permission inheritance and conflict resolution for Log Views in Nodinite

Next Step

Add or manage Role
Add or manage Log View
Add or manage Monitor View

Related Topics

Monitor Views permission set
Repository Model permission set

Administration
Access Management
Log Views
Monitor Views
Repository Model
Users