Decide whether the other person needs a copy or access
Sending a copy gives someone a separate file. Sharing an iCloud Drive item gives them access to an item you continue to manage, subject to the permissions you choose. Those are different relationships. A finished itinerary sent to a friend may need only a copy; a folder where two people assemble trip documents may benefit from ongoing shared access.
Use this workflow for files you own in iCloud Drive and are permitted to share. A local On My iPhone folder or a third-party provider is not automatically an iCloud shared folder. Confirm the location in Files before looking for collaboration controls. Account requirements, app support and access options can differ by sharing method, so use the options actually shown for that item.
Make a small folder with a clear boundary
Create a folder dedicated to the shared task, such as Weekend trip planning. Put only the necessary documents inside. Do not share your entire Documents folder because it already contains the itinerary. A narrowly scoped folder is easier for both the owner and participants to understand, and it reduces the chance that a later unrelated file becomes visible by accident.
For the example, include a draft itinerary and a transport reference. Keep identity documents, private payment records and unrelated bookings elsewhere unless there is a specific agreed need to share them. A folder's name does not enforce confidentiality; its contents and permissions determine what others can access.
Set access before sending the invitation
In Files, locate the iCloud Drive folder, touch and hold it and choose Share. Select the collaboration option rather than Send Copy when the share sheet offers that choice. Inspect who can access it and whether they can make changes or only view. For a small named group, choose invited people rather than a broadly reusable link when that matches the available options.
On iCloud.com, the folder's Share controls similarly let the owner choose invited people or anyone with the link, then choose the access level and create the link. These browser controls can be useful when you want a larger view of the settings. Do not use an Anyone link merely because copying it is convenient; anyone who obtains that link may gain the access you granted.
| Intended use | Starting permission | Practical consequence |
|---|---|---|
| Two people actively assembling documents | Named participants with changes allowed | Participants can affect the shared work |
| Family members reading a finished plan | View-only access | Changes remain with the owner or designated editors |
| A one-time final attachment | Send a copy | Later edits to the original do not update that copy |
| Publicly distributable reference material | A link only if broad access is intended | Forwarding the link can extend its audience |
Test with the participant's perspective
Send the invitation through an agreed channel and ask the participant to open it using the intended account. Have them read one harmless test document. If editing is intended, ask them to make a small agreed change and confirm it appears for the owner. This checks both access and the actual collaboration behavior before the folder fills with important work.
If they can view but not edit, inspect permissions before asking them to reinstall an app. If they see an access request, check the invited identity and account in use. If the file opens as a separate downloaded copy, confirm that they followed the collaboration link rather than an attachment you sent earlier. These are different problems despite looking like “sharing does not work.”
Understand the shared folder's reach
Items placed inside the shared folder participate in its shared boundary. Think before moving a private document into it. Shared-folder permissions also affect how individual items can be shared; do not assume a nested file can freely have an unrelated audience. If one document needs a different group, a separate folder or separately shared item may be clearer.
Editing rights are consequential. Participants can change shared material, so agree on simple working rules such as who maintains the itinerary and where drafts belong. Do not describe a shared workspace as a backup: a mistake in the shared item can affect everyone using it. Keep an appropriate independent copy of a milestone when the project needs one.
End access deliberately
When the trip or project ends, review the folder's sharing controls. The owner can manage participants, adjust access or stop sharing. Tell collaborators before closing access if they still need a permitted final copy. Removing access does not recall copies someone already downloaded or information they already read.
Keep the final agreed document distinct from the working drafts. A folder named Archive does not itself change permissions; verify those settings directly. The Files location guide helps distinguish local, cloud and recent views, while the backup explanation explains why shared synchronization is not an independent recovery plan.
Sources & further reading
Apple’s documentation supports the feature details. The scenarios and decision sequences above are CJVV’s editorial guidance.