LobeHub
LobeHub

Private & Workspace Resources

Cloud

This feature is available only in LobeHub Cloud

Every content resource in a workspace carries one of two visibility tiers:

  • Private: visible and usable only by its creator;
  • Workspace: visible to workspace members, with member permissions refining what they can do.

The app's sidebars and list pages split content into Private / Workspace sections, and private items usually carry a lock icon.

Supported resource types and defaults

Resource typeDefault visibility when created in a workspace
AgentFollows the creation entry — "+" in the Private section creates private, "+" in the Workspace section creates shared
Agent group / session groupWorkspace
Page / documentFollows its section — the Private / Workspace lists each create into their own scope
TaskPrivate (switchable in the create dialog, shown as a visibility tag)
File / resource libraryFollows the scope you upload into
Image / video generation sessionsWorkspace
DevicePrivate — sharing a machine with the workspace is an explicit opt-in

Topics (conversations) have no visibility switch of their own: they follow their agent. Once an agent is shared with the workspace, members can see each other's topics under it and collaborate; topics under someone's private agent are simply unreachable. "Share topic" links (/share/t/…) are external, read-only publishing — a different thing from workspace collaboration.

Publishing and revoking

Switch from the item's context / more menu:

  • Publish to workspace: private → workspace; members gain access at the configured level;
  • Make private: workspace → private; the share is revoked.

Both directions open a confirmation dialog listing the consequences before taking effect.

What happens when you revoke (make private)

  • Other members lose access immediately; views they have open become inaccessible;
  • Existing message attachments and references show as "no longer available";
  • Content members have already loaded can't be recalled (irreversible).

One-way switches and special cases

  • Files / resource libraries and session groups can't go back to private once published; pages, agents, and tasks switch both ways;
  • Publishing a task keeps its historical runs private — only runs created after publishing are visible to members;
  • When a resource changes scope, it's automatically moved out of groups that no longer match.

The private boundary: not even the Owner can cross it

Private is a hard boundary, not a "collapsed by default":

  • Private resources are visible and manageable only by their creator — Owner / Admin powers don't penetrate: no viewing, no visibility change, no transfer;
  • Other members can't even probe whether a private resource exists (direct access returns "not found");
  • Workspace-shared agents can't read the caller's private content during execution either.

Only the creator can switch a resource's visibility. For asset handovers, have the creator publish first, or use the asset migration tools in General Settings (shared resources only).

Visibility vs. member permissions

They're two independent layers:

  • Visibility decides who can see it: private or workspace;
  • Member permissions (General Access) decide what members may do once shared: view / use / edit;
  • Permissions can be pre-configured on a private resource, but they only take effect after publishing.
  • Devices: the same private / workspace visibility, just defaulting to private — see Devices;
  • Credentials / connectors: use personal / workspace scope tabs with a sharing switch — an independent scoping model, not the visibility switch — see AI Configuration.

Next steps