Integration
Connect Google Drive to Polaris
Files a worker produces already arrive as attachments on the task. Files your team already keeps in Drive are the part still waiting.
What connecting buys
Google Drive is an OAuth connection in the Polaris catalog covering docs, sheets and files. It authorizes through Google sign-in, a flow that has not shipped, so the connection stays pending and stores no credential. Files produced by a worker do not depend on it: deliverables arrive as attachments on the task comment, and written work lands in versioned Polaris docs.
- Auth mode
- Google OAuth
- Status
- Pending, flow not shipped
- Output files
- Attached to the task today
Two different file problems
People ask for a Drive connection for two unrelated reasons. The first is reading: the brand guidelines, the spreadsheet of last quarter's numbers, the folder of contracts. The second is output: where the thing a worker made ends up.
Only the first one needs Drive. Output is already solved. A worker attaches files to the task it delivered, including generated PDFs, and written work is drafted into the Docs tree where it is versioned, commentable and reviewable. Nothing about that path routes through Google.
Reading versus producing
Reading Drive, not available yet
- Working from a spreadsheet the finance team maintains
- Pulling context out of an existing folder of material
- Reading a contract your legal folder already holds
- Anything that starts with a file somebody else made
Producing files, available now
- Deliverables attached to the task comment, PDFs included
- Written work as versioned docs with comments and file review
- A nested doc tree that behaves like the wiki it replaces
- Content pasted into the task when the source is short enough
What the Drive connection covers
The catalog entry names docs, sheets and files. Roadmap, not shipped.
Docs
Prior art a worker should read before writing anything new, which is the difference between a first draft and a restatement.
Sheets
The numbers a finance or data worker is expected to reconcile against, in the format they are actually kept in.
Files
Everything else a team hoards in folders, where the scope of a grant matters more than the file count.
Workers that will want this connection
Hire an AI research analyst
Assign the question on Tuesday afternoon and read the brief before your Wednesday call, with every claim carrying the URL it came from.
Hire an AI financial analyst
You supply the figures; it writes the explanation of what moved, why it matters and which assumption the whole thing rests on.
Hire an AI content writer
Briefs go in as tasks, drafts come back as versioned docs you can comment on line by line, and your voice rules live in a file rather than in one person's head.
Budget reports written for the people who did the spending
Plan against actuals is easy to produce and hard to read. A worker writes the variance up in sentences a department head will actually act on.
Finding where the SOP and the real procedure came apart
Every written procedure starts accurate and drifts. A worker compares the document to how the work actually ran and reports the difference.
When the deliverable is a file
A chat reply is not a deliverable if the thing you needed was a document somebody can open.
Questions people ask
+Can a Polaris worker open a file from my Google Drive?
Not today. Drive authorizes through Google sign-in and that flow has not shipped, so the connection stays pending with no credential stored. Material a worker needs can be pasted into the task or into a Polaris doc in the meantime.
+Where do the files a worker produces end up?
On the task. A delivery arrives as a comment with the work in it, and generated files, including PDFs, are attached to that comment. Written work is also drafted into the Docs tree, where it is versioned and open to comments.
+Does Polaris replace Google Drive?
No, and it is not trying to. Polaris Docs is a nested block editor with versioning and review, which covers written work. A general file store for video, design source files and everything else your company keeps is a different product.
+Will a Drive grant cover my whole account?
That is decided at Google's consent screen when the flow ships, not inside Polaris. Whatever the grant covers is what a worker can reach, which is why the scope is worth reading rather than clicking past.
Related
Every tool a Polaris worker can be given
One catalog, one credential per tool per organisation, authorized by an owner and used by every worker who carries it.
Connect Gmail to Polaris
The honest version: Gmail is in the catalog, the Google sign-in flow has not shipped, and the product says pending rather than pretending.
Connect Google Calendar to Polaris
Scheduling is the one thing an assistant is asked for first, and it is the one connection still waiting on Google sign-in.
When the deliverable is a file
A chat reply is not a deliverable if the thing you needed was a document somebody can open.
Hire an AI research analyst
Assign the question on Tuesday afternoon and read the brief before your Wednesday call, with every claim carrying the URL it came from.
Budget reports written for the people who did the spending
Plan against actuals is easy to produce and hard to read. A worker writes the variance up in sentences a department head will actually act on.