Reassign approval tasks

With the Named Approver feature, you can reassign approval tasks to specific team members for better control over the approval process. Route owners can delegate tasks from roles to individual named approvers, while named approvers can reassign their tasks to other qualified team members.

Use cases for reassignment

Different roles have specific reassignment capabilities that support various workflow scenarios. These use cases show how each role can manage approval tasks to ensure efficient approval processes.

As a route owner or domain administrator, you can assign an approval task from a role to a specific role member. This ensures that only the assigned named approver can complete the approval task by approving, rejecting, or reassigning it.

As a named approver, you can assign your approval tasks either to another user with the approval role or back to the role itself. This lets you delegate your approval to another team member when needed. Additionally, you can view your approval tasks in the approval queue. This gives you visibility into all approval tasks assigned specifically to you.

As a domain administrator, you can assign approval tasks from a named approver back to the role. This allows any user with the role to approve the record when the original assignee isn't available.

How reassignment works

When you route a record for approval, Vera creates an approval route that can be reassigned based on your role and permissions:

  1. The route owner routes a record for approval from the source system.

  2. Vera creates an approval route and displays it in the source system.

  3. Vera sends Pending Approver email to all approvers who opted in to notifications.

  4. The route owner can go to the Vera record via the links in the approval route.

  5. The route owner can reassign approval tasks from the role to a role member.

  6. Vera sends Cancelled Approval email to all approvers who opted in to notifications.

  7. Vera sends Pending Approver email to the named approver who opted in to notifications.

Once assigned to a named approver:

  • Approval tasks assigned to named approver appear only in their approval queue.

  • Only the named approver can approve or reject approval tasks assigned to them.

Who can reassign approval tasks

The ability to reassign approval tasks depends on your role and how the task is currently assigned:

Approval Task Assigned To Route Owner Domain Administrator Named Approver
Assigned to a role Can reassign Can reassign Can't reassign
Assigned to individual approver Can reassign Can reassign Can reassign

Route owner account requirements

A route owner's ability to reassign tasks depend on their Vera account status at the time of routing:

  • If the route owner doesn't have a Vera account when they route for approval, only the domain administrator can reassign approval tasks from roles to individual users.

  • If a route owner is added to Vera after they route for approval, their account won't be associated with existing routes and they still can't reassign those approval tasks.

Jira Cloud limitations

Due to a limitation in Jira Cloud, Vera can't map Jira Cloud users to Vera user accounts. Jira Cloud only exposes a user's Public Name and GUID from their Atlassian account. This prevents the reliable linking of a route owner to their corresponding Vera user.

As a workaround, users with the Domain Administrator role can manually reassign approval tasks to the appropriate Vera users.

What's next

After setting up task reassignment, create and approve test cases to see the approval workflow in action.