- 10 minutes to read

Add or manage User

This guide shows you how to add individual users to Nodinite and assign them to Roles for role-based access control. Individual users provide granular, person-by-person access for external partners, executives, or anyone requiring special permissions.

New to Users? See What is a User to understand when to use individual users vs Windows AD Groups.

Add the User CONTOSO ella.warehouse with a description, an e-mail address, and the Role Contoso: Warehouse Staff, animated walkthrough (7.12)
Animated walkthrough: a new User with one Role, ready in the list.

  1. In the Users Overview, click Add User.
  2. Type the User name (CONTOSO\ella.warehouse), the Additional information, and the E-mail address for the E-mail Alarm Plugin.
  3. On the Roles card, click Edit, tick Contoso: Warehouse Staff, and click Confirm and close.
  4. Click Save and close. Filter the list on ella: the new User is there.

Before You Begin

  • Administrator access required - You must be assigned to the Administrators Role
  • Valid Windows account - User must have a Windows domain account (or local account in Workgroup mode)
  • Know the user name - DOMAIN\username (e.g., CONTOSO\alice.smith) or the UPN, username@domain.com

Step 1: Open the Add User interface

Navigate to Administration → Access Management → Users in the Nodinite Web Client sidebar.

Click the Add User button to create a new User.

Add User button on the Users Overview page (7.12)
The Add User button sits above the Users list.

To edit an existing User, click on the user name from the list in the Users Overview.

Step 2: Enter user details

Configure the user's Windows account name and optional metadata.

Add User form under the breadcrumb Administration / Users / Add User, with an empty User name box, Additional information, E-mail address, and the Roles card (7.12)
Only User name is required; the E-mail address is used by the E-mail Alarm Plugin. A new User shows the General tab only; the permission tabs appear once it is saved. The User name box opens empty, with no format error until you type.

Mandatory Fields

User Name

The User name field is required and must match an existing Windows account. The form accepts three formats: DOMAIN\UserName, UserName@domain.com, or UserName@domain.

Examples
  • CONTOSO\alice.smith - Domain user
  • alice.smith@contoso.com - The same user in UPN format
  • PARTNER\john.vendor - External consultant from trusted domain
  • .\localuser - Local Windows account on the Nodinite server
Common Mistakes
  • Don't use: Contoso/alice.smith (forward slash instead of backslash)
  • Don't use: alice.smith (no domain)
  • Don't use: a reserved name: administrator, guest, admin, root, or system

User name field with a forward slash between domain and user, and the error listing the three accepted formats (7.12)
The form rejects a user name in any other format and names the three it accepts.

The form also checks the parts of a DOMAIN\UserName name: the domain is 1–15 characters, and the user name is at most 20 characters, doesn't start or end with . or -, and contains none of \ / [ ] : ; | = , + * ? < > @ ".

Tip

Copy the exact username from Active Directory Users and Computers to avoid typos.

Optional Fields

Additional Information

A user-friendly description to document why this user has access or what their role is.

Best Practices
  • Include the person's job title or department: "Finance Department Manager"
  • Document temporary access expiration: "External consultant - access expires 2026-06-30"
  • Note special permissions: "CTO - executive dashboard access"
Examples
  • "SAP integration specialist from vendor Contoso Corp"
  • "VP of Operations - read-only monitoring access"
  • "Temporary contractor for Project Phoenix migration"

E-mail address

The e-mail address for receiving monitoring alerts from the Monitoring Service via Alarm Plugins.

Important Notes
  • The E-mail address is only used by the E-mail alarm plugin - it does not affect authentication
  • For easier maintenance, prefer E-mail with options which can use AD email attributes
  • Leave blank if user should not receive monitoring alerts
Examples
  • alice.smith@contoso.com - Corporate email
  • john.vendor@partner.com - External consultant email
  • emergency-team@contoso.com - Distribution list for critical alerts

Step 3: Assign Role membership

Assign the User to one or more existing Roles to grant access to specific Log Views and Monitor Views.

Assign Roles to User dialog filtered on Contoso, with the All and Selected tabs, Include deleted, and Confirm and close (7.12)
Check the Roles for the User and click Confirm and close; the Selected tab shows the current Roles.

How Role Assignment Works

  • Multiple Roles allowed - Users can be assigned to as many Roles as needed
  • Cumulative permissions - User receives all the Allows from all assigned Roles
  • A Deny wins - A right set to Deny in any of the User's Roles is denied, even if another Role allows it; a right that no Role sets is denied too

Example: Two Roles

  • Assign to Role: "Production Logs" (access to production Log Views)
  • Assign to Role: "SAP Specialist" (access to SAP-specific Repository Model items)
  • Result: User has access to Production Logs + SAP Repository items (combined)

Tip

Start with minimal Role assignments (principle of least privilege), then add more Roles as needed based on user requests.

Step 4: Save and verify access

Click Save (or Save and close) to create or update the User. The new User, its changes, and its Role memberships are recorded in the Log Audits; sign-ins are not.

Verify the User Can Log In

  1. User opens Nodinite Web Client in browser
  2. User authenticates with Windows credentials (DOMAIN\username)
  3. User should see Log Views and Monitor Views from assigned Roles

Check the Effective Permissions

A saved User has the tabs Log Permissions, Monitor Permissions, C4 Set Permissions, and Repository Permissions. They show, read-only, the net rights the User gets from the Roles assigned to it directly. Roles that come through a Windows AD Group are added only when the user signs in, so they don't show here. After you save a change to the User's Roles, the tab counts, such as Log Permissions (2), and their rows refresh at once; no page reload is needed. Use the tabs to confirm access without logging in as the user.

User editor for CONTOSO alice.smith on the Log Permissions tab, with Access Log allowed and the rights for two Log Views (7.12)
Net rights for one User: Allow and Deny per right, combined from every Role. See Permission Set for Log Views for what each right means.

Warning

If the user cannot log in, see the Troubleshooting section below.

Common Scenarios

Scenario 1: Add External Consultant

Situation: Vendor consultant needs 60-day access to SAP integration logs.

Steps

  1. Click Add User
  2. Enter User name: PARTNER\john.consultant
  3. Enter Description: "Vendor consultant for SAP troubleshooting - access expires 2026-04-30"
  4. Enter E-mail address: john.consultant@partner.com
  5. Assign to Role: "SAP Production Logs"
  6. Click Save
  7. Set calendar reminder to remove user in 60 days

Scenario 2: Grant Executive Dashboard Access

Situation: CTO needs read-only visibility into all production integration health.

Steps

  1. Click Add User
  2. Enter User name: CONTOSO\cto
  3. Enter Description: "CTO - executive monitoring dashboard"
  4. Enter E-mail address: cto@contoso.com
  5. Assign to Roles: "Production Monitor Read-Only" + "Executive Dashboard"
  6. Click Save

Scenario 3: Temporary Contractor Access

Situation: 3-month contractor needs limited test environment access.

Steps

  1. Click Add User
  2. Enter User name: CONTOSO\temp.contractor
  3. Enter Description: "Temporary contractor - Project Phoenix - expires 2026-05-15"
  4. Leave E-mail address blank (no monitoring alerts needed)
  5. Assign to Role: "Test Environment Access"
  6. Click Save
  7. After project ends, remove entire User from Nodinite

Troubleshooting

User Cannot Log In

Symptom: User enters Windows credentials but is denied access to Nodinite.

Possible Causes

  1. User not added to Nodinite Verify user appears in the Users Overview list
  2. User name format incorrect: Check for typos, verify DOMAIN\username format
  3. Windows account doesn't exist: Confirm account exists in Active Directory
  4. Trusted domain issue: For external users, verify domain trust relationship configured
  5. IIS authentication disabled: Verify Windows Authentication is enabled in IIS for the Nodinite Web Client, see IIS Authentication settings

Resolution

Check each cause above, correct configuration, ask user to retry login.

User Can Log In But Sees No Data

Symptom: User successfully logs in but sees empty lists or "No data available" messages.

Possible Causes

  1. No Roles assigned: User must be assigned to at least one Role
  2. Roles have no Views: Assigned Roles don't have any Log Views or Monitor Views configured
  3. Views have no data: Log Views/Monitor Views exist but contain no log entries or monitors yet

Resolution: Assign user to Roles with active Log Views or Monitor Views, verify Views contain data.

"Must be in format" Error

Symptom: The red message Must be in format: DOMAIN\UserName, UserName@domain.com or UserName@domain appears under User name.

User name field with a forward slash between domain and user, and the error listing the three accepted formats (7.12)
The same validation error as in Step 2.

Cause: The user name is in none of the three accepted formats, or one of its parts breaks a rule.

Resolution

  • Use backslash \, not forward slash /, between domain and user name, or use the UPN (user@domain.com)
  • Include the domain: a user name on its own isn't accepted
  • Keep the domain to 15 characters and the user name to 20, without \ / [ ] : ; | = , + * ? < > @ ", and not starting or ending with . or -
  • Don't use a reserved name: administrator, guest, admin, root, or system
  • For local accounts use .\username format

User Not Receiving Email Alerts

Symptom: User should receive monitoring alerts but email never arrives.

Possible Causes

  1. E-mail address blank: No E-mail address set on the User
  2. Alarm plugin not configured: E-mail or E-mail with options plugin not set up on Monitoring Service
  3. Monitor not configured for alerts: Monitor doesn't have alarm plugin actions configured
  4. Email address incorrect: Typo in email address

Resolution: Verify email address in User settings, check alarm plugin configuration, test with simple test alert.

Best Practices

User Naming and Descriptions

  • ✅ Use descriptive Additional Information - Document why user has access, who they are, when access expires
  • ✅ Include expiration dates - For temporary access, note end date in description
  • ✅ Document business justification - "Approved by CTO for audit purposes"

Role Assignment

  • ✅ Start minimal - Assign only necessary Roles initially
  • ✅ Review quarterly - Periodically review user list and remove inactive users
  • ✅ Prefer AD Groups for teams - Use individual Users only for exceptions (see Windows AD Groups)

Email Configuration

  • ✅ Use corporate email - Not personal email addresses
  • ✅ Test alert delivery - After adding user, trigger test alert to verify email works
  • ⚠️ Don't use distribution lists - Unless entire group should receive alerts for this specific user's permissions

Security and Access Reviews

  • ✅ Document access grants - Use Additional Information field to note approval
  • ✅ Remove promptly - Delete users immediately when access no longer needed
  • ✅ Monitor audit logs - Review the Log Audits for unexpected changes to Users and Role memberships (sign-ins are not recorded)
  • ✅ Follow least privilege - Grant minimum access required for user's job function

Next Steps

What is a User - Understand when to use individual users vs Windows AD Groups
Add or manage Windows AD Group - Set up team-based access
Users Overview - View and manage all configured users

Add or manage Role - Create roles with specific permissions
Add or manage Log View - Define which logs users can access
Add or manage Monitor View - Configure monitoring dashboards

E-mail - Configure email alarm plugin for user notifications
E-mail with options - Advanced email configuration with AD integration

Access Management - Overview of Users, Groups, Roles, Claims, and Policies
What is a Role - Understand role-based access control

Log Audits - Track user activity and access changes
Monitoring Service - Background service that sends alert emails
Permission Set for Log Views - Rights a Role grants in Log Views
Permission Set for Monitor Views - Rights a Role grants in Monitor Views
Getting Started with Administration