Document Permissions

Document permissions control who can view and edit each document in your project. They give you more detailed access control than the standard project roles.

Document permissions dialog showing visibility and editing settings

Permission Types

Each document has two independent permission settings:

Permission	Controls	Default
Document Visibility	Who can see the document	Viewers and up
Document Editing	Who can edit the document	Editors and up

Permission Levels

Visibility permissions and editing permissions have these levels:

Level	Description
Viewers and up	All project collaborators have access
Editors and up	Editors, Creators, and Owners
Creators and up	Creators and Owners only
Specific users	Only the users or teams that you select
Nobody	No one except the project Owner

Document Visibility defaults to Viewers and up, and Document Editing defaults to Editors and up. These defaults apply when no explicit permission is set on a document or any of its ancestors.

Identifying Restricted Documents

In the sidebar, a document with restricted permissions shows a lock icon next to its name. Put the pointer on the lock icon to see the tooltip "This page has restricted permissions".

Accessing Restricted Documents

If a user does not have visibility access to a document, the document does not show in that user's sidebar. If the user opens the document from a direct URL, NocoDB shows a "Document Not Found" message. The message includes this note: "This document doesn't exist or you don't have permission to view it."

Document Not Found error when accessing a restricted document

If you believe the document exists, contact the project owner to request access.

Who Can Manage Permissions

Only project Owners and Creators can set document permissions. Editors, Commenters and Viewers cannot change permission settings.

Project Owners always have full access to all documents. Permission settings do not change this.

Availability

Document permissions require the Enterprise plan on Cloud, or an Enterprise license on self-hosted deployments. The Community Edition includes NocoDocs, but not document-level permissions.

Managing Permissions: Set and change permissions on each document.
Permission Inheritance: How child documents get permissions from parent documents.
Actions on Document: Rename, reorder and manage documents.