Managing the Nodinite Web Client
Unlock the full power of Nodinite with the Web Client. This guide shows you how to manage integrations, users, security, and assets with self-service, role-based access, and full audit logging.
✅ Empower business users with secure self-service
✅ Role-based access and policy management
✅ Full audit logging for compliance and traceability
✅ Restore deleted records and never lose critical data
✅ Fine-grained control over logging, monitoring, and repository assets
The Nodinite Web Client enables self-service for your business and uses Role based security.
Manageable assets
Learn more about the Web Client User Interface in the end-user guide for the Nodinite Web Client part of Core Services.
You must be a member of the Administrators role to manage Nodinite
Why does Nodinite not delete my records?
Nodinite almost never forgets anything—a delete operation is rarely a hard delete! Deleted records are flagged, not removed, and can be restored by an Administrator. This ensures auditability, long-term statistics, and peace of mind if mistakes happen. Learn more: Manage deleted records in the Web Client
1. Access Management
With Nodinite, you control who can access, read, or distribute sensitive content—such as medical records or business transactions—without direct server access. Role-based access lets you fix problems remotely from the Web Client and restrict or allow access to specific resources, all with full auditing. Avoid giving unnecessary admin rights and always know who did what, when, and where.
All that you do is being Log Audited
All operations that change data, or involve sensitive actions like downloads or message views, are logged in a tamper-resistant Log Audits storage. Only users in the Administrators role can access the Audit Log via the Web Client User Interface or Web Api.
The Audit Log helps you:
- Avoid blame-game discussions
- Track all remote actions and changes
- Know exactly who did what and when
Policy based access management
Nodinite uses Windows Integrated Security. To access the Web Client User Interface, a Nodinite Administrator must register the end-user as a User or as part of a Windows Group, then assign them to the right Roles.
The policy is governed by a predefined Administrators Role
A registered user with access to the Web Client User Interface menu.
Users in the Administrators role also have access to Administration and full edit rights to manage the Repository Model.
A user in the predefined Administrators role has access to additional menu items in the Web Client User Interface
What is a Role?
Nodinite uses Role based security to grant Users access to Log Views and Monitor Views. The special Administrators role cannot be changed except for its associated Users and Groups.
Quick facts for a Role:
- Unique name
- Any number of Roles can be defined
- Any number of users or Windows AD Groups can be associated
- Users and groups can belong to multiple Roles
Add or manage Role - Roles enforce policy on:
- Log Views
- Monitor Views
- Administrators Role - Full access to all Nodinite operations
What is a User?
A User is an entity with a Windows identity (Domain\UserName). Only Administrators can manage Users. Unregistered users or those not in a Windows AD Group are denied access and prompted for credentials.
Note
By default everything is disallowed and an Administrator must explicitly Allow or Deny what authenticated users can see and do.
Example: Access rights for nodinitedemo01\demouser for Log Views
Example: Access rights for nodinitedemo01\demouser for Monitor Views
A registered User who is not an Administrator and has no associations to Log Views or Monitor Views is still granted logon rights (with very limited features). This is similar to the public grant in SQL databases.
Quick facts for a User:
- Unique name
- Any number of Users can be defined
- Optional email address for E-mail plugin in Monitor Views
- Deny always wins
What is a Windows AD Group?
A Windows AD Group is an entity with the name 'Domain\GroupName'.
Quick facts for a Windows AD Group:
- Unique name
Important
If you change the group name in Windows AD, Nodinite will not recognize it until updated.
- Any number of Windows AD Groups can be defined
Important
Do not use the built-in local administrators group
- No email info for members; add manually for email plugin or E-mail with options in Monitor Views
- Can be a member of one or many Roles
2. Manage the Repository Model
Create Integration Landscapes like the image below by using the Repository Model.
Design your integration flows using Nodinite Repository Model
3. Logging
With Nodinite, you get end-to-end logging of your workflows and can provide custom-built self-service Log Views for your business. Tailor layouts for specific needs and empower users to access the data they need.
With Nodinite, you can filter returned data to any detail level. You may not want to (or legally can) share everything. Examples:
- Anything on selected Endpoint
- All Orders
- All failed orders last month
- All orders to customer X
- Users can search for approved invoices to supplier X with an amount > $100, no older than 3 days
- Find all orders missing a corresponding order response (with Ack/Nack management and alerts for exceeded thresholds)
Nodinite supports creating Log Views to control what data to list, columns, order, grouping, and user permissions (view, download, resend, repair, etc.).
- Provide self-service Log Views for your business
- Manage access Users and Roles
- Manage Log Agents
- Manage Search Fields
- Manage Log Status Codes
4. Monitoring
Nodinite delivers end-to-end monitoring and a self-service portal for your business and support teams. Use Monitoring Agents to detect problems and resolve issues securely and instantly. The Repository Model enhances self-service and knowledge sharing.
Nodinite provides Monitor Views to group related Resources (e.g., all dependencies for an invoicing integration flow).
Invoicing Integration
Even simple integrations have many Resources and dependencies. Information is key for different stakeholders at different times.
Administrators can provide role-based Monitor Views for fine-grained solution management. Users only see explicitly allowed Resources. Custom Remote Actions (stop/start, etc.) can be enabled. Monitor Views often eliminate the need for Remote Desktop Sessions and admin privileges.
Note
All actions in Nodinite are log audited.
Log Audits - Stay secure
The Monitoring capabilities of Nodinite are provided by Monitoring Agents, governed by the Monitoring Service. Agents provide Resources with different states. User-specific alerts are configured in Monitor Views. Monitor is where you access and configure Monitor Views.
There can be any number of Monitor Views defined.
- Manage Monitor Views
- Manage Resources
- Manage Categories
- Manage Applications
- Manage Monitoring Agents
5. Customization of content that affect users
Review the System Parameters user guides for more information.
6. Settings for Administrators
From Nodinite 5.1 and later, even Administrators may be blocked from using Monitoring and Logging features.
Example: Members of the built-in Administrators role denied access to a specific Log View