Skip to main content

Setting up document's security policies

If you have the Security permission in a document, you can access the Security tab of the details panel.

Document's security
 

Here you can see a grid in which you can grant / revoke permissions to groups and users.

To grant / revoke a single permission, just check / uncheck the corresponding checkbox.

To add a new security entity use Add Group or Add User list boxes, while to drop an element right-click on the name and press Delete or just revoke the Read permission.

If you want to make your changes persistent in the current folder, you have to press the Apply Rights button.

Complete list of Permissions

PermissionApplicable ResourcesActions Allowed on Resources
Readallaccessing and using
Previewdocumentdisplaying in the interface
Printdocumentprinting
Downloaddocument, folderextracting from the platform
Emaildocumentincluding the resource in an email
Writeallediting
Addfolderadding new elements inside
Securitydocument, foldermanaging security policies
Immutabledocumentenabling immutability
Passworddocumentprotecting with a password
Deletealllogically removing
Movedocument, foldermoving into another location
Renamedocument, foldermodifying the name
Custom IDdocumentediting the Custom ID
Revisiondocumentediting the Revision
Importfolderimporting from .zip archives or other source
Exportfolderexporting to .zip archive or other target
Signdocumentdigitally signing
Archivedocument, folderarchiving or inserting into an export archive
Workflowdocumentlaunchin a new workflow instance
Calendardocumentcreating a calendar event
Subscriptiondocument, foldersubscribing other users to the issued alerts
Automationdocument, folderinvoking an automation routine
Reading requestdocumentsending a reading request
Storefolderchanging the default store

Admins can do everything

The users in the admin group always have full permissions on all the resources.

Inherit security policies from the folder

If you do not specify any security policy at document level, the system will use by default the parent folder's policies. If you specify security policies at document level, then they completely overwrite those specified in folder.