[juanmleng]

What and why?

Documents a new way to risk tier a record: a risk tier assessment added to a User Action step in a record workflow. The step's assignee answers the record's risk tier questions on the step, and submitting it publishes the assessment.

• Workflow step types: a new "Risk tier assessments" subsection under User Action (adding it, what users see, what submitting does, permissions), and the Approval step's Fields to Review now mentions the assessment.
• Set up risk tiering workflows: a new section comparing this with risk tiering workflows, linked both ways.

Written from the implementation in ValidMind/backend#3970 and ValidMind/frontend#3135.

Preview

• Workflow step types › Risk tier assessments
• Workflow step types › Approval › Fields to Review
• Set up risk tiering workflows › Risk tier a record from its own workflow

How to test

Rendered each affected page locally, one at a time:

skills/validmind-docs-coverage/scripts/render-pages.sh guide/workflows/workflow-step-types.qmd guide/risk-tiering/set-up-risk-tiering-workflows.qmd training/administrator-fundamentals/using-validmind-for-risk-management.qmd

All three render; the only warning (unresolved validmind/validmind.qmd) also appears without this change. The training module uses the step types' short slide summary, which is unchanged.

What needs special review?

• The implementation PRs are still drafts. Do not merge this until they ship; the behaviour described may change in review.
• Approvers see the record's current published assessment, not necessarily the version the run published. This is stated as a limitation.

Dependencies, breaking changes, and deployment notes

Depends on ValidMind/backend#3970 and ValidMind/frontend#3135 shipping.

Release notes

Workflow User Action steps on record workflows can now include a risk tier assessment: the assignee answers the record's risk tier questions on the step, and submitting it publishes the assessment. Learn more ...

Checklist

• What and why
• Screenshots or videos (Frontend)
• How to test
• What needs special review
• Dependencies, breaking changes, and deployment notes
• Labels applied
• PR linked to Shortcut
• Unit tests added (Backend)
• Tested locally
• Documentation updated (if required)
• Environment variable additions/changes documented (if required)

🤖 Generated with Claude Code

[github-actions]

Validate docs site

✓ INFO: A live preview of the docs site is available — Open the preview

[github-actions]

Lighthouse check results

✓ INFO: Average accessibility score is 0.93 (required: ≥0.9) — View the workflow run

Audit mode: changed pages (1 URL(s))

Show Lighthouse scores

Commit SHA: 483a4ee

For a thorough audit, run the Lighthouse check workflow manually (Actions → Lighthouse check → Run workflow) with depth 0–2, or add the lighthouse:full label for depth 2 on the next validate run.

Page	Accessibility	Performance	Best Practices	SEO
/guide/risk-tiering/set-up-risk-tiering-workflows.html	0.93	0.78	1.00	0.82
/guide/risk-tiering/set-up-risk-tiering-workflows.html	0.93	0.78	1.00	0.82
/guide/risk-tiering/set-up-risk-tiering-workflows.html	0.93	0.79	1.00	0.82