Skip to Content
DocsAccount & SecurityRoles and Permissions

Roles & Permissions

Roles and Permissions determine what actions users are allowed to perform within Qubase.

Access to workspaces, projects, database schemas, and collaboration features is controlled through assigned roles. Understanding your permissions helps you collaborate effectively while protecting shared resources.


Before you begin

Before managing roles and permissions, ensure that you have:

  • Access to a Workspace or Project
  • The required permissions to manage members (if applicable)

[!NOTE] Available roles and permissions depend on your workspace and project configuration.


What are Roles?

A role is a collection of permissions assigned to a user.

Roles define what actions a user can perform within a Workspace or Project.

Typical responsibilities may include:

  • Managing members
  • Creating projects
  • Editing database schemas
  • Viewing project resources
  • Collaborating with team members

What are Permissions?

Permissions control access to specific actions and resources.

Examples of permissions include:

  • View database schemas
  • Create database schemas
  • Edit database schemas
  • Delete database schemas
  • Manage members
  • Manage projects
  • Access AI Engineering features

Permissions are granted based on the assigned role.


How access works

User Assigned Role Granted Permissions Access Workspace & Project Resources

Permission management

Depending on your assigned role, you may be able to:

  • View resources
  • Create resources
  • Edit resources
  • Delete resources
  • Invite members
  • Manage collaboration settings

Available actions depend on your assigned permissions.


Why roles matter

Roles help teams:

  • Protect important resources
  • Prevent unauthorized changes
  • Organize team responsibilities
  • Improve collaboration
  • Maintain project security

Best practices

  • Assign only the permissions required for each team member.
  • Review assigned roles regularly.
  • Update permissions when responsibilities change.
  • Avoid granting unnecessary administrative access.

[!TIP] Following the principle of least privilege helps keep projects secure and easier to manage.


Last updated on