Security and Sharing
Visibility levels, collaborators, link access, enterprise and team scopes, premium content, and policies that control public sharing across Springbase.
Rule of thumb: Default to private. Widen visibility only when you are comfortable with who can read — and what the AI may cite.
Unified Sharing Model
Most shareable assets in Springbase use the same visibility vocabulary:
| Level | Meaning |
|---|---|
| Private | Owner (+ invited collaborators where supported) |
| Unlisted | Anyone with the direct link |
| Public | Discoverable in community/marketplace (where enabled) |
| Enterprise | All members of your organization |
| Team | Members of a specific team |
Not every asset supports every level. See the matrix below.
What Supports Which Visibility
| Asset | Private | Unlisted | Public | Enterprise | Team |
|---|---|---|---|---|---|
| Contexts | ✓ | ✓ | ✓* | ✓ | ✓ |
| Recipes | ✓ | ✓ | ✓* | ✓ | ✓ |
| Meetings | ✓ | — | — | ✓ | ✓ |
| Canvas artifacts | ✓ | ✓ | ✓ | ✓ | ✓ |
| Chats | ✓ | ✓ | ✓ | ✓ | ✓ |
* Public discoverability for community Contexts/Recipes may require platform approval. Treat public as intentionally published content.
Meetings focus on private / enterprise / team — not public community listing.
Share a Context
- Open the Context → Share or Publish.
- Set visibility.
- Optional: invite collaborators (viewer or editor).
- For link-shared Contexts: set link role (view or edit on supported surfaces).
- Source visibility: choose whether viewers see underlying document names on public pages.
Collaborators can help maintain content without making it public.
Share a Recipe
- Recipe card → Share.
- Set visibility and collaborators.
- For premium Recipes: set credit price; prompt may stay hidden until purchase.
- Fork control: allow or block copies.
Recipe link sharing does not grant edit-by-link the same way Contexts might — use collaborator invites for editors.
Share a Meeting
Meeting Share dialog:
- Private — you only
- Enterprise — org members
- Team — selected team
No collaborator email list — scope-based access only. Do not share sensitive recordings wider than policy allows.
Share Canvas Artifacts
From Canvas Share:
- Set visibility, category, tags
- Optional: attach Knowledge Bases / Meetings for viewers (RAG inheritance)
- RAG billing: author pays, viewer pays, or hybrid — affects who spends credits when viewers use AI in the artifact
See Artifacts & Canvas.
Community: Equip vs Publish
| Action | Effect |
|---|---|
| Publish public/unlisted | Others can open your Context or Recipe |
| Equip community Context | Copy read access into your workspace — you don't own the original |
Equip useful public knowledge bases instead of rebuilding from scratch.
Enterprise Controls
Enterprise admins may configure:
| Control | Effect |
|---|---|
restrict_public_sharing | Blocks public/unlisted publishing when enabled |
| Feature policies | Gate agent, automations, meetings, etc. |
| SSO enforce | Requires SSO login for members |
| Data retention | Auto-delete chats, docs, meetings after N days |
Members see Enterprise and Team visibility when they belong to an org. Sensitive internal KBs should use Enterprise or Team, not public links.
Roles (Enterprise Portal)
| Role | Typical access |
|---|---|
| Member | Use shared resources; limited admin |
| Admin | Manage teams, members, some settings |
| Super admin | Full org settings, SSO, policies |
Platform admins (Springbase staff) gate public marketplace visibility separately from enterprise roles.
Best Practices
- Separate Contexts by sensitivity — public marketing vs internal finance never mix.
- Review before unlisted links — URLs can leak; treat like semi-public.
- Premium Recipes — hide prompts when IP matters; price reflects value.
- Meeting recordings — default private; enterprise-only for internal calls.
- Artifacts with RAG — viewers querying your KB spend credits per billing setting.
Premium and Hidden Content
| Feature | Behavior |
|---|---|
| Premium Recipe | Prompt hidden until credit purchase |
| Approved public Recipe | May require admin approval workflow |
| Artifact share + RAG | Viewers may access attached Context snippets per share settings |
Related Guides
- Contexts — ownership and collaborators
- Recipes — premium and fork settings
- Meetings — team sharing
- Integrations — OAuth is per-user
Related docs
Learn how to build living knowledge bases in Springbase with documents, notes, shared access, live sources, community Contexts, and grounded Chat.
Turn reliable prompts into reusable templates with variables, optional Contexts, scheduling, sharing, and Agent mode for connected apps.
Record calls, join Zoom/Teams/Meet links, upload audio, or paste transcripts — then get summaries, action items, search, and Chat integration.
Create documents, dashboards, diagrams, and AI-powered mini-apps in Canvas. Edit, publish share links, export to PDF, and persist data across sessions.
Connect Gmail, Slack, Calendar, GitHub, Notion, HubSpot, and 100+ apps — for Agent mode, Agent Recipes, and Live Data cloud sync.
Learn the core Springbase concepts: Contexts, retrieval, Recipes, Plans, Agents, Canvas, Meetings, permissions, and reusable assets.