Sharing & backup
Studio itself has no per-collection "invite a teammate" UI, and no zip export button lives on the collections page kebab menu alone — both of those live one level down, in the collection's own management surfaces. This page covers both.
Share it: Explorer, not Studio
Access is granted from Explorer (/explorer), the read/browse-
and-edit companion app. From there, a collection owner grants access at one of three levels:
| Role | Can do |
|---|---|
| Viewer | Browse, search, view items. Read-only. |
| Editor | Add/edit items, upload files. Cannot touch schema or access. |
| Owner | Everything, including schema and access management. |
If the collection belongs to an Organization (created from
/account.html → "+ New organization"), org membership (View / Edit / Admin)
grants matching collection access automatically to every collection under that org — no
per-collection invite needed unless you want to override someone's level on one specific
collection.
Backup, import, and merge
Collection Settings (kebab menu next to the collection name in the sidebar, or the card menu on the Collections page) → Manage:
- Download zip — full backup: every file, schemas, assets.
- Import zip — into an empty collection (or one with zero filename conflicts).
- Merge zip… — into an already-populated collection; a 3-step wizard lets you map each incoming type and file to something existing or brand-new, skips duplicate-named nodes rather than overwriting.