Member Permissions (General Access)
Cloud
This feature is available only in LobeHub Cloud
Once a resource is published to the workspace, its creator can use Member Permissions in the item menu to set the access level — what workspace members may do with this resource. Access levels are configurable on agents, agent groups, and documents.
Access levels
| Resource type | Available levels | Default |
|---|---|---|
| Agent | View / Use / Edit | Use |
| Agent group | View / Use / Edit | Use |
| Document | View / Edit | View |
What each level means:
- View: browse the resource's content and configuration without using or modifying it;
- Use: chat with the agent or use the resource in workflows, without changing its configuration;
- Edit: collaboratively edit the resource's content and configuration — but not ownership: visibility switching and permission management stay with the creator.
The creator and workspace Owner always keep full access regardless of the configured level. Permissions can be pre-configured while a resource is still private, with a note that they take effect after publishing.
Stacking with visibility and roles
Three layers converge — the strictest wins:
- Visibility: private resources are entirely invisible to members; member permissions don't apply;
- Workspace roles: a member's baseline abilities — Viewers are read-only workspace-wide, so even a resource opened up as "Edit" can't be edited by a Viewer, nor can they trigger credit-spending actions;
- Member permissions: what a member may do with the specific resource.
Other sharing shapes
- Skills & connectors: shared with the workspace on install — everyone can browse and use them; editing / removal is creator-only (the Owner manages all) — see AI Configuration;
- Topic collaboration: topics under a shared agent are open to members who can access that agent, with collaboration and comments — controlled indirectly by the agent's visibility and level; topics have no permission switch of their own.