Intake connectors

Google intake connection center

This lane stages linked records for review. Connect Google, inspect Gmail and Drive preview data, verify Gemini, and then route records into the matter workflow only after review.

Start intake uploadOpen storage connectorsOpen assisted review
Google connection center

Gemini, Gmail, Drive, and visual intake on one portal surface

Each signed-in user can save their own Google OAuth app details here, connect Gmail and Drive with their own credentials, then move directly into intake and Gemini review.

Google connection requiredOpen storage connectorsOpen AI workbench
Per-user Google OAuth config
Bring your own Google OAuth client. This config stays scoped to the current signed-in user on this browser.
Google setup instructions
  1. In provider console, enable the Gmail API, Google Drive API, and Google Calendar API for your project.
  2. Create an OAuth 2.0 Web application client.
  3. Add this exact authorized redirect URI: https://your-app/api/connectors/google/callback
  4. Paste the client ID and client secret above, then save the per-user config.
  5. Click Connect Google to authorize this browser session for your own account.
Scopes should include openid, email, profile, Gmail read access, Drive access, and Calendar read access. Use Google test users if your OAuth app is still in testing.
Google account
Not connected yet
Browser session state
Gmail
0
live preview threads
Drive
0
live preview files
Calendar
0
live preview events
Staged uploads
0
browser-visible local records
Google lane
Bring your own Google OAuth app per user, save it here, then connect this browser without touching shared env config.
Visual intake
Folder-style review for Gmail, Drive, Calendar, and local records now lives on the same portal surface.
Gemini lane
Gemini remains beside intake so summarization, rescan, and timeline synthesis can stay tied to what was just staged.

Google workspace

Connect Gmail, Drive, and Calendar so ProSe can organize messages, attachments, folders, and court dates into the active matter.

Connect GoogleUpload from device now

Checking Google connection…

Visual intake explorer

Folder-first intake across Gmail, Drive, calendar, and browser-staged records

This rail is meant to feel like a litigation intake desk, not a flat upload dump. Scan Google lanes, narrow the record set, then import only the source you actually want to pull into the matter.

Reconnect Google
All matters
0
browser-visible case workspaces
Imported / staged docs
0
Drive + device document volume
Gmail threads
0
recent legal communication preview
Calendar / hearings
0
event-ready records
Ingest progress
0%
timeline + evidence coverage posture

Google Drive + local folders

Drive buckets and browser-staged records stay together so the intake lane still works before or after live OAuth.

No folders available yet. Open upload intake.

Gmail + calendar lanes

Communication and hearing-oriented lanes stay separate until you decide to import them into the active matter.

No folders available yet. Open upload intake.

Folder contents

Search across folder contents, narrow by source, and selectively import live Google lanes into the active matter.

No records match this search and source filter yet. Review connections.

All matters overview

0 visible
No browser-visible matters yet. Device upload, Google import, or intake creation will start populating this command rail.

Hardening posture

Intake overview
Selective import
Pull only Gmail, only Drive, only Calendar, or all Google lanes at once instead of forcing a single bulk path every time.
Searchable intake
Folder contents can now be searched and filtered by source, which matters once the preview count stops being toy-sized.
Lane visibility
The selected folder now shows lane metadata, source, and visible record count so intake review feels deliberate instead of opaque.
Matter-safe refresh
Google preview refresh and browser-side matter sync stay on the same surface, reducing the chance that intake feels detached from the live workspace.
Analysis service missingGemini disabledAPI key missingNeeds setup
Gemini connector controls
Save a Gemini API key here, then test live analysis, timeline synthesis, and report generation when this connection is authorized.
Idle
Training document payload
Rescan uses up to 1 staged record from the current browser workspace.
Connector response
{
  "ok": false,
  "note": "Check the connection to review Gemini readiness."
}
Analysis + job output
{
  "ok": false,
  "note": "Run training-text analysis, timeline build, report generation, or record refresh to review the integrated Gemini workflow."
}