How governance works for Apps
- One live bundle per App, one snapshot per version. You link the App to a governance bundle once. The bundle holds the policies, the evidence they ask for, and the approvals. When you publish a new version, the live bundle moves to it and the previous version keeps a read-only snapshot, so governance carries forward without re-collecting evidence. See When you publish a new version.
- Gates decide whether a version runs. A policy’s gates block deployment until the approvals are in. Domino checks them on every deploy and restart, against the deployment parameters, so an approval can depend on where and how the version runs. See How gates decide.
- Policies can attach at any time. You can govern an App at any point in its life. Policies your administrators enforce attach automatically. See Required policies.
Govern the App
The Synthetic Transaction Review App puts a compliance decision in front of reviewers, so a model risk policy is likely to cover it. Attach the policy to the version you published before you deploy it. You need a published version and policies defined by a GovernanceAdmin.1
Attach a policy
On the App’s page, select Add to Bundle and link the App to a new or existing bundle. The App is now governed, and every later version reuses the bundle.
2
Collect evidence
Evidence for Apps usually covers security and data privacy. For the transaction review App, that might be a scripted check that only the compliance team can read the
AML Dataset, plus a user acceptance testing (UAT) sign-off from a reviewer.- Scripted checks: Automated tests that verify dependencies, check for vulnerabilities, or validate data access permissions.
- Manual evidence: Screenshots, UAT sign-offs, or Data Source documentation.
3
Obtain approvals
Approvers review the evidence in the bundle and grant the approvals the policy requires. This is the same flow as for any other governed asset.
4
Deploy the version
Deploy the version. Domino checks the gates first, and blocks the deploy and lists any missing approval until it’s granted.
How gates decide
Domino evaluates a gate each time someone deploys or restarts a governed version.- Gates match on deployment parameters such as Hardware Tier or Data Plane. A gate can allow CPU tiers and require a
Validation sign offapproval before the version runs on a GPU tier. - On restart, Domino returns an error if a previously approved configuration no longer meets the policy.
- Preview instances of Draft Apps are never gated.
When you publish a new version
Each governed version maps to one bundle. Governance carries forward to the new version without re-collecting evidence. On publish, Domino snapshots the previous version’s bundle into a read-only bundle attached to the previous version. The snapshot copies evidence, attachments, and approvals, but not findings or comments. The read-write bundle moves to the new version. Approvals, findings, and attachments on earlier bundles stay editable. To see how evidence changed between versions, open the App and go to Governance > Changes. The tab compares evidence for the same policy across versions and shows what was added, removed, or modified. If a policy was upgraded between versions, the tab still pairs the bundles on that policy. If a policy exists in only one version, every question in it appears as added or removed.Required policies
Governance admins can mark policies as enforced. Domino attaches enforced policies to every App bundle in the deployment, always at their latest version. Practitioners can’t remove them. Governance, System, and Cloud admins can.
If an admin removed an enforced policy from an earlier version’s bundle, it attaches again on the next version as long as it’s still enforced. See Enforce required policies.
Related
- Work with bundles: Package assets for review.
- Define policies: Build the policies that govern Apps.
- Deploy to production: Start the approved version.