Skip to main content
All CollectionsRole And Permissions
Project role and permissions
Project role and permissions

Master KiteSuite's Project Roles & Permissions: Safeguard Your Data Integrity!

Gaurav Aery avatar
Written by Gaurav Aery
Updated over a week ago

KiteSuite ensures your data is secure by allowing you to assign specific roles and permissions. This way, you can decide who gets to see and use particular data, maintaining its confidentiality and integrity. These roles and permissions operate differently for projects and workspaces. Let's explore project permissions.

In a project, you'll find four default roles: Owner, Admin, Member, and Viewer. Each role has different permissions. You can edit the permissions of all roles except the Owner.

Owner

The project owner is the person who created the project. Owners have unrestricted access to the entire project. You can't change the project owner's role, but you can modify their workspace-level permissions if they're not the workspace owner.

Admin

Project admins are right below the owner in terms of permissions. They enjoy almost the same level of access as the owner. You can customize their permissions to suit your needs.

Member

Users invited during project creation default to this role. You can modify their permissions.

Viewer

Users with this role can only view items. You can customize their permissions as well.

Project lead

When creating a project, you can select a project lead. The project owner is the person who created the project, while the project lead is the one who manages it. You can change the project lead from among the project members.

For instance, if a user is the project lead and the project owner removes that user from the project, the project owner becomes the default project lead.

Custom role

In addition to the default roles, you can create custom project roles to tailor permissions according to your specific needs. Initially, custom roles have the same permissions as Viewers, but you can customize them. Here's how:

Step 1: Click "Manage Custom Role."

Step 2: Select "Create Custom Role."

Step 3: Enter a role name and hit enter. You can use the same custom role name for both workspace and project custom roles. Remember that permissions work independently.

Step 4: Congratulations, you've successfully created your custom role.

Actions on custom role

You can also edit or delete custom roles. If you delete a custom role assigned to a member, that member's role will automatically revert to the default "Member" role.

Permissions table

Use the table below to check permissions according to each role:

Permissions group name

Owner

Admin

Member

Viewer

Custom role

Manage projects

Yes

No

No

No

No

Manage items

Yes

Yes

Yes

No

No

Manage sprints

Yes

Yes

Yes

No

No

Manage project documents

Yes

Yes

Yes

No

No

Manage lists

Yes

Yes

Yes

No

No

Manage epics

Yes

Yes

Yes

Yes

Yes

Manage fields

Yes

Yes

Yes

No

No

Permissions for epics and sprints are specific to the Scrum template and don't apply to other templates.

Did this answer your question?