Use cases
Jobs where this local tool earns its keep. Each names the role, the task before the deadline, the steps, and what done looks like.
1. Salesforce admin across multiple orgs before Dec 1
Who: A Salesforce administrator responsible for several production orgs and sandboxes who must prove which integrations still call SOAP login().
Task: Before 2026-12-01, produce a residue list with owners so SOAP login does not start failing overnight when Use Any API Auth is enforced.
Steps: Per org, pull Login History and API Total Usage; grep Partner/Enterprise WSDL login(); ask middleware vendors; open the home board; add rows with permission, recency, owner, and IP notes; export Markdown into the security ticket; assign migrate-or-perm work.
Result: No surprise SOAP login failures on Dec 1. Every hit has an owner, an evidence source, and a clear next action toward permission grant or External Client App plus OAuth.
2. Integration engineer replacing Partner WSDL login
Who: A Salesforce integration engineer who owns a legacy Partner WSDL client that still authenticates with SOAP login().
Task: Retire SOAP login() in favor of External Client App plus OAuth (client credentials or JWT Bearer) before the December permission cut creates production pages.
Steps: Confirm the hit on the inventory board; choose JWT Bearer or client-credentials; implement the new auth path; re-test reads/writes; mark the residue row resolved in the change ticket; keep Help URLs beside the export.
Result: The integration authenticates without SOAP login(). Auditors can see the board export showing the row closed and the replacement auth method documented.
3. Security review asking for evidence of SOAP callers
Who: A security-focused Salesforce admin preparing an audit packet for platform security requirement updates.
Task: Export a readable inventory with sources, permission gaps, and owners without pasting org credentials into third-party SaaS.
Steps: Fill the board from Login History plus vendor asks; note broad-IP and six-month unused adjacent rules; copy Markdown; attach official Help and The Daily Org calendar links; store the packet in your ticketing system.
Result: The audit packet shows residue and remediation owners. This local board never received org credentials, and dates remain anchored to official Help.
How-to and FAQ.