Documents
Keep bylaws, minutes, forms, and shared files in an organization folder tree instead of a shared drive that drifts from the roster.
Folders and files
Where: Documents
- Create a folder tree that matches how officers already think about papers (bylaws, minutes, forms, …).
- Upload files into the appropriate folder. Each file must be 25 MB or smaller, and one of: CSV, DOCX, GIF, JPEG, PDF, PNG, PPTX, TXT, WEBP, or XLSX. Contents must match that type — renaming an executable or HTML file is rejected. Download uses the stored type, not the browser-supplied Content-Type.
- Delete a folder when it is no longer needed — the confirm dialog warns if the folder (or its subfolders) still contain documents.
- Prefer organized retention over ad-hoc file deletion when history matters; retention and legal-hold controls (when granted) use
documents.retention.manage.
Creating, editing, and deleting folders needs documents.manage (or Admin). Deleting a folder removes that folder and every subfolder under it, and soft-deletes the documents in that tree.
Folder access
Each folder has an All Members switch:
- On — any member who can open Documents may open the folder
- Off — pick the specific roles that may open the folder; leave the role list empty for Admin only
Nested folders can Inherit From Parent instead. Access follows the parent folder’s current rules (and keeps following if the parent changes). Inheritance is the default when you create a folder under another folder. Top-level folders have no parent, so they do not show the inherit option.
Admins always see every folder.
Storage and platform fees
Document storage counts toward your organization’s platform usage: 25 GB included, then overage on the Platform Fees invoice. See Platform Fees.
See also
- Audit Trail — uploads, deletes, and folder ACL changes are audited
- Members & Access — roles used for folder ACLs