Connect Google Docs to ECA
Give ECA governed access to Google Docs’s 21 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Google Docs to ECA in four steps
Admins approve the server once. Everyone in ECA then gets it through the same governed connection.
- 1
Approve Google Docs in Runlayer
Add Google Docs from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect ECA to Runlayer
Users add the Runlayer Plugin to ECA by following Runlayer’s setup guide. ECA reaches Google Docs’s 21 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
ECA setup guide - 3
Sign in to Google Docs
Sign in the way Google Docs requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Google Docs from ECA
Google Docs’s approved tools appear in ECA. Every call is checked against policy and recorded.
Tools
21 Google Docs tools in ECA
Runlayer policy decides which of these ECA users can call. 7 read data only and 5 can change or delete data.
Add comment
Add a comment to a specific text range in a Google Docs document.
Apply doc updates
Apply an ordered batch of raw Google Docs API Request objects to a document via documents.batchUpdate.
Create file
Markdown (recommended, default path): uploaded as text/markdown and converted by Google Drive's native markdown importer (headers, bold, italic, lists, tables, blockquotes, fenced code blocks, links,…
Delete between text
Delete a whole block of a document — a heading and everything beneath it, tables included — by naming the text at each end instead of computing character indices.
Delete text
Delete all occurrences of specific text from a Google Docs document.
Edit table
Structurally edit an existing table in a Google Doc: insert/delete rows and columns, set a column width, style a cell (background color, vertical alignment, padding), replace a cell's text, or…
Fetch
Fetch the content of a Google Docs document using its document ID.
Fetch all tabs
Fetch content from all tabs in a Google Docs document.
Control
What Runlayer can see and stop in ECA
Some controls apply to every client at the gateway. Others depend on what ECA exposes to Runlayer.
Gateway policy (available)
Every Google Docs call from ECA passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, ECA as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for ECA yet, so control happens at the gateway.
Frequently asked questions
Connect more