Skip to main content

File Space

/file-space is EnClaw's built-in file area — a place where you and your agents can put documents, spreadsheets, exports and anything else the work produces or needs. Upload a contract for an agent to summarise; find the report an agent generated for you last Friday; share a file with a colleague via a link. It all lives in File Space.

When an agent hands you a download link in chat, it points here — so even if you never browse the page, you're using it.

The page at a glance​

  • A Folders pane with the directory tree (and a Show system toggle for system-generated folders you don't normally need).
  • A file table for the selected folder — name, type, size, a PII column, and per-file actions.
  • Per file: Download, Share, Delete, plus copy-path and copy-ID shortcuts for referencing the file elsewhere.

The basics​

Uploading​

  1. Open File Space.
  2. Navigate to the folder you want (or create one — see below).
  3. Drag files straight in from your desktop, or use the upload button.

Once uploaded, the file is available to agents too — you can say "summarise the contract I just uploaded" and the agent reads it from File Space. Agents can read the common document formats (PDF, Word, Excel and friends) directly.

Downloading​

Open the file's entry and choose Download. Files agents generate for you — reports, exports, drafts — land in File Space as well, so this is also where you collect an agent's homework (with My Sessions as the quickest index of which run produced what).

Download links have the form /file-space/file/<id> and open a small landing page that checks it's really you before serving the file — which makes them safe to paste into chat, email or documents.

Folders​

File Space is organised as ordinary nested folders. Different areas may be scoped differently — some folders are yours, some belong to a team or to the whole organisation — so where you put a file affects who can come across it. Keep personal working files in your own area; put shared deliverables where the team expects them. (Per-file access control is enforced behind the scenes, so seeing the page never exposes files you don't have rights to.)

A tidy habit that pays off: one folder per project or client, mirroring how your Slack/Teams channels are organised. Agents and humans alike find things faster.

Sharing files​

Rather than emailing attachments around, share a link:

  1. Open the file and choose Share.
  2. Set what the link allows — Read is the safe default; Read/Write if the recipient should be able to change it.
  3. Set how long the link lives (a date, or never).
  4. Copy the link and send it however you like.

Two properties make these links safer than an attachment:

  • They're time-limited. A link expires when you said it should — a file shared for this week's review isn't still floating around in someone's inbox next year.
  • They're permission-controlled. The link grants exactly the level of access you chose, and access through it is logged.

Your existing shares are listed with their status (active, expired, revoked). If you shared something by mistake, revoke the link; expiry then becomes immediate rather than eventual.

Size and type limits​

Folders can carry rules set by your organisation:

  • Size limits — a cap on how large files (or a folder overall) can be. An upload over the cap is refused with a clear message rather than silently trimmed.
  • Type restrictions — some folders accept only certain kinds of file (documents and spreadsheets, say, but not executables). If your file's type isn't welcome in that folder, you'll be told at upload time.

The specific numbers and types vary by organisation and by folder, so if an upload bounces, the message it gives you is the authoritative answer. Genuinely oversized-but-legitimate files are a quick request to your admin.

PII scanning on upload, in plain language​

When you upload a file, EnClaw can automatically check it for personal information — things like email addresses, phone numbers, government identifiers and credit card numbers. Think of it as a colleague glancing at the document on its way in and saying, "heads up — there are card numbers in this."

What it means for you:

  • It's protective, not accusatory. The scan exists so sensitive data doesn't end up somewhere too widely shared by accident — a spreadsheet full of customer phone numbers dropped into an org-wide folder, for instance.
  • Flagged doesn't mean blocked, necessarily. A flagged file shows a "Detected" badge in the PII column — click it to see what was found and where, with a prompt to redact or restrict access. Depending on your organisation's rules for that folder, the upload might instead be refused with an explanation.
  • The fix is usually placement or preparation. Move the file to a more restricted folder, or strip the personal details it doesn't need to carry, and upload again.

If you routinely work with files that legitimately contain personal data, your admin can make sure the right folder is set up for them.

Good to know​

  • Integrity is checked. Files are fingerprinted on upload, so what you download later is verifiably what went in.
  • Access is logged. Who touched what, and when, is recorded — reassuring for anything sensitive.
  • Retention rules may apply. Your organisation can set how long files in a given area are kept; don't treat File Space as a forever-archive unless your admin says that area is one.
  • Cloud drives can appear here too. Your organisation may mount shared storage (such as OneDrive or SharePoint areas) into File Space, so some folders you see are windows onto those systems.

For files an agent should act on — "read this, then draft the response" — upload first, then ask, and mention the file by name. More conversation tips in Chat.