Information Technology Reference
In-Depth Information
Orchestrator roles
Orchestrator has two different roles, the runbook author, and the runbook operator.
■
Runbook authors
User accounts that are members of the Orchestrator Users group.
You specify which group functions as the Orchestrator Users group during deploy-
ment. Members of this group have full administrator access to the Orchestrator
deployment.
■
Runbook operators
Runbook operators have permissions granted by runbook
authors using the Orchestrator Runbook Designer. They can access the Orchestration
console, can view and invoke runbooks to which they have been given permission.
MORE INFO ORCHESTRATOR ROLES
You can learn more about Orchestrator security groups at
http://technet.microsoft.com/
Service Manager roles
Service Manager includes 13 different built-in user roles that allow administrators to create
additional user roles based on the built-in roles. These roles are available in the User Roles
node of the Administration workspace, as shown in Figure 2-31, and have the following prop-
erties:
■
Activity Implementers
Can edit manual activities in their queue scope. Have read-
only access to other work items in their queue scope. Have read-only access to queue
items in their group scope.
■
Administrators
Full access to all elements of a Service Manager deployment.
■
Advanced Operators
Are able to manage work items and configuration items in
their queue scope. Can manage announcements in the Self-Service Portal.
■
Change Initiators
Can create change requests and activities for configuration items
in their group scope. Have read access to work items in their queue scope.
■
Service Request Analysts
Can create and edit service requests and activity work
items in their queue scope. Have read access to work items in their queue scope. Have
read access to configuration items in their queue scope.
■
End Users
Can create incidents, request software, view announcements and knowl-
edge base articles in the Self-Service Portal.
■
Read-Only Operators
Have read-only access to work items in their queue scope.
Have read-only access to configuration items in their group scope.
■
Release Managers
Can manage release records and activity work items in their
queue scope. Have read-only access to other items in their queue scope. Have read-
only access to items in their group scope.