Asset Management permissions
To access the various modules in Remedy Asset Management, you need the following permissions and authorizations:
- Asset Management permissions
- Contract Management permission model
- Cost module permission model
Asset Management permissions
This table describes the Asset Management permissions for following user roles.
Important
If you select the Application user license type as None, you get only Asset Inventory permissions. For information about these permissions, see Asset Inventory permissions .
Permissions | Description | Application user license type |
---|---|---|
Asset Admin | Users with Asset Admin permissions can perform all of the Asset Inventory functions as well as the following Asset Management functions:
Important: This permission does not grant access to purchasing or receiving functions. A person with Asset Admin permissions does not need Asset User and Asset Viewer permissions. Best practice: We recommend that you grant these permissions only to users playing a Configuration Administrator role. Users with Asset Admin permission have full access to contracts and SWLM features, which means they do not need any other Contract permissions unless they must create new Contract Types (this ability is given with Contract Admin permissions) or configure certain aspects of SWLM (this ability is given with Contract Config permissions). |
|
Asset User | Users with Asset User permissions can perform all of the Asset Inventory functions as well as the following Asset Management functions:
Important: To modify the CI, the user with asset user permission must be a member of the support group that is associated with the CI by the Supported by role. Asset Admin permission is required to access inventory management and bulk update features. The Asset User permission does not grant access to the following functions:
A user with Asset User permissions cannot create a CI to CI relationship. The Asset User permissions do not have equivalent permissions to the Contract User permissions group. If a user requires the ability to either modify license certificates or manage License jobs as part of SWLM, then they must also be given Contract User permissions. Best practice: We recommend that you grant these permissions to users who are directly supporting specific CIs and who must update CI attributes. The users with the Asset user permission can also update relationships for the following Request Type:
|
|
Asset Viewer | Users with Asset Viewer permissions have access to all of the Asset Inventory functions as well as the following Asset Management functions:
Important: The Asset Viewer permission does not grant access to:
Asset Viewer permissions are automatically granted when assigning any of the following permissions:
Best practice: We recommend that you grant these permissions to all Support personnel (that is, users who do not already have the Asset Admin or Asset User permissions). Having access to CI information is vital for most ITIL processes. |
|
Asset Config | Users with Asset Config permission have access to all of the Asset Inventory functions as well as the following Asset Management functions:
Important: Users with Asset Config permission do not need Contract Config permissions. Best practice: We recommend that you grant these permissions only to users who administer the Asset Inventory and Asset Management system (that is, to an user who acts as an Application Administrator). |
|
Purchasing User | Users with Purchasing User permissions can access the following functions within the BMC Asset Management application:
Best practice: We recommend that you limit the use of these permissions to users who perform the following roles in the Asset Management Purchasing feature:
|
|
Receiving User | Users with Receiving User permissions can access the Receiving console to receive CIs from the Purchasing system. Best practice: We recommend that you grant these permissions only to users who use the Asset Management Purchasing feature, for example, Purchasing Agents because, they grant access only to the receiving functions. |
|
Contract Admin | Users with Contract Admin permissions can perform the following functions:
Important: A user with the Asset Admin permission can do everything that a user with Contract Admin permission with the exception of creating new Contract Types. Best practice: We recommend that you grant these permissions to users who need full access to the Contract Management features, but who don't need the full Asset Management access given by the Asset Admin permissions group. |
|
Contract User | Users with Contract User permissions can perform the following functions:
Best practice: We recommend that you grant these permissions to users who need controlled access to create and modify contracts, but who do not require access to modify CI information. If a user is also needs to modify CI information, you should also give that user Asset User permissions. |
|
Contract Viewer | Users with Contract Viewer permission can view all contracts from the Contract console. Best practice: We recommend that you grant these permissions to users who require view access to contracts. |
|
Contract Config | Typically, an Application Administrator requires this set of permissions. Users with Contract Config permission can perform the following functions:
Important: This permission does not grant access to the SAM console. If a user has Asset Config permission they do not need Contract Config permissions. This is because, the Asset Config permissions group can configure the same SWLM features that the Contract Config permissions can configure. Best practice: We recommend that you grant these permissions to users who must only configure Software Licence Management (SWLM) features. |
|
Contract Management permission model
Contract Management permission groups are defined as computed groups in the Group form. Each Contract permission group is mapped to an Asset permission group to support the deployable application functionality. To remove specific users from the computed group, remove the BMC Asset Management groups for each Contract permission group to make each Contract permission group stand alone.
Cost module permission model
The cost module uses the following permissions:
- Cost Viewer — Can only view cost data
- Cost User — Can add costs
- Cost Manager — Can update and manage the charge back process
Comments
Log in or register to comment.