A good shared folder answers three questions: what is included, which file to open first, and what the recipient is allowed to do. Build a delivery copy instead of exposing your whole working directory.
Define the recipient’s task
For a fictional workshop, participants need the brief, a one-page participant handout, and a README explaining them. The complete delivery ZIP supplies exactly those three files for this exercise. They do not need budget drafts, private notes, temporary exports, or your full Downloads folder. Download the sharing checklist and adapt it to the actual task.
Workshop-share/
README.txt
workshop-brief.pdf
participant-handout.pdf
The ZIP extracts to this exact tree. The brief has two pages; the handout has one page and ends with END OF PARTICIPANT HANDOUT. The README names both files. No real workshop is being announced. Compare three files after extraction; source DOCX, personal notes, and working drafts are intentionally outside this delivery copy.
Build and inspect a separate copy
Copy only the intended final files into a new folder. Open each one from that folder and check the title, pages, version, and readability. Examine document comments, tracked changes, hidden sheets, and file properties when the source format can contain them. Do not assume a filename or PDF export automatically removes private information.
Write a README that states the purpose, contents, and any application requirements. Use relative filenames so the instructions make sense after a recipient moves the folder. Do not include a fake contact; use an actual authorized project contact when you make a real delivery.
Check access before sharing
On macOS Tahoe 26, Finder’s Get Info → Sharing & Permissions can help inspect local file access. Those local permissions are not the same as the permissions on a cloud sharing link. Review the actual sharing service’s recipient and access settings separately.
Choose only the access needed for the task. A recipient who only needs to read a PDF does not automatically need edit access to the source folder. Do not broaden access to “anyone” merely to make a test link work.
Test the recipient experience
When authorized, use the service’s recipient preview or an intended recipient account to confirm access. Do not borrow someone else’s login. Check that the recipient can open the first file and any relative links without access to your private folders.
If sending a ZIP, extract it to a new local folder first and confirm the same contents. Include just one obvious top-level folder. If a file depends on a local absolute path, fix the instructions or package the permitted dependency before delivery.
Final check
Compare the delivery folder against the checklist: correct audience, expected file count, no unrelated material, readable contents, clear versions, and appropriate permissions. If any item is uncertain, keep the folder local until you have resolved that specific issue. Sharing a polished folder is a useful check, not a guarantee that the recipient’s software will behave identically.
References & scope
These official references support the software instructions. Practice documents are original, fictional teaching examples; labels can vary by release.
- Change permissions for files, folders, or disks on Mac
Inspect Sharing & Permissions in Get Info; permissions affect access. - Organize files in folders on Mac
Create folders and copy or move files in Finder; cross-disk moves can copy instead.