User roles & access

Zavimo provides a flexible permission system to help you control access and collaboration at every level—Workspace, Team, and Project.

Workspace roles

There are three workspace roles:

Workspace owner

• Can manage billing and subscriptions
• Can edit and delete the workspace
• Can invite new members
• Can create chat channels

Member

• Can do everything except workspace owner-level actions
• Can collaborate across all workspace content

Guest

• Can be invited only to specific projects
• Cannot access other projects, teams, folders, or workspace-level docs
• Not counted toward seat usage, but limited per plan

Project roles

Project roles define what a user can do within a single project. These roles apply to both individuals and groups (e.g. all workspace members or team members).

• Full-access - Can edit, delete, manage project settings and permissions
• Can edit - Can edit tasks and content but not project settings
• Can comment - Can leave comments but not edit
• Can view - Read-only access

Role inheritance

Projects can inherit roles based on their placement:

• If in a team, roles can be assigned to team members
• If public, roles can be assigned to workspace members
• If users are assigned multiple roles, the most permissive role wins
  Example: “Can comment” from workspace, “Can edit” from team, “Full-access” individually = Full-access

Team roles

Teams have two roles:

• Team owner - Can delete the team, manage members, and lock views/fields
• Team member - Can view and collaborate, but cannot manage team structure

Team & folder permissions

• Docs and views inside a team: editable only by team members
• Docs and views inside the workspace: editable by all workspace members
• Folders follow the same logic as docs