Shared Folder Permissions for a Small Team
Set a small team's shared folder so people can read the record without everyone being able to delete it.
A shared folder is how a small team stops emailing attachments back and forth. It is also how one tired person deletes a year of minutes, because the folder was shared with the same full powers for everyone. Permissions are the quiet half of preservation. They decide who can add, who can edit, and who can destroy. You do not need an elaborate system. You need the finished record to be harder to damage than the inbox.
Give the archive a named owner
Someone should be allowed to reorganize, restore, and change who has access. Two or three owners is safer than one, so a vacation does not freeze the team, and a crowd of owners is the same as no owner. Write the names by role if roles are stable: the secretary and the treasurer, for example. Everyone else can be a contributor or a reader. A contributor can add files. A reader can open them. Neither needs the right to empty the folder. The owner is not a status prize. It is the person who will answer when something important disappears.
Split the writable area from the finished area
Create an inbox the whole working group can add to, and a finished area for files you have accepted as the record. Move files from the inbox into the finished area when they are named and, if you keep versions straight, marked as the ones to trust. In the finished area, most people should be able to read and not delete. This matches the spirit of what read-only means, enforced by the shared folder rather than by a promise. If your tool cannot do fine-grained rights, use a practical substitute: the finished copy lives in a place only the owners can change, and everyone else gets a viewing copy. A viewing copy that people edit will drift. Say which location is the record.
Do not share the account instead of the folder
Passing around one login feels simple and removes every boundary. You cannot tell who deleted a file, you cannot remove one person without changing the password for everyone, and a leaked password is a leaked archive. Give each person their own access, even if the group is four people. When someone leaves, remove their access the same week and confirm they cannot open the folder. Keep a note of who has access. It belongs beside the retention habits in a note for a hobby club if the team is a club, because what you keep and who can destroy it are one policy.
Test the boundary with a harmless file
Before you announce the folder, put a sample file in the finished area and ask a non-owner to delete it or overwrite it. You want them to fail. Then ask them to add a file to the inbox. You want them to succeed. Testing on a real minutes file is a bad way to learn that the settings were wider than you thought. If the test shows everyone can delete, tighten the setting and test again. Also open the folder from a second computer to be sure the rights followed the person, not the machine you used to set them up.
Permissions do not replace a spare copy
A perfectly limited folder still lives in one service or one computer until you copy it somewhere else. An owner can still make a mistake, and a service can still close. Permissions reduce accidents inside the team. A spare reduces disasters outside the team's control. Once a month, an owner should confirm the spare exists and that new finished files made it into the finished area rather than lingering in the inbox under draft names. Access rules keep the record stable. The copy keeps it alive if the shared place itself goes away.
Frequently asked questions
What if the software only offers full access or none? Use it for the inbox if you must, and keep the finished record in a place with a real owner and a spare copy. Do not accept that every helper must be able to delete the minutes.
Should volunteers be able to edit a shared document live? Live editing fits drafts. For the accepted record, save a dated copy into the finished area after the meeting so a later edit does not silently rewrite what was agreed.
How many owners are too many? If you cannot say who would notice a deleted folder, you have too many, or too few. Two or three people who actually look is a sound household and club scale.
Steps
- Name an owner: Decide who may change the structure of the archive folder and who may only add or read.
- Separate incoming from finished: Give the team a writable inbox and a finished area that is harder to edit.
- Test with a second person: Have a teammate try to delete a sample file in the finished area and confirm they cannot.
- Write the rule down: Put the permission choices in the folder note so the next volunteer inherits the reason.