Delegated Administration and Director
May 28, 2016
Delegated Administration uses three concepts: administrators, roles, and scopes. Permissions are based on an administrator’s role and the scope of this role. For example, an administrator might be assigned a Help Desk administrator role where the scope involves responsibility for end-users at one site only.
For information about creating delegated administrators, see the main Delegated Administration document.
Administrative permissions determine the Director interface presented to administrators and the tasks they can perform. Permissions determine:
- The views the administrator can access, collectively referred to as a view.
- The desktops, machines, and sessions that the administrator can view and interact with.
- The commands the administrator can perform, such as shadowing a user’s session or enabling maintenance mode.
The built-in roles and permissions also determine how administrators use Director:
|Administrator Role||Permissions in Director|
|Full Administrator||Full access to all views and can perform all commands, including shadowing a user's session, enabling maintenance mode, and exporting trends data.|
|Delivery Group Administrator||Full access to all views and can perform all commands, including shadowing a user's session, enabling maintenance mode, and exporting trends data.|
|Read Only Administrator||Can access all views and see all objects in specified scopes as well as global information. Can download reports from HDX channels and can export Trends data using the Export option in the Trends view.
Cannot perform any other commands or change anything in the views.
|Help Desk Administrator||Can access only the Help Desk and User Details views and can view only objects that the administrator is delegated to manage. Can shadow a user's session and perform commands for that user. Can perform maintenance mode operations. Can use power control options for Desktop OS Machines.
Cannot access the Dashboard, Trends, or Filters views. Cannot use power control options for Server OS machines.
|Machine Catalog Administrator||No access. This administrator is not supported for Director and cannot view data. This user can access the Machine Details page (Machine-based search).|
|Host Administrator||No access. This administrator is not supported for Director and cannot view data.|
To configure custom roles for Director administrators
In Studio, you can also configure Director-specific, custom roles to more closely match the requirements of your organization and delegate permissions more flexibly. For example, you can restrict the built-in Help Desk administrator role so that this administrator cannot log off sessions.
If you create a custom role with Director permissions, you must also give that role other generic permissions:
- Delivery Controller permission to log on to Director.
- Permissions to Delivery Groups to view the data related to those Delivery Groups in Director.
Alternatively, you can create a custom role by copying an existing role and include additional permissions for different views. For example, you can copy the Help Desk role and include permissions to view the Dashboard or Filters pages.
Select the Director permissions for the custom role, which include:
- Perform Kill Application running on a machine
- Perform Kill Process running on a machine
- Perform Remote Assistance on a machine
- Perform Reset vDisk operation
- Reset user profiles
- View Client Details page
- View Dashboard page
- View Filters page
- View Machine Details page
- View Trends page
- View User Details page
In this example, Shadowing (Perform Remote Assistance on a machine) is turned off.
In addition, from the list of permissions for other components, consider these permissions:
- From Delivery Groups:
- Enable/disable maintenance mode of a machine using Delivery Group membership
- Perform power operations on Windows Desktop machines using Delivery Group membership
- Perform session management on machines using Delivery Group membership