- 11 minutes to read

What is a Windows AD Group?

Grant Nodinite access to whole teams at once. A Windows AD Group in Nodinite is an Active Directory security group mapped to one or more Nodinite Roles. Instead of granting access to individual Users one at a time, you grant access to an entire AD group, and all group members automatically inherit the permissions of the Roles.

  • ✅ Automatic provisioning - Users added to the AD group automatically get Nodinite access
  • ✅ Centralized management - Control access in Active Directory, not in multiple systems
  • ✅ Reduced administrative overhead - Manage 50 users by adding one group instead of 50 individual users
  • ✅ Organizational alignment - Access structure mirrors your org chart and team structure
  • ✅ Simplified auditing - Review group membership in AD for compliance reporting
  • ✅ Faster onboarding - New team members get access by joining existing AD groups

A member of a mapped AD group opens the Log View of the group's Role and searches an order, with nothing set up for the user personally, animated walkthrough (7.12)
Animated walkthrough: what a group member gets. The recording uses the dev domain's own group, DEV\Domain Users.

  1. The group is mapped to the Role Contoso: Operations.
  2. A user who has no User entry and no Role of their own signs in. Log lists the Role's Log View Contoso: Orders.
  3. The user opens the Log View and searches the order number ORD-10001.
  4. The result appears. Nothing was set up for the user personally: the access comes from the group.

Overview

This approach uses your existing Active Directory infrastructure for centralized Access Management, reducing administrative overhead and keeping access control synchronized with your organizational structure. You manage the groups in the Windows AD Groups Overview.

Windows AD Groups list with three Contoso groups, the filter box, Include deleted, the Add Windows AD Group button, and an Action button per group (7.12)
Each group is listed by its domain-qualified name.

Note

Windows Authentication Mode Required

Windows AD Groups are used when your Nodinite environment is configured for Windows Authentication mode. Nodinite supports two authentication modes, chosen in the Auth step when you set up the environment:

If you use OAuth 2.0 / OIDC authentication (Install Nodinite v7 - OpenID), see Claims and Policies instead. To switch modes, see Migrate Authentication Method.

How Windows AD Groups Work

Authentication and Authorization Flow

flowchart LR U["fa:fa-user User signs in<br/>with Windows credentials"] --> IIS["fa:fa-server IIS<br/>Windows Authentication"] IIS -->|"authenticates against"| AD["fab:fa-windows Active Directory"] AD -->|"group memberships"| N["fa:fa-shield-halved Nodinite<br/>matches Windows AD Groups"] N -->|"group is member of"| R["fa:fa-users-class Roles"] R -->|"cumulative permissions"| A["fa:fa-unlock Log Views, Monitor Views,<br/>Repository Model"] style U fill:#2678BD,color:#fff style IIS fill:#9E59BB,color:#fff style AD fill:#9E59BB,color:#fff style N fill:#E47528,color:#fff style R fill:#E47528,color:#fff style A fill:#93d16d,color:#000

Blue: the user; purple: Windows infrastructure (IIS and Active Directory); orange: Nodinite authorization; green: the access granted.

  1. User logs in to the Nodinite Web Client using Windows credentials
  2. IIS authenticates the user against Active Directory (see IIS Authentication settings and NTLM vs Kerberos Authentication)
  3. Nodinite reads the user's groups from the Windows logon token (Kerberos ticket) on every request, including the groups the user belongs to through nested groups
  4. Group-to-Role mapping is evaluated - which Nodinite Roles are assigned to the user's AD groups
  5. Permissions are granted based on all Roles assigned to the user's groups, added to the Roles of the user's own User entry, if any (permissions are cumulative). A user needs no User entry.

When changes take effect

  • A change in Active Directory reaches Nodinite when the user gets a new Windows token: the user signs out of Windows and in again. Signing out of Nodinite alone doesn't help, because the browser signs in again with the same token.
  • A change in Nodinite (a group, its Roles, or a Role's rights) takes effect within a minute.

Example Scenario

Active Directory Setup

  • AD Group: CONTOSO\Integration Team (members: Alice, Bob, Charlie)

Nodinite Configuration

  • Windows AD Group: CONTOSO\Integration Team
  • Assigned to Roles: "Developer" + "Test Environment Access"

Result

  • Alice, Bob, and Charlie can all log in to Nodinite
  • They automatically have Developer permissions and Test Environment Access
  • When David joins the AD group, he gets the same access after he signs out of Windows and in again
  • No changes needed in Nodinite

Windows AD Groups vs Individual Users

Understanding when to use each approach helps optimize your access management strategy.

Factor Windows AD Groups Individual Users
Best for Teams, departments, roles with many members External users, special cases, fine-grained control
Management location Active Directory (centralized) Nodinite (application-specific)
Provisioning speed Automatic when user joins AD group Manual - must add each user individually
Typical use case 10+ users with similar permissions Partners, vendors, unique access requirements
Maintenance effort Low - managed in AD Higher - managed per user in Nodinite
Access revocation Remove from AD group (at the user's next Windows sign-in) Must remove from Nodinite manually
Audit trail AD group membership reports Nodinite user list and Log Audits
Flexibility Group-level permissions Per-user permissions
Organizational sync Automatic - reflects AD structure Manual - must mirror org changes

When to Use Windows AD Groups

Choose Windows AD Groups when:

  • ✅ You have multiple users with the same access requirements (teams, departments)
  • ✅ You want automatic provisioning - users join AD group, they get Nodinite access
  • ✅ You prefer centralized management - control access in one place (Active Directory)
  • ✅ You need to align access with org structure - mirroring teams, departments, or projects
  • ✅ You want to reduce administrative overhead - one group instead of many individual users
  • ✅ You use AD group nesting for hierarchical access (e.g., EMEA Team → Finance Team → Finance Admins)

When to Use Individual Users Instead

Choose individual Users (Add or manage User) when:

  • ✅ You have external users (partners, vendors, contractors) not in your Active Directory
  • ✅ You need fine-grained control over specific individuals
  • ✅ The user count is small and doesn't justify creating an AD group
  • ✅ You need temporary access not worth creating an AD group for
  • ✅ Access requirements are unique to the individual, not shared with others

Mixing Both Approaches

Nodinite allows you to mix Windows AD Groups and individual Users on the same Role.

Example: One Role, Three Assignments

  • Role: "Production Monitor"
  • Assigned to:
    • Windows AD Group: CONTOSO\Operations Team (20 members)
    • Individual User: PARTNER\john.vendor (external consultant)
    • Individual User: CONTOSO\jane.executive (special access for VP)

Result: All 22 people have Production Monitor access, managed through different mechanisms based on what makes sense for each.

A User's effective-permission tabs count only the Roles assigned to that User directly. The Roles a user gets through a Windows AD Group are added at sign-in; see What is a User?.

Prerequisites and System Requirements

Infrastructure Requirements

Before using Windows AD Groups in Nodinite, your environment must meet these requirements:

  • A Windows server with IIS hosting the Nodinite Web Client and Web API, with Windows Authentication enabled (IIS Authentication settings)
  • Server is domain-joined - must be part of the Windows domain or forest
  • Domain trusts configured (if accessing groups from other domains/forests)
  • Active Directory accessible from the Nodinite server
  • Security groups exist in Active Directory (not distribution groups)

System Configuration

Enable Windows AD Groups Feature

Windows AD Groups are disabled by default: on a new installation the UseActiveDirectoryGroups System Parameter is false. To enable them:

  1. Navigate to Administration → Settings → System Parameters
  2. Find the UseActiveDirectoryGroups System Parameter
  3. Set the value to ** rue** and click Save

While the value is false, Nodinite ignores the groups when users sign in (no Roles through groups), and hides the Windows AD Groups menu item and the Role editor's Windows AD Groups card. The groups stay in the database and work again when you set the value back to true.

UseActiveDirectoryGroups System Parameter edit page with the Value set to true (7.12)
The UseActiveDirectoryGroups System Parameter page; select true and click Save to enable Windows AD Groups.

A change takes effect within about 15 seconds; no restart is needed.

Permissions and Access Control

Administrator Role Required

You must be a member of the Nodinite Administrators Role to:

  • Add or manage Windows AD Groups
  • Assign groups to Roles
  • Configure all other administrative objects in Nodinite

The Administrators role is a built-in Role in Nodinite that:

  • Cannot be renamed
  • Cannot be deleted
  • Grants full administrative access
  • Is created during initial installation

See Access Management for complete details on the authorization model.

Cumulative Permissions

When a user's AD group is assigned to multiple Roles, they receive all permissions from all Roles (cumulative, not restrictive). What each Role grants is set in its permission sets: Log Views, Monitor Views, Repository Model, and C4 Diagram Sets.

Example: Developer Group in Two Roles

  • User is member of AD group CONTOSO\Developers
  • CONTOSO\Developers is assigned to:
  • User gets: Test Log Views + Repository Model access (combined permissions)

Limitations and Important Notes

The Administrators Group Name

A group named Administrators cannot be added to Nodinite as a Windows AD Group, in any domain, so BUILTIN\Administrators is refused too, in the editor and in the Web API. This is a security restriction to prevent unintended administrative access. Nothing else treats the Windows Administrators group specially: Nodinite Administrators are the members of the Nodinite Administrators Role.

Workaround: Create a dedicated AD group for Nodinite administrators (e.g., CONTOSO\Nodinite Admins) instead of using the built-in Windows Administrators group.

No Automatic Name Validation

Nodinite does not validate whether the Windows AD Group name you enter actually exists in Active Directory: it never asks Active Directory, and accepts any DOMAIN\GroupName. What it does check: both parts are present and 1–256 characters long, the name isn't already used, and the group name isn't Administrators. Otherwise the editor says Domain length should be between 1 and 256 characters and Active Directory Group name 1 and 256 characters and group name Administrators can not be used.

What This Means

  • Spelling matters - Ensure the group name is spelled exactly as it appears in AD
  • Format matters - Must use DOMAIN\GroupName format (backslash, not forward slash)
  • Case sensitivity - Group names are compared case-insensitively, with or without the machine or domain prefix
  • Manual verification required - Test by having a group member log in

Best practice: Copy the exact group name from Active Directory (via PowerShell Get-ADGroup or AD Users and Computers) to avoid typos.

Group Renames Require Manual Updates

If someone renames a Windows AD Group in Active Directory:

  • Nodinite continues referencing the old name
  • Users will lose access until the name is updated in Nodinite
  • No automatic synchronization occurs
  • Nodinite Administrator must manually update the group name in Nodinite

Recommendation: Coordinate with your Active Directory administrators to be notified of group renames affecting Nodinite access.

Security Groups Only (Not Distribution Groups)

Only Active Directory Security Groups work with Nodinite. A Windows token carries security groups only, so distribution groups (used for email) never reach Nodinite.

Deleted in Active Directory or in Nodinite

  • Deleted in Active Directory, still in Nodinite: no token carries the group any more, so it grants nothing. Its row stays until you delete it.
  • Deleted in Nodinite: the group is no longer evaluated. Users who only had access through it lose that access within about a minute. Users who also have a User entry or another group keep what those give. Restore brings the group back with its Roles.

Verify group type in PowerShell:

Get-ADGroup -Identity "Integration Team" | Select-Object Name, GroupCategory
# GroupCategory should be "Security", not "Distribution"

Common Scenarios

Scenario 1: Department-Based Access

Situation: Finance department needs access to SAP integration logs

Solution: Reuse the Finance Group

  1. Use existing AD group CONTOSO\Finance Team (or create if doesn't exist)
  2. In Nodinite, add Windows AD Group CONTOSO\Finance Team
  3. Assign to Role "Finance Log Access" (configured with SAP Log Views)
  4. All Finance team members automatically get access

Benefits: When finance hires new staff, they join the AD group and automatically get Nodinite access.

Scenario 2: Multi-Tier Support Team

Situation: L1 support needs monitoring access, L2 support needs logs + monitoring, L3 needs full access

Solution: One Group per Support Tier

  1. Create AD groups: CONTOSO\Support L1, CONTOSO\Support L2, CONTOSO\Support L3
  2. Add all three as Windows AD Groups in Nodinite
  3. Assign to Roles:
    • L1 → "Production Monitors" (Monitor Views)
    • L2 → "Production Monitors" + "Production Logs"
    • L3 → "Production Monitors" + "Production Logs" + "Repository Model" + Remote Actions
  4. Users get appropriate access based on their support tier

Benefits: Support team structure in Nodinite mirrors organizational support levels.

Scenario 3: Project-Based Temporary Access

Situation: 12-person project team needs access to Project Phoenix integration logs for 6 months

Solution: A Temporary Project Group

  1. IT creates temporary AD group CONTOSO\Project Phoenix
  2. Add as Windows AD Group in Nodinite with description "Project Phoenix team - ends June 2026"
  3. Assign to Role "Project Phoenix Logs"
  4. When project ends, IT deletes AD group (or removes Nodinite configuration)

Benefits: Clean separation of project access, easy to grant and revoke for entire team at once.

Next Steps

Ready to add Windows AD Groups to Nodinite?