16 August 2026
Updated 16 August 2026 · Beech Product Education Team
Where project files live now — Vault for the firm pool, Studio for canvases, Jot, and links.
Intent: Explain vault vs studio in a way that a new team member can follow without prior Beech context.
Who this helps: Architecture studio admins, managers, and contributors who need a repeatable operational workflow.
If you used to look for a file tree under Studio, look at Vault instead. Studio stayed creative; Vault is the firm storage pool.
Vault
Open any project → Vault. Folders, uploads, trash, and a firm-wide usage meter. Capacity is pooled across active projects — Starter includes 50 GB, Professional 125 GB, Business 250 GB. Admins can buy one monthly add-on when you need more.
Link files to tasks from the task panel. Optionally require a Vault file before Done in Info → Project settings.
Studio
Canvases, Jot, and inspiration links. Not the place for the project file archive. Embeds in Jot can still pull from Vault files.
Prerequisites
- Confirm you can access the project and the page referenced in this workflow.
- Collect any drawing references, due dates, and ownership details before you start.
Expected outcome
By the end of this workflow, your team has one visible, repeatable process and cleaner handovers.
Common mistakes and prevention
Mistake 1: Skipping context fields (owner, due date, status notes), which makes follow-up harder.
Mistake 2: Treating chat updates as source of truth instead of recording the update in Beech.
Troubleshooting checklist
- 1Troubleshooting step 1
If a control is missing, verify your role has permission for the action.
- 2Troubleshooting step 2
If results look wrong, check filters and refresh to confirm latest synced data.
Full reference: Vault in the user guide
Related guides: Deliverables issuance checklist · Site visits and MOMs · Meeting notes vs site visits