---
title: "AI Agent File Storage: Who Can Read the Output"
url: https://www.insulin.dev/blog/ai-agent-file-storage/
canonical: https://www.insulin.dev/blog/ai-agent-file-storage/
type: Blog
description: "AI agent file storage decides who reads an agent’s output. Check where it works, where kept files land and who can read each store before sensitive work."
---

# AI Agent File Storage: Who Can Read the Output

> Canonical HTML version: https://www.insulin.dev/blog/ai-agent-file-storage/

1.  [Home](/)
2.  [Blog](/blog/)
3.  AI Agent File Storage: Who Can Read the Output

# AI Agent File Storage: Who Can Read the Output

An agent’s files are read by whoever can read the store they land in, not by whoever was in the conversation. Check the record, the working folder and the kept files separately.

![Chengjun Yuan](/leadership/chengjun.jpeg)

Chengjun Yuan

Co-founder & CTO · Nov 2, 2026

 ![AI Agent File Storage: Who Can Read the Output](/images/blog/ai-agent-file-storage/hero.png)

**AI agent file storage** is where an agent writes files while it works, and where it keeps the ones meant to outlast the task. Who can read an agent’s output is decided by that storage, not by who was in the conversation. A private chat, or a scheduled job only its owner can see, can still save files into a folder the whole organization can open.

Insulin shows the gap plainly. A job there is private to its creator: not even an org admin can see, run, edit or delete it. Yet anything an organization agent’s job keeps for later runs belongs in the organization’s Drive, which every member can read. The job is hidden; what it keeps is not.

## Who can read what an AI agent writes?

**Whoever can read the store the output lands in.** An agent’s work leaves three things behind, and each can have a different audience:

-   **The record.** The transcript, the answer and, for scheduled work, the run history. Its audience is set by the conversation or the job: the people in a chat or channel, or the job’s owner.
-   **The working folder.** Scratch space on whatever machine or sandbox the agent runs commands on. Its audience is whoever can reach that machine, which can include administrators who were never in the conversation.
-   **The kept files.** What the agent saves for later, in a drive, a bucket, a shared folder or a knowledge base. Its audience is that store’s sharing list, which usually belongs to the agent’s owner rather than to the person asking.

The three are controlled in different places. A visibility setting on a chat or a job governs the record; storage permissions govern the other two. Reviewing one tells you nothing about the others, which is how a private task ends up writing into a shared folder without anyone changing a setting.

## Why a shared agent writes to shared storage

**An agent’s storage usually follows its owner.** A personal assistant works on your behalf, so what it keeps goes somewhere you control. An agent the organization owns serves many people, so it needs a store all of them can reach, and organization storage is the natural choice.

That is a sound design with one consequence a reviewer should state plainly: anything a shared agent keeps is readable at the breadth of that shared store, whoever asked and however private the request felt. Suppose a finance lead at Acme asks the organization’s analyst agent to draft next quarter’s discount plan. The draft arrives in a private chat. If the agent also saves the working spreadsheet, it is saved where the whole organization can read it.

The working folder has a quieter problem: scratch space is not storage. When several machines serve one shared agent, a later run may land on a different machine, so a scheduled job that expects the previous run’s files may not find them. And scratch is not necessarily gone, either. Insulin’s docs don’t say when a working folder is cleared, so confirm that before an agent writes sensitive material there.

## What to ask any agent workspace

**Get these answered before an agent gets sensitive work.** They apply to a custom bot, a hosted assistant and an agent platform alike:

1.  **Where does the agent run commands?** On a sandbox per person, or on a shared machine with a folder per person?
2.  **Where do kept files go, and who decides?** The agent’s owner, the person asking, or the agent itself?
3.  **Who can read that store, and who can change it?** These are often two different lists.
4.  **Can an administrator open a member’s own working space or files?** Many workspaces let admins act on members’ resources. Find out which ones.
5.  **How long do working folders last?** If nobody can say, that’s the answer to get before sensitive work starts.
6.  **Does the record follow the same rules as the files?** A private run history does not make the run’s files private.

## How Insulin handles agent output

**In Insulin, whose agent it is decides where the work happens and who can read what it keeps.** Organization agents work on a shared sandbox pool “in chat, in goals and in jobs alike, rather than on the personal sandbox of whoever is talking to them,” per the [AI Sandbox section of the docs](https://doc.fours.com/insulin/getting-started/#ai-sandbox-organization).

| Agent and surface | Where it works | Where kept files go | Who else can read |
| --- | --- | --- | --- |
| Built-in assistant or a personal agent, in chat, goals or jobs | Your personal sandbox | Not stated in the docs | No other member. An org admin can reach your sandboxes |
| Organization agent, in chat or a goal | A working folder of your own on a shared pool sandbox | The organization’s Drive, marked **Org** in Files | Every member can read the Drive; only an org ADMIN can change it |
| Organization agent, in a job | A folder for each run, on whichever pool sandbox it lands | The organization’s Drive | Every member can read the files. Only you can see the job and its runs |

**A personal agent keeps output away from other members, not from an org admin.** A personal agent is private to its creator, and its Share button is disabled, so no teammate can use it. Your sandboxes are yours to manage, but the [roles reference](https://doc.fours.com/insulin/getting-started/#your-own-things-are-not-role-gated) adds: “An org ADMIN can reach the others on your behalf — but not jobs.” What a personal agent leaves in your sandbox is within an admin’s reach; your jobs are not.

**A conversation with an organization agent is not a private store.** Each person’s conversations with organization agents get a working folder of their own on a pool sandbox, but what the agent keeps goes to the organization’s Drive, which the Files app shows beside your own Drive. “Every member can read the organization’s Drive; only an org ADMIN can change what is in it.”

**A job’s privacy covers the job, not its files.** A job runs as the agent that created it and is visible only to its owner, org admins included. For an organization agent’s job, each run works in scratch space: “the next run may land on a different sandbox, so a job should not count on finding the previous run’s files there.” Anything runs need to share belongs in the organization’s Drive, as the [jobs documentation on files a run leaves behind](https://doc.fours.com/insulin/jobs/#files-a-run-leaves-behind) puts it. One exception runs the other way: work Planner schedules in an organization channel belongs to the channel, and every member of that channel sees it. The other controls an unattended run needs are in [what to decide before background AI agents run](/blog/background-ai-agents-controls/).

### What Insulin leaves to you

The platform decides where output goes. Deciding what an organization agent should be asked to keep is yours:

-   **Keep restricted material away from organization agents.** Anything not every member may read should not be saved by one. Use the built-in assistant or a personal agent instead, knowing an org admin can still reach your sandboxes.
-   **Use a store with a sharing list when only some people should read the result.** An organization knowledge base opens only through a share: “Even an organization admin cannot open an org knowledge base they were not shared on.” An org admin creates one, and an agent attached to it with **Edit** access can create files in it. A file attached to a chat is a different store again: it belongs to the thread. [Attach a file to chat, or add it to a knowledge base](/blog/attach-a-file-or-add-to-knowledge-base/) covers that choice.
-   **Don’t build a job on the previous run’s working files.** Put what runs share in the organization’s Drive, and accept that every member can read it.
-   **Count kept files as cost as well as exposure.** Sandbox storage accrues “for as long as the sandbox exists,” running or stopped, per the [metering page](https://doc.fours.com/insulin/billing/metering/#sandboxes).

### What the docs don’t say

-   **How long working folders last.** The docs call them scratch space and give no retention period.
-   **Where a personal agent’s kept files go.** The Files app shows your own Drive beside the organization’s, but no doc sentence says a personal agent saves there.
-   **Whether an org admin can read a member’s own Drive.** Admins can reach members’ sandboxes; the docs don’t say whether that extends to the Drive.
-   **What separates working folders on one pool sandbox.** Each person and each job gets a folder of its own; the docs don’t describe the boundary between them.

## Pick the agent by who should read the result

**Before handing an agent sensitive work, name the people who should read the result, then choose the agent whose storage has that reader list.** If the answer is “only me,” a shared agent is the wrong tool, however private the chat feels. If it is “the whole team,” a shared agent’s shared store is the point: the output is where everyone can find it.

Check the record and the files separately, every time. Most surprises come from assuming one follows the other. For the rest of a workspace’s setup, from roles to sharing defaults, work through the [AI workspace admin checklist](/blog/ai-workspace-admin-checklist/).

## Sources

Primary sources for the platform rules cited above. Last verified November 3, 2026. Providers change their products, prices and terms without notice — check the source before relying on a detail.

-   [Insulin Getting Started — Fours Doc](https://doc.fours.com/insulin/getting-started/) — AI Sandbox (Organization): the shared sandbox pool organization agents work in, in chat, in goals and in jobs alike, rather than on the personal sandbox of whoever is talking to them; a working folder on a pool sandbox for each person's conversations with organization agents and for each job; working folders as scratch space, a later run possibly landing on a different sandbox; what organization agents keep held in the organization's Drive, marked Org in the Files app beside your own Drive; every member able to read the organization's Drive and only an org ADMIN able to change it. Your own things are not role-gated: desktop, memory, jobs, skills and sandboxes self-owned, and an org ADMIN able to reach other members' rows on their behalf, but not jobs; managing the organization's shared sandbox pool requiring org admin
-   [Insulin Jobs — Fours Doc](https://doc.fours.com/insulin/jobs/) — How Jobs Are Created: a job running as the agent that created it, private to its owner, who alone can see, run, edit or delete it, organization administrators included; work Planner schedules in an organization channel belonging to the channel and seen by every member of it. Files a run leaves behind: a run of an organization agent's job working in a folder of its own on a shared sandbox, the next run possibly landing on a different sandbox, a job not counting on finding the previous run's files there, and anything runs need to share belonging in the organization's Drive, which every member can read in the Files app
-   [Insulin Agents — Fours Doc](https://doc.fours.com/insulin/agents/) — User-Level vs Org-Level Agents: user-level agents private to their creator and org-level agents created only by org admins; Sharing Agents: only Organization agents can be shared, and a personal agent's Share button is disabled; knowledge-base access modes, Edit letting an agent create, update and deprecate files but never delete; Attachments in a Thread: sent attachments belonging to the thread and shown in its Files tab
-   [Insulin Knowledge Bases — Fours Doc](https://doc.fours.com/insulin/knowledge-base/) — Sharing and Roles: an org role alone granting no access to an organization knowledge base; access only through a per-knowledge-base share or org-wide sharing; even an organization admin unable to open an org knowledge base they were not shared on; org admin access required only to create one
-   [Insulin Metering — Fours Doc](https://doc.fours.com/insulin/billing/metering/) — Sandbox storage metered for as long as the sandbox exists, running or stopped
