# Access Their Drive & Files

The Drive is your employee's file cabinet. Everything they produce, from documents and journal entries to images and drafts, is saved here for you to review.

## TL;DR

Every piece of work an employee produces is saved in their Drive. Documents, journal entries, images, drafts. Browse it per employee, per team, or company-wide. When an employee cannot send something directly (like an email without Gmail connected), they save the draft to the Drive so you can always review what they would have done.

## What is the Drive?

The Drive is where you go to see everything an employee has created. Think of it as their desk with all their files on it. Anything they write, draw, generate, or draft ends up here, organized into folders.

When you open an employee's Drive, you see a folder structure like this:

| Folder | What is inside |
|--------|---------------|
| **Notebook** | The employee's written work. Contains two sub-folders: **Documents** (reports, blog posts, research, drafts) and **Journal** (daily entries about what they accomplished) |
| **Deliverables** | Final output meant for you or external use |
| **Storage** | Media files. Contains **Uploads** (files you shared), **Screenshots** (from desktop control), and **Artwork** (generated images) |

## Where to Find It

The Drive is available at three levels. The higher you go, the more you see.

| Level | What you see | How to get there |
|-------|-------------|-----------------|
| **Employee** | One employee's files, organized by folder | Workspace, select employee, click **Drive** tab |
| **Team** | All team members' files, grouped by employee | Workspace, select team, click **Drive** tab |
| **Company** | Everyone's files, grouped by team then employee | Workspace, click Organization, click **Drive** tab |

## How It Works

### Everything Gets Saved

Employees automatically save their work to the Drive. You do not need to ask them. When an employee writes a blog post, it goes to Documents. When they generate an image, it goes to Artwork. When they finish meaningful work, they write a journal entry.

### Drafts When Tools Are Not Connected

This is one of the most useful things about the Drive. When an employee does not have access to an external tool, they still do the work and save it as a draft.

| Scenario | What happens |
|----------|-------------|
| "Send an email" but Gmail is not connected | Employee writes the full email draft (subject, body, recipient) and saves it to Documents |
| "Post on social media" but no social tools | Employee writes the post content, generates images, and saves everything to the Drive |
| "Create a report" without data tools | Employee uses web search, does the research, and writes the report to Documents |

You can review the draft, see exactly what the employee would have done, and connect the tool when you are ready. This builds trust before giving full access.

### Navigating from Chat

When an employee mentions a file in chat ("I wrote the report and saved it to your Drive"), you can click the link to jump directly to that file. The Drive sidebar opens and shows you the content.

## What You Can Do

| Action | How |
|--------|-----|
| **Browse files** | Open the employee's **Drive** tab |
| **View a file** | Click any file to open a side panel showing the full content or image |
| **Edit journal entries** | Click "Edit" on personal journal entries |
| **Navigate from chat** | Click file links in chat to jump to that file in the Drive |
| **See team output** | Select a team, open their **Drive** tab to see all members' files |
| **See company output** | Select Organization, open the **Drive** tab to see everyone's files |

## How to Set It Up

**Nothing to do.** The Drive is built in. Every file the employee creates is automatically saved and organized.

## Tips & Tricks

- **Check the Drive after complex tasks.** Blog posts, reports, research, and email drafts are saved here automatically
- **Review drafts before connecting tools.** See what the employee would do with a tool before you give them access. Review drafts first, connect when you trust the output
- **Use the team Drive for oversight.** See what the entire team has produced in one view, grouped by employee
- **Ask for revisions, not new files.** If a document needs changes, tell the employee to update the existing one instead of writing a new file
- **Journal entries tell the story.** Check the Journal folder to see the employee's own summary of what they did and why

## Good to Know

- **Internal files are hidden.** The employee's internal memory and configuration files are not shown. You only see work output
- **Per-employee storage.** Each employee has their own Drive. Files are not shared between employees. The team and company views aggregate but do not merge
- **No deletion from UI.** Drive files are owned by the employee. You can read and review but not delete from the interface
- **Journal entries are editable.** You can edit personal journal entries. Documents and media are read-only from the Drive. To make changes to a document, ask the employee to revise it

## Frequently Asked Questions

**Q: Can I edit files in the Drive?**
A: Journal entries are editable. Documents and media are read-only. To change a document, ask the employee to revise it.

**Q: Are files shared between employees?**
A: Each employee has their own Drive. To share work between employees, ask them to delegate or send content to a teammate.

**Q: What happens when I connect a tool the employee was drafting for?**
A: The employee uses the tool directly next time. Previous drafts remain in the Drive for reference.

**Q: Is there a storage limit?**
A: No practical limit for normal usage.

**Q: Can I upload files to the Drive?**
A: You can share files with the employee through chat (drag and drop or attach). Those files appear in the Storage/Uploads folder.

**Q: Where do generated images go?**
A: Images created by the employee (like illustrations or diagrams) go to Storage/Artwork. Screenshots from desktop control go to Storage/Screenshots.