Files used by several people.
WHAT TO ESTABLISH
A structure everyone understands Who may access what Where things belong
WHAT TO USE FOR ACCESS
Groups, aligned to roles.
WHY NOT INDIVIDUALS
Because individual permissions accumulate and are never removed.
WHAT TO AVOID
Everyone having full access to everything Permissions granted for one request and never reviewed Structures nobody understands
WHAT TO DOCUMENT
The structure, and who has access to what.
WHAT TO REVIEW
Access, periodically, and after anyone changes role or leaves.
WHAT TO MONITOR
Capacity, which grows steadily.
WHAT CONSUMES IT
Media files Duplicates Archives never removed Personal files stored on shared systems
WHAT TO ESTABLISH
Retention rules, and apply them.
WHAT TO PROVIDE
Somewhere for archives, separate from working storage.
WHAT TO BACK UP
All of it, with a tested restore.
WHAT TO CHECK
That the backup includes what people assume it does.