Objective

Pilot a Litify + Microsoft Teams + Google Drive workflow for Matter-level case-folder access, starting with Sam only and one live Matter.

What changed

• Verified the active Drive connector account as sam@aguiardrive.com and confirmed the shared-drive case-file universe.
• Confirmed the current Matter fields and the pilot metadata path for Case_Folder_Google_Drive__c and View_Case_Folder__c.
• Validated the metadata deploy path and documented the deploy command and rollback path.
• Found a strong live Matter-to-folder match for MAT-26052667782 / Jaden Sanders | 5/19/2026 | Automobile Accident.
• Populated the pilot Matter with the Google Drive folder URL and confirmed View_Case_Folder__c renders as an Open Google Drive Folder link.

Commands or live systems touched

• Live Salesforce/Litify org LITIFY_ORG.
• Google Drive connector for sam@aguiardrive.com.
• Teams connector read path, with send still blocked by missing ChatMessage.Send or Chat.ReadWrite.
• Session evidence: /Users/samaguiar/.codex/sessions/2026/05/27/rollout-2026-05-27T18-34-53-019e6b93-90a5-7703-b99e-0a5b6279de2c.jsonl.
• Local pilot artifacts: /Users/samaguiar/Documents/Projects/admin/session_logs/litify-teams-drive-pilot-2026-05-27/PILOT-CHECKLIST.md and /Users/samaguiar/Documents/Projects/admin/session_logs/litify-teams-drive-pilot-2026-05-27/drive-matter-match-sample.md.

Rollback state

• Revert the Matter field write by clearing Case_Folder_Google_Drive__c on the pilot Matter.
• If the metadata pass is rolled back later, restore the old View_Case_Folder__c formula and remove the added layout placements.
• The pilot checklist captures the validated deploy command and rollback notes.

Open follow-up

• Teams write-path reauth is still required for chat posting.