Workspaces and team access
Workspaces are the core sharing boundary in OpenDocs.
What a workspace does
When you complete onboarding, OpenDocs associates you with a workspace. That workspace becomes the primary scope for:
- workspace-visible documents
- team membership
- invitations
- visibility defaults and policies
Workspace visibility
If a post is workspace visible, active workspace members can read it.
That makes it the best default for:
- architecture docs
- rollout notes
- specs
- runbooks
- AI-generated drafts that should stay internal
Team workflows
OpenDocs supports team and invitation flows in the dashboard. At a product level, that means you can:
- add teammates
- manage roles
- invite collaborators
- keep internal documents visible to the right people
Domain-restricted collaboration
The workspace model also includes domain controls for organizations that want tighter boundaries around who should be allowed into the workspace.
The current public docs focus on the simpler and most common workflow:
- private for me
- workspace for my team
- public for anyone with the link
Best practice
If you are using OpenDocs with agents, keep the agent default at workspace
unless you explicitly want an outward-facing URL.