Kitchen allows you to control access to resources in detail, so you can decide who has visibility and what level of interaction they have.
Below is an overview of the available access levels and roles across different resources. The right role depends on how much access you want to give to a specific user.
General Access Levels
Each resource in Kitchen can have one of the following access levels:
Private
Only visible to you and explicitly invited team members.
βShared with Clients
Accessible to invited clients and team members.
βInternal
Visible to all team members in your workspace without explicit invitation.
Important Notes
Setting the General Access does not automatically give users access to a resource (except for the Internal level). To give someone access, you need to invite them using the Share button within the resource.
Access Inheritance
If a folder is set to a specific General Access and already shared with certain users, any new resources created inside that folder with the same access level will automatically inherit those users.
User Permissions for Resources
Within each resource, users can be assigned different roles that define their level of interaction. In general, team members can be assigned a broader range of roles and permissions than clients.
Below is a breakdown of roles by resource type, listed in increasing order of permissions.
Folders
For folders you share, users can be assigned the following roles:
Clients
Viewer
Read-only access and ability to download files.
Commenter
Can view, download, and leave comments (for example, feedback on files).
Uploader
All of the above, plus the ability to upload and manage their own files in the folder.
Creator
All of the above, plus the ability to create and manage their own folders.
Team Members
Team members can also have the roles above, and additionally:
Manager
All of the above, plus the ability to invite users and manage access.
Admin
Full access.
Boards
For boards, you can assign the following roles to users:
Clients
Viewer
Can view the board and tasks, download files from them, and complete assigned tasks.
Commenter
All Viewer permissions, plus the ability to comment on tasks.
Creator
All of the above, plus the ability to create and manage their own tasks in existing lists.
If a client is not assigned as a member of a task created by someone else, they cannot complete or modify that task. They can only comment on it or attach files.
They also cannot delete tasks they did not create.
Full Creator
All of the above, plus the ability to manage all tasks, regardless of who created them.
Team Members
Team members can also have the roles above, and additionally:
Editor
All of the above, plus the ability to manage lists, custom fields, and labels.
Manager
All lower-level permissions, plus the ability to invite users and manage access.
Admin
Full access.
Conversations
When creating a conversation to communicate with clients or team members, you can assign the following roles:
Clients
Viewer
Read-only access and the ability to download files sent through messages.
Commenter
Can view and send messages, and download files.
Team Members
In addition to Viewer and Commenter, team members can also have:
Manager
All lower-level permissions, plus the ability to invite users and manage access.
Admin
Full access.
Documents
For native Kitchen documents, you can assign the following roles:
Clients
Viewer
Read-only access.
Editor
Can edit content.
Team Members
Team members can have the roles above, as well as:
Manager
Can invite users and manage access.
Admin
Full access.
Embeds, Milestones, Invoices, Quotes, and Proposals
For these resource types:
Clients can only be assigned the Viewer role
Team members can be assigned as Viewer, Manager, or Admin
Note
For embeds that support editing (such as Google Docs or Google Sheets), access and editing permissions depend on the settings of the original file in the external platform.
Still need assistance? Contact support.
