Folders of files organized and shared as a group.
Why it matters. Keeps related work together instead of as loose attachments.
On Borg. Organize files into shared folders your whole team can open, instead of scattered one-off attachments.
A link to a file or folder that can be sent to anyone who needs access.
Why it matters. Avoids re-uploading or re-attaching the same file repeatedly.
On Borg. Share one link to a file or folder instead of re-uploading or re-attaching it every time.
Access boundaries
Covered
Control over who can view, edit, or is blocked from a file or folder.
Why it matters. Keeps sensitive files from spreading further than intended.
On Borg. Set who can view, edit, or is blocked from a file, so sensitive work never spreads too far.
Recover an earlier version of a file after it changes.
Why it matters. Lets you recover from an accidental overwrite without digging up a manual backup.
On Borg. Not built yet — recovering an overwritten file means restoring from a backup until this ships.
Desktop sync client
Planned
A folder on your computer that mirrors files to the cloud automatically.
Why it matters. Lets files work like local folders without manual uploads.
On Borg. Planned, not built — everything runs in the browser today, with no local folder syncing automatically yet.
Pooled team storage
Covered
One storage allowance shared across the whole team instead of per-person caps.
Why it matters. Avoids buying unused storage for people who need less.
On Borg. Storage runs on infrastructure your team controls, so capacity scales with what you run, not a vendor cap.
Some upstream apps gate certain features behind their own licenses; the coverage chips above say where.