docs: document org-wide record activity views and filters [sc-17354]

[emmavdh]

What and why?

Documents organization-wide Record Activity vs per-record Activity for SC-17354 / SC-16807 (epic 15038), and updates Settings Activity for the same filter rollout.

Implementation: frontend#2734, backend#3380.

Before: View record activity only described opening Activity from a single inventory record and its Event Category / Filter by Value popover. View settings activity still described an Event Type-only filter and omitted several shipped audit scopes.

After:

• Intro and overview clarify organization-wide Activity → Record Activity vs a record's Activity page
• View record activity uses tabs for both entry points
• Filter record activity documents org-wide Activity Filter + Record/Artifact Filter (including downstream artifact behavior) separately from per-record filters
• View settings activity documents the query-builder filters (Category, Action, Actor, Target Type) and expands what is tracked (risk tiering, record stages/custom fields, finding statuses, workflow states, global charters)
• Tracking landing blurb and chatbot product map (/activity) updated via keyword mapping so regenerate keeps the links

How to test

1. Mark this PR ready for review (draft PRs skip the preview validate job).
2. Wait for the validate check to pass and deploy the hosted preview.
3. Review the updated pages on the PR preview (compare with production as needed):
   • View record activity
   • View settings activity
   • Tracking organization activity
   • Organizational Oversight & Reporting (training)
4. Confirm Record Activity distinguishes:
   • Org-wide: left sidebar Activity → Record Activity
   • Per-record: Inventory → record → Activity
5. Confirm org-wide record filters document Activity Filter and Record/Artifact Filter, and that record-attribute filters include downstream artifact activity.
6. Confirm Settings Activity documents query-builder fields (Category, Action, Actor, Target Type) instead of Event Type-only, and that What is tracked includes risk tiering and the other expanded scopes.
7. Confirm per-record filters still document Event Category / Filter by Value.

Production for side-by-side comparison:

• https://docs.validmind.com/guide/reporting/view-record-activity.html
• https://docs.validmind.com/guide/reporting/view-settings-activity.html

Optional local render:

skills/validmind-docs-coverage/scripts/render-pages.sh \
  guide/reporting/view-record-activity.qmd \
  guide/reporting/view-settings-activity.qmd \
  guide/reporting/tracking-organization-activity.qmd \
  training/administrator-fundamentals/organizational-oversight-reporting.qmd

What needs special review?

• Org-wide record filter field lists follow the shipped field_schema (hidden FE fields such as Linked Model / Template / Current step are omitted).
• Settings Category labels follow FE display names (formatScopeDisplay) where they differ from raw scopes (for example Inventory Records, Risk Assessments, Record Fields).
• Shared overview/steps includes are used by training slides — wording kept compatible with RevealJS consumers.

Dependencies, breaking changes, and deployment notes

• Depends on merged FE/BE work for SC-16807 (org-wide activity filters; LD flag launchdarkly.rollout.org-wide-activity-filters, offline default on)
• No breaking docs changes

Release notes

You can review and filter record and artifact activity organization-wide from Activity, including filters on event dimensions and current record or artifact fields. Settings Activity uses the same query-builder style filters for configuration audit events. 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 (documentation)
• PR linked to Shortcut
• Unit tests added (Backend)
• Tested locally
• Documentation updated (if required)
• Environment variable additions/changes documented (if required)

[CLAassistant]

All committers have signed the CLA.

[github-actions]

Lighthouse check results

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

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

Show Lighthouse scores

Commit SHA: a850986

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/reporting/tracking-organization-activity.html	0.91	0.70	1.00	0.82
/guide/reporting/tracking-organization-activity.html	0.91	0.75	1.00	0.82
/guide/reporting/view-record-activity.html	0.93	0.75	1.00	0.82
/guide/reporting/view-record-activity.html	0.93	0.76	1.00	0.82
/guide/reporting/tracking-organization-activity.html	0.91	0.75	1.00	0.82
/guide/reporting/view-record-activity.html	0.93	0.73	1.00	0.82

[cachafla]

@emmavdh small suggestion - I'd remove this bullet point from "What is tracked on settings activity?" here: https://docs-staging.validmind.ai/pr_previews/emma/sc-17354/docs-for-sc-16807/guide/reporting/view-settings-activity.html

"Global charter settings, including charter creation, updates, moves, and deletions"

[github-actions]

Validate docs site

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

[panchicore]

🌮 LGTM