Permission model at a glance
| Dimension | Notes |
|---|---|
| Organization | Department / group, which sets the baseline visibility |
| Role | A set of responsibilities: administrator, auditor, member and so on |
| Directory | Read, write, upload, share and delete rights on a storage node |
| File | An 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
- Configure permissions from coarse to fine: start with the department template, then refine as needed.
- Use "everyone can write" sparingly, especially on folders holding sensitive material.
- Enable a share link policy for outbound scenarios instead of granting download rights directly.
- Review the privilege escalation alerts and long-unused high-privilege accounts once a month.