Hide Active Directory Objects from Users
By default, after you install Adaxes, all users can view all objects in Active Directory. However, some users in your company need to view only specific AD objects. To allow users to view only the objects they need, it is necessary to adjust their permissions via Security Roles.
The permission to view all objects in Active Directory is granted by the built-in Security Role called Domain User.
If you want to explicitly specify what objects users are allowed to access in Active Directory, first you need to remove the default assignment of the Domain User role:
- Select the Domain User role in the Console Tree.
- Right-click the default assignment item (Authenticated Users over All Objects).
-
In the context menu, click Delete.
-
Click Save.
After the assignment is removed, all users are not allowed to view any objects in Active Directory. The only object they will be able to view, is their own user account (this permission is granted by the built-in User Self-Service role).
To allow users to view and manage objects in Active Directory, you need to assign them to corresponding Security Roles. Below you will find instructions on how to address typical requirements.
To do this, assign the Domain User role to Authenticated Users over the Organizational Unit you need.

Step by step
-
Select the Domain User role in the Console Tree.
-
In the Result Pane (located to the right), click Add Assignment.
-
Select Authenticated Users and click OK.
-
Select the Organizational Unit you need, click Add, and select Child objects of this Organizational Unit.
If you want to allow users to also view the Organizational Unit itself, select the This Organizational-Unit object option. - Click OK two times.
-
Click Save.
To do this, assign the Help Desk role (or any other role) to your Help Desk group over the children of an Organizational Unit and members of a group.

Step by step
-
Select the Help Desk role in the Console Tree.
-
In the Result Pane (located to the right), click Add Assignment.
-
Select the group you need and click OK.
-
Select the Organizational Unit you need, click Add, and select Child objects of this Organizational Unit.
- Click OK.
-
Select the group, members of which you want to allow to view and manage, click Add,
and select Members of this Group.
- Click OK two times.
-
Click Save.
To do this, assign managers of the Sales department to a Security Role over members of a Business Unit that includes all users whose Department property contains 'Sales'.

Step by step
-
Create a Business Unit that will contain all users from the Sales department.
See View & manage AD objects collectively to learn how to create a Business Unit.
- Select the Security Role you need in the Console Tree.
-
In the Result Pane (located to the right), click Add Assignment.
-
Select the group you need and click OK.
-
Select the Business Units item in the Look in drop-down list.
-
Select the Business Unit you need and click Add.
-
Select the Members of this Business Unit and This Business Unit object options.
- Click OK two times.
-
Click Save.
To do this, you need to assign your Administrators group to the Super Manager role over All Objects.

Step by step
-
Select the Super Manager role in the Console Tree.
-
In the Result Pane (located to the right), click Add Assignment.
-
Select the group you need and click OK.
-
Select All Objects and click Add.
- Click OK two times.
-
Click Save.
Blind User Role
Adaxes includes a built-in Security Role called Blind User that can also be used to hide Active Directory objects.
The Blind User role contains only one permission Deny Read all object types and is very simple to use. To hide an AD object from a user, you just need to assign the Blind User role to this user and include the object you want to hide to the assignment scope. In this way, you can hide objects located in an OU, members of AD groups, objects that belong to a Business Unit, specific AD objects, etc.
For example, to hide an Organizational Unit from users, you just need to assign the Blind User role to the users and include the OU and its children to the assignment scope.
