Shared Folder Permissions
A four-person design team shares one Windows PC. Each person has a separate standard (non-administrator) user account. They keep project files in C:\Projects, a folder on the shared drive. Last week a teammate accidentally overwrote the final logo file, so the team lead wants to prevent that happening again. His plan: give everyone Administrator rights 'so they can fix things themselves', and set C:\Projects to read-only for all users. A designer points out she still needs to save new versions of files daily.
1. Explain why making all four users administrators is a poor solution to the overwrite problem.
Read the worked answer
Administrator rights grant the ability to change system settings, install software, and modify any file on the machine - they do not prevent accidental overwrites of project files. In fact they widen the blast radius: any mistake can now damage the OS or other users' data, and malware run under an admin account does far more harm.
The overwrite problem is a file permission and versioning problem, not a privilege problem. The correct responses are:
- Restrict write access on the shared folder to the people who need it, or
- Use versioning / keep dated copies so an overwrite is recoverable, and
- Keep day-to-day accounts as standard users, elevating only when genuinely needed.
Giving everyone admin rights solves nothing and creates new risk.
2. The lead's second idea - making C:\Projects read-only for everyone - conflicts with a stated requirement. Identify the conflict and propose a workable permission arrangement.
Read the worked answer
Conflict: the designer needs to save new versions of files daily. A folder that is read-only for all users blocks exactly that - she could open files but not save changes. The 'fix' would stop the team working.
Workable arrangement:
- Keep C:\Projects writable for the team members who need to save work (grant Modify rather than Full Control, so they cannot change permissions themselves).
- Address the overwrite risk with versioning or dated filenames (e.g. logo_v1, logo_v2, logo_final_2024-05-01) and, where available, File History or a backup so a previous version can be restored.
- Optionally make the final approved files read-only individually, rather than the whole folder - that protects finished work without blocking new saves.
- Keep accounts as standard users; the team lead retains admin for system changes.
This satisfies both goals: daily saving continues, and an accidental overwrite is recoverable.