Permission policy guide

From the permission model to ready-made templates: covering common management scenarios with four-dimensional authorization.

Permission model at a glance

DimensionNotes
OrganizationDepartment / group, which sets the baseline visibility
RoleA set of responsibilities: administrator, auditor, member and so on
DirectoryRead, write, upload, share and delete rights on a storage node
FileAn exception grant on a single file, with automatic expiry

Three recommended templates

  • Department isolation: one root folder per department; members can read and write their own department only, and cross-department access is invisible by default.
  • Project collaboration: project spaces grant access per member, and permissions are reclaimed automatically when the project ends.
  • Read-only publishing: the standard documents folder is read-only for everyone and writable by administrators only.

Practical advice

  1. Configure permissions from coarse to fine: start with the department template, then refine as needed.
  2. Use "everyone can write" sparingly, especially on folders holding sensitive material.
  3. Enable a share link policy for outbound scenarios instead of granting download rights directly.
  4. Review the privilege escalation alerts and long-unused high-privilege accounts once a month.
Copy a link to this page