Sharing & Permissions¶
BotBoss gives every resource one Google-Drive-style share menu — while keeping every organization's data fully isolated. You decide exactly what to share, who can see or change it, and you can take that access back at any time. Every share is permissioned, revocable, and audited.
What you can do¶
You can share the things you create and own, including:
- Files and folders — sharing a folder cascades to everything inside it.
- Data tables, databases, and saved views — open up the data your team needs.
- Dashboards — share live, read-only views of your metrics.
- Skills — reuse and distribute the playbooks you've built.
- Artifacts — share generated documents, charts, and other outputs.
- Agents — let teammates see and message an agent, or manage it.
- Saved task and work-item views — share the lenses you've set up for tracking work.
The share menu is the same everywhere, so once you've shared one thing you know how to share them all.
Who you can share with¶
For each share, you pick who gets access:
- Anyone in the workspace — everyone in your organization can find and open the resource.
- Specific people or agents — grant access to named teammates or AI agents only.
Agents are permissioned exactly like people, so an agent only ever acts on what it has been given. When an agent proposes a share, a person confirms it first.
Access levels¶
Every share grants one of three roles — the same words you know from Google Drive:
| Role | What they can do |
|---|---|
| Viewer | View and use the resource (read-only). |
| Editor | View and edit the resource. |
| Manager | Edit and re-share — change who else has access. |
Some surfaces — like dashboards and saved views — are read-only for recipients by design. You can revoke any share at any time, and access is cut immediately.
Visibility: Private vs. shared with the org¶
Resources that support visibility (files, folders, tables, databases, and saved views) carry a simple toggle:
- Private — only you (and workspace admins) plus the people, agents, or folders you've explicitly granted.
- Everyone in the workspace — anyone in your organization can read it.
For folders, the visibility you set cascades to everything inside — a private folder keeps its contents private, and a folder shared with the org makes its files org-readable. A file can also be made org-readable on its own with the per-file Private ↔ Everyone toggle.
Shareable links¶
For dashboards, you can mint an unlisted link so people outside your organization can view it read-only. External links always carry an expiry (and can be revoked early). Dashboards built on sensitive data require you to explicitly acknowledge before an external link can be created.
How permissions work¶
The core rule is simple: you can only share what you can already access. Sharing never grants more than you hold — it widens access within your own bounds, never beyond them.
- To share a resource you need write access to it; to re-share it (grant access to others) you need the Manager role on it.
- Recipients only get the role you grant — Viewer, Editor, or Manager — never more.
- Agents are permissioned the same way; when an agent proposes a share, a person confirms it first.
Example. You build a "Q3 Revenue" dashboard. You share it as Viewer with your whole organization so everyone sees it live, and grant your analyst Editor access to keep it updated. Later the analyst changes roles — you revoke their access in one click and they immediately lose it, while everyone else keeps the read-only view.