Open your assignment under Assignments in the Govern section. The ID sits at the top of its detail page with a control to copy it. That ID is what connects the assignment to your pipeline.

In your pipeline, or locally to test, run checks run with the assignment’s ID:

Be sure to:

• Replace your_assignment_id with the ID you copied in step 1.

The server resolves the ID to the set of checks the assignment currently maps, and those are the checks that run. The command in your pipeline never names a check, so you change what it enforces by editing the assignment in the web application, and the next run picks that up.

Note: --assignment-id takes precedence over --checks-settings-file. If you pass both, the local file is ignored and never read, and the run tells you so.

To include database-scoped checks, add --checks-scope=changelog,database. The checks run command reference lists every parameter the command takes.

The output names each check that fired, the changeset or database object that triggered it, the severity, and the exit code. A changelog run then lists every changeset it validated, and a database run counts the objects it examined by type. Either way that is the quickest way to confirm a check reached what you expected it to.

Each check’s severity maps to an exit code, and when multiple checks fire, Liquibase returns the highest one. That exit code is what stops a pipeline. Every reported run also appears in the Policy Checks dashboard under Monitor.