English
Collaboration and Permission Boundaries
Current permission model and collaboration scope
Collaboration and Permission Boundaries
Current Permission Model
- Project roles:
owner,manager,editor, andviewer - Access checks are enforced by project membership
Current Status
- Project-level multi-member collaboration is available (
owner/manager/editor/viewer) - System-level user administration is available (
admin/user,active/disabled)
What to Check First
If you see a permission error, confirm your account is a member of the project.
Role Capabilities (Current)
owner: full control of the project, including member management, settings, and destructive operations such as project deletionmanager: can manage project members, project settings, project memory/environment, installed assets, and start or stop the project container when container support is enabled, but cannot perform owner-only actionseditor: can use project conversations, files, agents, and tasks, but cannot manage members or project-wide settingsviewer: read-only access to project content, conversations, files, and results; cannot chat, edit files, run agents, or manage settingsadmin(system-level): can manage user roles and account status in User Management