What your firm needs before day one.
LawHand platform requirements, the Microsoft 365 and Google Workspace integration matrix, the administrator consent each provider requests, and the onboarding sequence.
Platform requirements
LawHand runs in a current desktop browser with JavaScript and cookies enabled. There is no desktop client to install and no server for the firm to host. Each licensed user signs in with their own work account. The Microsoft Teams app and Office add-in are separate opt-in surfaces.
Microsoft 365
Tenant-wide consent is granted by an Entra Global Administrator and covers directory read, Outlook mail read and send, OneDrive and SharePoint file read/write, and calendar read/write. Firms can connect per user instead, which drops the directory scope and makes user matching manual. Microsoft Teams scopes are added only on explicit opt-in.
Google Workspace
Consent is approved by a Google Workspace Super Admin or a delegated administrator and covers read-only directory, Gmail read and send, Google Drive, and calendar. Individual users can connect their own account instead, which drops the directory scope.
Onboarding sequence
Agree the rollout scope, grant consent, verify the scopes actually granted, bind storage and prove one live read and write, then record the connection and test disconnect before go-live.
Current limits
Tenant-wide consent is presently a single broad bundle; narrower per-module consent and selected-site SharePoint access are planned, not current. SharePoint and Drive bindings are verified on write rather than assumed. Zoom Phone intake uses a separate customer-owned application, and QuickBooks Online is bound to a specific company.