---
id: "29c31fae-a1b2-4e86-8ccd-4c5fee5059c6"
name: "Record Salesforce demos"
micro_summary: "Record Salesforce demos with the built-in tab-scoped recorder, independently verify the Salesforce result, avoid PHI, retain the exact returned recording directory, and never reenact completed work."
status: "resolved"
see_also: [{"target": "2b6dcf53-6809-47b9-8643-0ef9f59cfd5f", "reason": "Canonical browser-harness recording workflow, built-in recorder guidance, and specialized low-level CDP fallback."}, {"target": "deaf859e-f976-461c-a99c-8b0176e3b734", "reason": "Proven Salesforce-specific recording pattern: independent pre/post verification, org-specific reality checks, browser proof, and cleanup."}]
scope: "Reusable browser-harness skill for recording a Salesforce UI demonstration safely: prepare org-specific test state, capture the Salesforce tab, verify the result independently, and retain or produce a reviewable video."
warnings: "Never record PHI, credentials, tokens, unrelated tabs, or desktop content. Never reenact completed work just to manufacture a recording; use only a matching retained capture whose timestamp and page identity can be verified."
---
## Default workflow

1. **Prepare safely.** Use synthetic, non-PHI data in the correct sandbox or explicitly approved org. Re-query org-specific IDs and prerequisites; never carry record-type IDs across sandbox refreshes.
2. **Prove before filming.** Use the narrowest independent Salesforce check available—metadata, CLI, or SOQL—to confirm the expected setup and define the visible payoff.
3. **Start recording.** Call `start_recording(name, title=...)` before the first meaningful browser action.
4. **Drive Salesforce.** Reuse the authenticated tab and follow the Salesforce subtree's iframe/shadow-DOM instructions rather than inventing selectors. Keep capture scoped to the Salesforce tab.
5. **Stop and retain.** Call `stop_recording()` immediately after the visible result and retain the exact returned recording directory.
6. **Verify after filming.** Independently confirm the resulting Salesforce state. Clean up test records when the target org requires it.
7. **Post-produce only when requested.** Follow the canonical `interaction-skills/make-video.md` workflow. Prefer the built-in recorder; use low-level CDP screencasting only for specialized needs it cannot cover.