Each user can have a different role for each business unit. By default, the available roles provide access to different types of functionality in CA Service Catalog. However, the following factors greatly influence the functions that users can perform, regardless of their role:
Note: For details about the Access Control configuration settings, see the Implementation Guide.
Request-related functionality is available when CA Service Catalog is installed. Subscription and invoice-related functionality is available when Accounting Component is installed
Is the user role for requesting services without subscriptions. These users can also manage their own requests, such as approve, reject, fulfill, and other actions to handle requests pending action.
Most users in the organization use this role only.
This role is predefined as the default role for new users. However, administrators can optionally change the default role for new users from the catalog user to another role.
This role is most suitable when you are not using subscriptions or billing in your implementation.
Is end user for all functions available through the catalog. This user includes all the same access rights as the catalog user. In addition, the end user can subscribe to services, view invoices, view and add news messages, documents, and reports.
Is the administrator role for managing requests, such as viewing and handling all requests in the business unit and any applicable subbusiness units. Request managers handle both their own requests pending action and the requests pending action of other users. Request managers can search all requests in the Catalog system, while catalog users can search only their own requests.
Creates, defines, and manages services (not requests) for a specific tenant or business unit. This user also has administrative access to configure reports, dashboards, documents, and message alerts.
This role is most suitable when you want a user to create and maintain services. This user cannot request or subscribe to services.
This user can also handle requests pending actions, for example, by approving and rejecting requests.
Creates, defines, and manages services for a specific tenant or business unit.
In addition, this user also has the same access rights as the request manager role.
This user can also request services but cannot subscribe to them.
Is the "root" user in a specific super tenant (super business unit). A super business unit is a business unit that contains one or more child business units. This administrator has almost complete access to the super business unit and all its sub business units. For example, anywhere in the super business unit, this administrator can create business units, create new users, and assign roles.
Is the "root" (highest level) user in the Service Provider (highest level) business unit. This user has complete system access to all business units. For example, this user can specify default settings that apply to all users by logging in to the root business and accessing the Administration, Configuration, User Default tab.
Important! Assign this role carefully!
This role is available only for the Service Provider business unit, the default business unit created during installation.
Only this administrator has access to data mediation, system configuration, events, rules, and actions.
By default, at installation time, the Catalog system creates a user ID named spadmin with this role.
Service Delivery administrators can specify a default role for all users.
|
Copyright © 2013 CA.
All rights reserved.
|
|