Enforce named approvers
By default, approval tasks in Vera can be assigned to a group or a specific individual. If your process requires that every approval task goes to a specific person (a Named Approver), you can enforce this in the Approval Policy. You can enforce it globally, per route template, or per approval task level.
The Require Assignment property controls this behavior at three levels. Each level inherits from its parent unless you explicitly override it:
-
Approval Policy (global): affects all route templates and their levels unless overridden below.
-
Route Template (per route): affects all levels in that route unless overridden at the level itself.
-
Approval Task Level (per step): most granular control. Use this when a specific step must be assigned to an individual, for example a Quality sign-off.
Before you start
The Require Assignment property accepts three values:
|
Value |
Behavior |
|---|---|
|
null |
Inherit from the parent (policy > route template > task). This is the default. |
|
false |
Named Approver isn't required. Group assignment is acceptable. |
|
true |
A Named Approver must be selected before the approval task can be approved or rejected. |
Use inheritance (null) at lower levels to centralize control. Override only when a route or step needs stricter or looser enforcement. A lower-level setting always overrides its parent.
Here's a quick decision matrix to help you choose:
-
Enforce everywhere: set Require Assignment to true at the Approval Policy level.
-
Enforce for one route: leave the policy at null and set Require Assignment to true on that Route Template.
-
Enforce for a single step: set Require Assignment to true on just that Level.
-
Mix and match: use null to inherit, true to enforce, and false to allow group-based assignment.
Configure the Approval Policy
To enforce Named Approvers, access the administration area, go to Policy Management, and download the Approval Policy file you want to modify. Open it in a text editor and set Require Assignment at the level you need.
The following examples show different enforcement scenarios. Each one highlights where Require Assignment is set and what it does.
Keeps assigning a Named Approver optional by inheriting at every level (no enforcement):
{
"Name": "Vera AP",
"Approval Policy": {
"Version": "1",
"Approval Groups": [
"Business",
"Quality",
"Technical"
],
"Require Assignment": null,
"Route Templates": [
{
"Name": "GxP Approval",
"Rank": "1",
"Record Types": [
"qTest Requirement"
],
"Levels": [
{
"Name": "Level 1",
"Approvers": [
"Technical",
"Business"
],
"Require Assignment": null
},
{
"Name": "Level 2",
"Approvers": [
"Quality"
],
"Require Assignment": null
}
],
"Constraints": [],
"Prevent Author Approval": "true",
"Signatures Required": "true",
"Allow Multi Task Approval": null,
"Require Assignment": null
}
]
}
}All routes and levels must assign a Named Approver unless a lower level explicitly sets false:
{
"Name": "Vera AP",
"Approval Policy": {
"Version": "1",
"Approval Groups": [
"Business",
"Quality",
"Technical"
],
"Require Assignment": true,
"Route Templates": [
{
"Name": "GxP Approval",
"Rank": "1",
"Record Types": [
"qTest Requirement"
],
"Levels": [
{
"Name": "Level 1",
"Approvers": [
"Technical",
"Business"
],
"Require Assignment": null
},
{
"Name": "Level 2",
"Approvers": [
"Quality"
],
"Require Assignment": null
}
],
"Constraints": [],
"Prevent Author Approval": "true",
"Signatures Required": "true",
"Allow Multi Task Approval": null,
"Require Assignment": null
}
]
}
}Only this route requires Named Approvers. The policy stays at null:
{
"Name": "Vera AP",
"Approval Policy": {
"Version": "1",
"Approval Groups": [
"Business",
"Quality",
"Technical"
],
"Require Assignment": null,
"Route Templates": [
{
"Name": "GxP Approval",
"Rank": "1",
"Record Types": [
"qTest Requirement"
],
"Levels": [
{
"Name": "Level 1",
"Approvers": [
"Technical",
"Business"
],
"Require Assignment": null
},
{
"Name": "Level 2",
"Approvers": [
"Quality"
],
"Require Assignment": null
}
],
"Constraints": [],
"Prevent Author Approval": "true",
"Signatures Required": "true",
"Allow Multi Task Approval": null,
"Require Assignment": true
}
]
}
}Only Level 2 requires a Named Approver. All other levels remain optional:
{
"Name": "Vera AP",
"Approval Policy": {
"Version": "1",
"Approval Groups": [
"Business",
"Quality",
"Technical"
],
"Require Assignment": null,
"Route Templates": [
{
"Name": "GxP Approval",
"Rank": "1",
"Record Types": [
"qTest Requirement"
],
"Levels": [
{
"Name": "Level 1",
"Approvers": [
"Technical",
"Business"
],
"Require Assignment": null
},
{
"Name": "Level 2",
"Approvers": [
"Quality"
],
"Require Assignment": true
}
],
"Constraints": [],
"Prevent Author Approval": "true",
"Signatures Required": "true",
"Allow Multi Task Approval": null,
"Require Assignment": null
}
]
}
}The policy enforces Named Approvers globally, but Level 1 is explicitly set to false so it accepts group-based assignment:
{
"Name": "Vera AP",
"Approval Policy": {
"Version": "1",
"Approval Groups": [
"Business",
"Quality",
"Technical"
],
"Require Assignment": true,
"Route Templates": [
{
"Name": "GxP Approval",
"Rank": "1",
"Record Types": [
"qTest Requirement"
],
"Levels": [
{
"Name": "Level 1",
"Approvers": [
"Technical",
"Business"
],
"Require Assignment": false
},
{
"Name": "Level 2",
"Approvers": [
"Quality"
],
"Require Assignment": null
}
],
"Constraints": [],
"Prevent Author Approval": "true",
"Signatures Required": "true",
"Allow Multi Task Approval": null,
"Require Assignment": null
}
]
}
}After you've made your changes, save the file and upload the policy as a new policy or a policy revision.
Operational guidance
Route Owners and Domain Administrators can assign Named Approvers from the Approval Task or Record pages. When a task is assigned to a Named Approver, it appears only in that individual's approval queue. Domain Administrators can view all tasks and delegate on the assignee's behalf, for example when someone is out of office.
Only the assigned individual receives pending and cancel notifications. If you want to reduce noise, disable group notifications in your SMTP settings.
When a record is re-routed, Vera automatically assigns tasks to the same individual who previously approved or rejected, so you maintain continuity.