Every employee keeps its own Drive, but you shouldn't have to open ten employees to find one file. Company Drive rolls every employee's Drive into one company-wide view: every document, transcript, and deliverable your whole workforce has produced, browsable and searchable from one tab.
An employee's individual Drive is where its own work lands, notebook entries, uploaded files, transcripts, deliverables. That's useful when you know which employee produced what. Company Drive is for when you don't, one view that rolls up every employee's Drive into a single company-wide file library, rooted at Org Files.
Browse or search across the whole workforce's output at once instead of opening each employee one at a time to check what it's produced. A report your content writer finished last week and a transcript your sales assistant logged this morning show up in the same place.
It's a read view over the same underlying files, nothing is duplicated or moved. Open a file from Company Drive and you're looking at the exact same document the owning employee has in its own Drive. That's the difference from a Team Drive tab, which shows the same rollup narrowed to one team's members, and from an individual employee's own Drive, which shows only that employee.
Files a human uploaded rather than an employee's agent, chat attachments and documents used to train an employee, don't belong to any one employee. Those sit in Company Drive's Uploads branch instead of nested under a name, and can be filtered by project.
Company Drive aggregates every employee's individual Drive into a single company-wide tab. Instead of remembering which employee handled a task and opening its Drive specifically, browse or search the whole company's file output at once.
It's a rollup, not a copy. Files stay owned by the employee that produced them; Company Drive just gives you one place to find any of them.
Open Company Drive and the tree starts with your regular teams, each one holding its members' Drives grouped inside it, followed by a Bench group for any employee not currently on a team. Terminated and resigned employees drop out of the view entirely, so the tree reflects who is actually active today, not a full history of everyone who ever worked here.
A toolbar toggle switches between two reads of the same data: Work files shows just the documents, images, video, and screenshots an employee's agent produced, while All files adds the Internal group, notebook, work logs, private notes, for anyone who wants the full picture including an employee's own working notes.
Every file the tree resolves opens in the same drawer used everywhere else in the product: content preview, comment thread, and Copy, Download, Share, and Fullscreen actions. Sharing a file from Company Drive copies a link any tenant member can open directly to that file, no separate export step required.
Not every file in Company Drive was produced by an employee's agent. Files a human attaches in chat, and documents uploaded to train an employee, are tracked separately as tenant uploads with no employee attached to them at all, so they show up in Company Drive under their own branch rather than nested inside anyone's name.
These uploads can be filtered by project from the same view, useful when you want to see everything a human fed into the system for one piece of work without also pulling in every employee's generated output.
The overflow menu offers a single Download drive action that zips every active employee's files, across every team plus Bench, into one archive. It hydrates each file's content before zipping so the export is a real snapshot, not just a list of links, useful for an offsite backup or handing a full output history to someone outside the product.
Files save themselves the moment an employee produces them
There is no save step. Whenever an employee writes a document, generates an image or video, exports a spreadsheet, or captures a screenshot during browser or desktop work, that file is written to its Drive as part of the action itself.
Each file is tagged with where it came from, which is how the six-group layout stays accurate without you filing anything by hand: a PDF report and a Markdown note the employee wrote both land in Work files; a screenshot from a browser automation run lands in Screenshots regardless of what it contains.
Team and company Drive are read views over the same underlying files. Opening a report at the team level shows the exact document the owning employee has, so oversight never requires opening employees one at a time to find what a team produced this week.
An employee finishes a research document or a client-facing export. Open its Drive, find it in Work files, preview it in the side panel, and leave a comment asking for a specific change instead of waiting for a chat message to surface it.
Open Team Drive to see every member's files grouped by employee in one view, without switching between employees one at a time to piece together what the team actually shipped.
Open the Internal group's Work logs to read the employee's own daily summary of what it did and why, useful when a result looks off and you need the reasoning behind it, not just the output.
An employee generates an image or exports a spreadsheet mid-task. Assign the file to the relevant project directly from its panel so it stays attached to the work it belongs to instead of getting lost in a general file list.
Yes. An employee's own Drive holds just that employee's work. Company Drive rolls up every employee's Drive into one searchable, company-wide view, organized by team and then by employee.
No. Company Drive is a read view over the same files each employee already has in its own Drive, nothing is duplicated.
Yes, that's the point of Company Drive: browse or search everything your workforce has produced without opening employees one at a time.
Chat attachments and training documents have no employee owner, so they appear in Company Drive's own Uploads branch rather than nested under any employee, and can be filtered by project.
Yes. The overflow menu's Download drive action zips every active employee's files across the whole company, including Bench, into one archive.
Company Drive is part of Where their work lives.
Your AI agents manage their own workspace. Scheduled tasks run daily, weekly, or on custom cron cadences. A built-in kanban board tracks what is in progress. Every document lands in a personal Drive. A daily work journal logs decisions, outcomes, and next steps automatically.