# Working with Batch Release Roles

Batch Release allows administrators and quality managers to assign users to Batch Release roles. With Batch Release roles, you can determine who can participate in a batch disposition role and what permissions they will have. This helps prioritize workloads across teams. If the availability of an assigned member changes, you can reassign their role to another eligible user.

The following standard roles are available; however, Admins can configure additional roles depending on organizational needs:

  * **Disposition Owner**: The user assigned to this role is responsible for recommending a decision for _Batch Dispositions_. This role is tied to the `owner__v` field on the `batch_disposition__v` object.
  * **Check Owner**: The user assigned to this role is responsible for completing a _Batch Disposition Check_. This role is tied to the `owner__v` field on the `batch_disposition_check__v` object.

If an Admin has configured Batch Release roles in your Vault, when you create a new _Batch Disposition_ record, you can assign users to these roles. For example, you might assign a user as _Approver_ on a _Batch Disposition_ record. Vault also cascades disposition role assignments to their children _Batch Disposition Checks_.

## Assigning Users to Roles

If an Admin has configured Batch Release roles, you can assign users to roles on _Batch Disposition_ records that are _Open_. For example, you may create a new _Batch Disposition_ record and then assign users to the _Owner_ and _Approver_ roles. When you assign a user to a role, Vault updates that user's assigned application role for that record, which can be viewed in the record's [sharing settings](/en/lr/61279/).

Vault may automatically assign roles upon the creation of a _Batch Disposition_ record. You can add, remove, or change role assignments on a _Batch Disposition_ record, which are constrained by [role eligibility][1].

Vault maps these roles to application roles to determine the user's record permissions. Role membership also grants users roles on related records in the process. For example, when you assign roles to a _Batch Disposition_ record, Vault grants those users the same application role for _Batch Disposition Check_ records.

To assign users to roles:

  1. Navigate to a _Batch Disposition_ record via a custom tab or **Business Admin**.
  2. Click **Edit**.
  3. Assign users to their designated roles, such as **Owner**. You can only assign one (1) user to each role. The list of users is restricted to those who are eligible as defined in your Vault's configuration.
  4. Click **Save**.

### Eligible Roles {#eligible-roles}

Admins can configure each role to constrain which users are available for selection, ensuring you assign only those eligible to perform the job using [custom or matching sharing rules](/en/lr/33946/).

### Reassigning Roles

You can reassign users to a role while the _Batch Disposition_ or _Batch Disposition Check_ is still in the _Open_ lifecycle state. If you wish to reassign a role while the object record is in another lifecycle state, you must reopen the _Batch Disposition_ record and cancel any active workflows.

## Reporting on Roles

Utilizing list pages or Vault's report functionality can facilitate workload balancing for Batch Release roles. To do so, create a [list page](/en/lr/44069/#list_page) with the roles or a report with an _Application Role_ [report type](/en/lr/3606/#report-type).

## Related Permissions

To view Batch Release role assignments, a user requires _Read_ permission to the _Batch Disposition_ (`batch_disposition__v`) and _Batch Disposition Check_ (`batch_disposition_check__v`) objects. To add, modify, or remove Batch Release role assignments, a user requires _Edit_ permission for the same objects.

 [1]: #eligible-roles