osFoundry / Platform
Sharing
Share any surface with a link or with specific people. Granular per-resource permissions.
What it is
Sharing in osFoundry lets you take any surface in your workspace — a chat or agent, an app, a code repository, a knowledge base, or a dataset — and give someone else access to it. You choose how: hand out a link that anyone with it can open, or grant access to specific people you name. Because osFoundry keeps chat, agents, apps, code, knowledge, and data in one workspace, the same sharing model applies everywhere, so you don't relearn a different flow for each kind of thing you want to hand off.
Access is set per resource, not per seat. Each surface carries its own permissions, so you decide independently what one person can do with a given repo versus what another can do with a dataset. That granularity means a link you share for a read-only app doesn't quietly widen access to the agent or knowledge base behind it — each resource is its own boundary. Because osFoundry is a bring-your-own-key desktop workspace with no per-seat fees, you're deciding who can reach a specific surface rather than paying to add named seats before anyone can collaborate.
This matters most when a workspace holds a mix of sensitive and shareable work. osFoundry is local-first, so data can stay on your device by default; sharing is the deliberate act of opening one surface to someone else, on the terms you set, rather than the default state. You get a single, consistent way to collaborate — a link when speed matters, named people when control matters, and per-resource permissions so each share says exactly what it should.
Key capabilities
- Share any surface — chat, agent, app, code repository, knowledge base, or dataset — from one consistent flow
- Choose link sharing for anyone with the URL, or grant access to specific named people
- Set permissions per resource, so each surface has its own access boundary
- Sharing one surface never implicitly widens access to the agents, data, or repos behind it
- No per-seat fees: you control who reaches a specific surface, not how many seats you've bought
Use cases
- Developer: shares a single code repository with a contractor by link, while the rest of the workspace stays private on their device
- Team lead: grants two named reviewers access to one app surface without opening the agents or datasets it depends on
- Analyst: sends a dataset to a specific colleague with per-resource permissions instead of exporting a copy out of the workspace
Frequently asked questions
What can I share in osFoundry?
Any surface in your workspace — a chat or agent, an app, a code repository, a knowledge base, or a dataset. The same link-or-people model applies to each, so sharing works the same way across chat, apps, code, knowledge, and data.
What's the difference between sharing a link and sharing with specific people?
A link opens the surface to anyone who has it, which is fastest when you just need someone in. Sharing with specific people grants access only to the individuals you name, which is what you want when the surface is sensitive or you need to control exactly who's in.
If I share one thing, does the person see my whole workspace?
No. Permissions are set per resource, so sharing one surface grants access to that surface only. osFoundry is local-first, so everything else can stay private on your device — sharing is a deliberate act on a single resource, not a switch that opens the workspace.