CRM
CRM Data Ownership with Company Google Drive
See how Workspace separates CRM lead storage from its application database by using a company-controlled Google Sheet in Google Drive.
Reviewed
Direct answer
The approved Workspace CRM direction stores manually created and imported lead records in a Google Sheet owned by the connected company or user account, rather than treating Supabase as the lead record store.
The ownership model
Before CRM lead operations are enabled, the relevant company or user connects a Google account. Workspace then uses a Google Sheet in that account's Drive for the lead dataset.
This gives the account owner direct possession of the underlying spreadsheet while Workspace provides the CRM workflow around it.
Manual and imported leads follow one storage rule
Leads entered through the CRM form and leads imported from an Excel-compatible file should resolve to the same company-owned Google Sheet model.
- Google connection is required before lead creation or import.
- Imported rows must be validated before they are written.
- CRM pipeline reads and writes must preserve the connected company's data boundary.
- Application configuration and authorization records remain separate from the lead dataset itself.
What this does not mean
Drive ownership does not remove the need for secure OAuth token handling, company-scoped authorization, auditability, validation, and recovery planning.
A company should also understand Google account access, sharing permissions, storage limits, and what happens if the connected account revokes access.
Key facts
- CRM leads are designed to live in the connected account's Google Sheet.
- Manual creation and spreadsheet import use the same ownership principle.
- Google OAuth connection and application authorization remain required security layers.