Skip to main content

Workspace Management: Roles & Permissions

Updated over 4 months ago

⚠️Custom Roles are available in Business and Enterprise subscriptions

Roles are an important tool that allows you to define what your teammates can and cannot do in your Qase account.

When defining a role, you can specify restrictions down to a very granular level, ensuring that those who need more control have it. In contrast, anybody who should have a limited scope and visibility is properly restricted.

By default, your Qase account comes pre-configured with three Roles already set up:

Owner

An owner of the account, a person that registered the account initially, has full control of the account's features (Including private projects created by other users in the account) and can manage all aspects of the application.

Administrator

An administrative role in the account similar to the Owner.

Member

A common role that grants access to all the basic Qase features;

it is set as the Default role in your new account, which means that any new member that is being invited gets Member role restrictions assigned to them - but you can set a different User Role (except for Owner user role) to be a Default one at any time.

Type of license is always stronger than the role. You can have an administrator role but be a read-only user: you will be read-only first, it will be a stronger setting. Same for the Billing user.

Create a new User Role

You are not limited to the pre-configured User Roles. To create a new User Role, go to "Roles" in Workspace Management, and click "Create a new role":

In the creation menu, fill in the Role Settings:

  • Role Title

  • Role Description

  • Set as default role - Check the box to apply this User Role's settings to any new member joining the workspace.

The next block is dedicated to the Role access rights - this is where you will define which entities and which kinds of actions will be available to users granted this User Role. Each entity can be restricted or allowed, and each action with an entity can be made available or unavailable.

Did this answer your question?