Three user roles and access permissions
Clawuno separates two questions: your role determines what you can do; Workspace access determines where you can do it. Advanced User does not grant every Workspace. Assigning an Agent to a Workspace does not grant its users access there.
Personal installations are normally operated by their administrator. Team and Enterprise installations can assign the following account roles. These are not three subscription editions.
Choose a role
| Role | Intended for | Responsibility |
|---|---|---|
| Admin | People responsible for the installation | Accounts, roles, instance settings, model credentials and all Workspaces |
| Advanced User | People designing workflows and digital colleagues | Create Agents, Works and Workspaces; configure authorized capabilities |
| User | People using prepared business environments | Chat with Agents and Uno, process business files and use existing Mini Apps |
New accounts default to Advanced User: actively choose the appropriate role rather than assuming the default is least privilege. Existing general accounts remain Advanced Users after upgrade; they are not automatically downgraded.
Capability comparison
“Available” still depends on Workspace access, session ownership, Agent state and client capabilities.
| Capability | Admin | Advanced User | User |
|---|---|---|---|
| Enter Workspaces | All | Authorized or owned | Authorized or owned |
| Uno, Agent Chat and group chat | Available | Available | Available |
| Browse, upload, download and supported editing of business files | Available | Available | Available |
| Use existing Mini Apps | Available | Available | Available |
| Work tasks and Git workbench | Available | Available | Not available |
| Create Agents, Workspaces and Mini Apps | Available | Available | Not available |
| Workspace settings, access and Agent assignments | All Workspaces | Owned Workspaces only | Not available, even for an owner |
| Configure Agents and own Uno model/Skill/tool choices | Available | Available | Not available |
| Forge, Anywhere configuration and Dashboard | Available | Available | Not available |
| User settings: language, own browser profiles and password | Available | Available | Available |
| System settings, provider connections/secrets, components and system backup | Available | Not available | Not available |
| Accounts, roles, Team activation and others' password resets | Available | Not available | Not available |
An Advanced User can select an administrator-configured model for an Agent, but cannot add Providers, view credentials or test connections through system settings. A User uses prepared Agents without access to their configuration.
Add or edit a colleague
- As an administrator, open System Settings → Users. Complete remote login and edition activation first when setting up a team; see administrator onboarding.
- For a new user, enter a name, sign-in email and password of at least eight characters, then choose a role. Editing supports name and role changes; email is read-only here. Use the separate password-reset action in the user list.
- Under Workspace permissions, select restricted Workspaces to grant. Workspaces open to all users are automatically available and cannot be revoked for one account here.
- Save after checking the choices. If only part of the save succeeds, resolve the remaining permission changes without creating a duplicate account. Reload and review the rules when concurrent changes cause a conflict.
- Have the colleague sign in with their own account and check the visible Workspaces and controls. An administrator's view does not verify the colleague's experience.
Administrators can access all Workspaces without individual selections. Before downgrading an administrator, check the Workspace access their new role should retain. The last administrator cannot be downgraded. When multiple companies are available, handle permissions separately and save or discard the current draft before switching.
Workspace access rules
An administrator or an owner with configuration capabilities changes these in Workspace settings → Access permissions. Personal edition does not display this tab.
- All users includes everyone in the current company, including future users.
- Selected users admits the selected accounts, that Workspace's owner and administrators.
- Inherit from parent dynamically follows the parent's access rule; it is not a one-time copy.
Top-level Workspaces default to all users. New children default to inheritance. To grant only a child Workspace, give the child an independent selected-users rule. Its audience may be broader or narrower than the parent's. The parent's owner exception does not pass to children, and owning a child does not grant access to its parent.
Inherited entries in user management are read-only and have a follow indicator. Change inheritance in the Workspace settings before granting independent access. A person with child-only access may see a locked parent placeholder that can expand but cannot open the parent's content. Only administrators manage older Workspaces without a reliable owner.
Agent assignment is separate
Choose collaborators in the Workspace's Agents tab, or inspect Workspace assignments from Agent settings. Editing a Workspace's assignments still requires management permission for that Workspace.
Global Agents are available in all existing and future Workspaces and cannot be removed in just one Workspace; change their global scope in Agent settings. New children inherit the parent's additional assignments unless given an independent list. This does not change user access rules.
For example, assigning “Finance assistant” to “Finance” does not let everyone who can use that Agent enter Finance. Grant the colleague Workspace access, then check the Agent is available there.
Troubleshoot access
| Symptom | Check first |
|---|---|
| No System Settings entry | Is the account an administrator? Advanced Users do not have this entry either |
| No Work, Git, Forge or configuration controls | Is the account a User? These are role restrictions |
| A Workspace is missing | Correct Engine, account and current access grant |
| Workspace opens but an Agent is missing | Agent assignment and active state |
| A selection cannot be removed | All-users access, ownership or inheritance; change the source rule |
| Chat is visible but cannot be edited/deleted | Session ownership and running state also apply |
Security boundary
Workspace business files are shared, not restricted to “only edit files I uploaded.” Ordinary Agent Chats follow Workspace sharing rules and should not be treated as private direct messages. Uno is personal but may still read and create shared Workspace content.
Product APIs check roles and access; guessing a URL does not grant management rights. However, Shell, scripts, external MCP and shared Agent memory are not a complete per-Workspace sandbox. An existing live observation connection is not guaranteed to disconnect immediately after revocation. Do not treat these controls as strong isolation against malicious Agents, arbitrary code or a host administrator.
For sensitive work, also control models, external services, host permissions and data scope. See models, credentials and data boundaries.