OAuth setup — Google and Microsoft
Configuring OAuth for Google Drive and Microsoft OneDrive so the workspace can read and write your matter files.
Google OAuth
To use Google Drive as the system of record, register an OAuth client in Google Cloud Console for the firm's workspace and authorise the app to access Drive on your behalf. The flow uses standard OAuth so consent, and revocation, stay in your Google admin's hands.
Microsoft / Entra OAuth
To use OneDrive, register an application in Microsoft Entra ID and grant it the delegated permissions needed to read and write the firm's files. As with Google, your tenant administrator controls consent and can revoke it at any time.
Scopes and what they grant
Acta requests only the scopes it needs to read and write matter files in the storage you chose. It does not request broad mailbox or directory access. Review the requested scopes at the consent screen — they are the minimum required for the workspace to function.
Troubleshooting
- Consent blocked by admin policy — ask your Google or Entra administrator to approve the app for the workspace.
- Redirect URI mismatch — the redirect URI registered with the provider must exactly match the origin where Acta is hosted.
- Token expired — sign in again; the session cap and idle-lock are working as designed.