Workspace
One file container for your company, with controlled access for members, agents and workflows.
One company file tree
Workspace holds your company documents, policies, playbooks, uploads, exports and generated files. File bodies are encrypted at rest. The dashboard Assistant, account agents and workflows save files here, including downloads and email attachments.
Account work stays in Workspace even if a write fails or access is denied. A member's personal assistant uses that member's personal Files instead.
Shared context and private Homes
The common tree contains company context, reference material and outputs. Each agent has a private Home for instructions, memory, skills, scripts and chat attachments.
- COMPANY.mdidentity, offering, voice
- DESIGN.htmlthe visual system
- Agents/one private Home per agent
- sales/
- AGENTS.mdidentity — read every run
- MEMORY.mdprivate memory — on demand
- skills/one folder per procedure
- scripts/reusable code
- chats/files members sent
- Studio/one folder per preset
- Downloads/fetched from external services
- your folders…policies, playbooks, FAQs
| Entry | Purpose |
|---|---|
| COMPANY.md | Company identity, offering, voice, people and links. |
| DESIGN.html | Living visual system. |
| Agents/ | One private Home per agent. |
| Studio/ and References/ | Preset folders and visual reference material. |
| Downloads/ | External files fetched by the dashboard Assistant. |
| Workflows/ | Persistent folders for workflows and their run-specific temporary files. |
| Apps/ | App source; read-only in Workspace. Change it through the app builder. |
Binding account instructions live in Settings → Instructions for agents, separately from COMPANY.md. Owners and editors maintain company context. Agents and workflows read root system files but cannot change them; nobody can rename, move or delete system entries.
Who reaches your files
Members browse according to dashboard access: viewers read; owners and editors maintain files. Agents read their own Home, company context and only the additional files you grant. Workflows reach the common tree, with protection rules still enforced.
Viewers read. Owners and editors maintain files.
Workflow step: also its workflow folder
Common Workspace tree
Protection and system rules still apply.
An agent always reads and writes its own Home. Other agents cannot browse it. An agent used in a workflow also reaches that workflow's folder for the run. Configure grants through agent Workspace access.
Watch out — Anyone who can use an agent can consult what it can read through that agent. Grant sensitive files with that audience in mind.
App source is unavailable to agents, even with whole-Workspace access. They use attached app tools instead. Workspace operators can browse source, but all changes belong in the app builder.