Google Docs
Google Docs is Google's browser-based word processor inside the Google Workspace suite, used to draft and collaborate on documents in real time.
Definition
Google Docs is Google's browser-based word processor inside the Google Workspace suite, used to draft and collaborate on documents in real time. In the Salesforce context, Google Docs has appeared in three different integration patterns over the years: a now-retired Salesforce for Google Apps connector that surfaced Docs in a related list on records, the modern Files Connect feature that lets Google Drive (including Docs files) act as an external content source, and the Quip-and-Slack integrations that compete with Docs for the same collaborative document space.
Today, Google Docs is most often integrated via Files Connect or via the Google Workspace add-on for Gmail, both of which let a Salesforce record reference a Google Docs file without storing the content inside Salesforce. The Files Connect path supports OAuth-based access to a user's Drive, lets Salesforce search Drive contents from the global search bar, and surfaces Docs as Content references on records. The legacy related-list pattern is gone; new orgs use Files Connect or the Gmail Integration's attachment workflow.
How Salesforce surfaces Google Docs on records today
The legacy Salesforce for Google Apps connector
The original integration shipped under the Salesforce for Google Apps banner. It added a Google Docs related list to standard records and let users attach a Doc by URL or pick from their Drive. Behind the scenes, Salesforce stored only the URL; the document itself lived in Google Drive. The feature was retired with the broader Google Apps rebrand and is no longer installable on new orgs.
Files Connect as the modern path
Files Connect lets Salesforce treat external content stores (Google Drive, OneDrive, SharePoint, Box) as searchable file sources. Once configured, Drive contents (including Docs) appear in Salesforce global search; users can attach a file reference to any record without copying the underlying content into Salesforce. Files Connect handles the OAuth handshake per user and respects the user's Drive permissions when displaying results.
Attaching a Google Doc to a record
With Files Connect configured, the Files related list on any record gets an Add Files button that includes External Sources as an option. Picking the Google Drive source opens the user's Drive browser inside Salesforce. The picked Doc is attached as a ContentDocument with an external pointer; the Doc itself stays in Drive. Clicking the file in Salesforce opens it in Google Docs in a new tab.
Sharing and permissions
Files Connect respects two sharing models simultaneously. The user's Drive permissions control whether they can find and open the Doc. Salesforce sharing on the ContentDocument controls whether other Salesforce users can see the file reference on the record. A Doc visible in the related list to a Salesforce user who lacks Drive access opens in a Google permission-denied screen, not in Salesforce.
The Gmail Integration angle
When a Doc URL appears in a Gmail message and the user logs the email to Salesforce via the Gmail Integration, the email body retains the URL. Clicking the link from the Salesforce email message opens the Doc in Google Docs in a new tab. This is the most common way Google Docs ends up referenced on Salesforce records today; the integration is incidental rather than feature-rich.
Quip as the Salesforce-owned alternative
Salesforce owns Quip, a collaborative document product that overlaps with Google Docs in scope and intent. Quip integrates natively with Salesforce: Quip documents can be embedded on record pages, edited in place, and tied to record-level templates. Customers who want the deepest document integration choose Quip over Google Docs; those who already use Google Workspace organization-wide rely on Files Connect.
Cert exam and historical relevance
Older Salesforce certification study guides reference a Google Docs related list and the now-gone Salesforce for Google Apps connector. Current exam material covers Files Connect, External Data Sources, and Quip. When reading legacy training material, mentally substitute Files Connect for the old Google Docs related list, and Quip for any deeper embedded-document scenario.
Set up Google Docs through Files Connect
Files Connect is the only supported way to surface Google Docs on Salesforce records in a new org. The setup involves an external data source, an authentication provider, and per-user OAuth.
- Create an Authentication Provider
Setup, Auth Providers, New. Pick Google as the provider type. Enter the OAuth client ID and secret from a Google Cloud Platform project the admin owns.
- Register the External Data Source
Setup, External Data Sources, New. Choose Files Connect: Google Drive as the type. Pick the Auth Provider created in step one. Save.
- Grant Files Connect access via permission set
Create or edit a permission set with Files Connect Cloud and Salesforce CRM Content User enabled. Assign to users who need to attach Drive files.
- User completes the OAuth handshake
On first use, the user clicks an external data source link in Setup or in a Files picker; Google's OAuth screen asks for consent. Once approved, the refresh token is stored against the user.
- Search and attach from the Files related list
On any record, click Add Files in the Files related list, switch to External Sources, pick the Drive source, search and select the Doc. The file appears in the related list with a Drive icon.
- The legacy Google Docs related list is gone. New orgs cannot install the old Salesforce for Google Apps package; use Files Connect instead.
- Files Connect respects Drive permissions. A Doc visible in Salesforce search to one user may be invisible to a colleague if the colleague lacks Drive access to the same file.
- Search results from Files Connect can lag Drive indexing by several minutes. Brand-new Docs may not appear in Salesforce global search immediately.
- OAuth consent must be renewed periodically. Users who see a Reauthenticate prompt in the Files picker need to walk through the consent screen again to refresh the token.
Trust & references
Cross-checked against the following references.
- Files ConnectSalesforce Help
- Set Up Files Connect for Google DriveSalesforce Help
Straight from the source - Salesforce's reference material on Google Docs.
- Use Files Connect Data SourcesSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What was the Google Docs integration?
Q2. What's a modern alternative?
Q3. Should you use the legacy Google Docs integration?
Discussion
Loading discussion…