Approvals

Approvals are checkpoints where designated stakeholders review evidence and sign off before a bundle can advance. They ensure that models, apps, and other assets meet organizational standards before progressing through the governance lifecycle. You need the GovernanceAdmin role to define approvals in policies. Roles and security has details on role assignment.

Each approval includes:

  • A name

  • A list of approvers (users or organizations)

  • Optional evidence requirements which must be satisfied before approval can be granted

Define approvals in a policy

Governance administrators define approvals within a stage using YAML.

Example: Define an approval with evidence

In this example, the stage includes an approval named Stage 4: validation sign off, which includes a checklist prompt for the approver:

- name: 'Stage 4: validation sign off'
  approvers:
    - model-gov-org
  evidence:
    id: Local.validation-approval-body
    name: Sign-off
    description: The checklist for approvals
    definition:
      - artifactType: input
        details:
          label: "Have you read the model validation reports?"
          type: radio
          options:
            - Yes
            - No

Conditional approval

Conditional approval lets practitioners proceed to the next stage while they track and address outstanding findings.

A reviewer can approve a stage conditionally by attaching findings to the approval. These findings form a remediation plan and create a formal feedback loop from the reviewer to the modeler.

If you resolve all findings by their due dates, the approval remains valid. If you don’t resolve the findings on time, Domino automatically revokes the approval.

Next steps