Reviewer Assignment Methods

When no reviewers can be assigned for a certification result due to a rule, alternative selection methods are tried in the configured order.

When creating a certification or choosing to Reassign Reviewers, Veza operators can assign all results to a one or more users, or auto-assign individual results. Certifications can be assigned to any of the following:

• Reviewers: Certification results are all assigned to the listed users. Results can have more than one reviewer at a time.

• User Managers / Resource Managers: Individual results are assigned to reviewers based on IdP metadata

• Fallback Reviewers (list of users): Assigned as reviewers for results where a Manager or Owner cannot be found, or if a rule would prevent assignment.

Veza will use the following logic when assigning reviewers :

• Reviewers are all candidates for assignment. User and Resource Managers are also candidates.

• When no candidates are available or allowed for assignment, Fallback Reviewers become candidates.

• If a self-review prevention or deny list rule prevents a candidate's assignment, the other specified Reviewers are assigned.

• If all candidates are not allowed, Veza will try to assign alternate reviewers based on the selection method.

Selection methods

When a valid candidate does not exist, Veza can assign that reviewer's manager, fallback reviewers, the workflow creator, or a Veza local user with the administrator role.

The Veza Customer Success team can change this global setting to enable of the following selection_methods. If the first selection method can find at least one allowed alternate reviewer, the user is assigned. Otherwise, the next selection method is attempted. Possible selection methods are:

• REVIEWERS_MANAGER | Assign the manager of the prevented candidate.

• CERTIFICATION_ALTERNATE_REVIEWERS | Assign to the first valid Fallback Reviewer, for certifications created using auto-assignment.

• WORKFLOW_CREATOR | Assign to the workflow creator.

• ADMIN | Assign to an arbitrary local Veza admin user.

For example with the selection methods:

"value": {
        "selection_methods": [
            "REVIEWERS_MANAGER",
            "CERTIFICATION_ALTERNATE_REVIEWERS"
        ]
    }

Veza will not assign the workflow creator or a system administrator as a fallback behavior. Instead, Veza will:

1. Assign the denied candidate's User Manager (if allowed).

2. Otherwise, assign the first valid Fallback reviewer.

3. Assign no reviewers for results where a valid manager or fallback reviewer does not exist.