Remedy Deployment Application roles and permissions

In Remedy Deployment Application, you can define role-based access to enable users to perform different operations based on their need. This access enables users who are not administrators to perform operations such as creating, viewing, copying, and deploying packages.

Roles and permissions for using Remedy Deployment Application

Remedy Deployment Application permission model defines the roles and permissions for users and enables secured access and controlled functionality. The following diagram depicts the permission model:

Refer to the table for the details of roles and permission: 

Considerations

• Only an Administrator or a Package Creator with AR System Administrator permission can create a package with , , and  objects.
• Only an Administrator can create and deploy a binary payload.
• With the appropriate application permission, a Package Creator can create a package using an Application Object. For example, to create a package using the Incident template, a Package Creator must have Incident Configuration permissions. For more information, see Promoting configurations and customizations across environments.
• A Package Creator, without AR System Administration permission, can create a package using ITSM objects such as SRM, Add Data, and Application Objects.
• A Package Deployer and Package Creator can edit only the Notification Email field on the Application Configuration form.

Refer to the following table to understand details about roles:

Assigning roles

You can assign the permissions by using the User form. Ensure that you have groups and roles created before you assign the permissions.  For more information about creating and mapping roles, see  Creating-and-mapping-roles.

For information about creating permissions on the People form, see Adding-People-by-using-a-template.

Where to go from here

Defining-and-deploying-data-and-object-packages