How to Update a Shared File Collection
Replace one item in a shared collection while checking linked copies, navigation, access, and version notices.
On this page (8 sections)▼
Updating one file in a shared collection can affect several links, folders, or client packs. Map where the file is used before replacing it, then verify every affected recipient path.
This guide focuses on collection-wide consequences. The individual file's replacement button is only one part of the update.
1. Map the file's dependencies
Identify whether several collections reference the same underlying file or contain independent uploaded copies. The distinction changes what an update will do.
| Relationship | Possible effect | What to verify |
|---|---|---|
| Shared reference to one file | Several collections may update together | Every affected pack |
| Independent uploaded copy | Other copies may remain unchanged | Which copies need replacement |
| External file URL | Host's update rules apply | External link and access |
| Downloaded recipient copy | Saved copy remains separate | Change notification is needed |
Do not infer the dependency model from identical filenames. Confirm how the platform stores and references the resources.
2. Decide whether the change belongs everywhere
A generic product guide may be appropriate to update across all packs. A client-specific proposal may not be. Check the audience and purpose before replacing a shared resource.
Record:
- The file and current revision.
- Every known collection or link using it.
- The proposed revision and reason.
- Approvals or signatures associated with the old copy.
- Whether every recipient should receive the change.
If only one client needs the revision, create the appropriate distinct resource rather than changing a shared file blindly.
3. Check replacement and publishing constraints
SendNow's replacement help says linked resources referring to a file switch to its new version and identifies eligibility, same-format, and signed-NDA restrictions. SendNow: Replace a shared file Check the current workflow before acting.
For microsites, distinguish content updates from changing the entry address. Its sharing help warns that an already-shared custom slug change can break the old URL. SendNow: Share and embed a MicroSite
Keep the original recipient addresses in your update record. Do not repair a file and accidentally create a new navigation problem at the collection entrance.
4. Apply the approved revision
Keep local copies of the relevant versions. Review the replacement for content, format, and dependencies before saving it.
When using a shared reference, apply the update once through the supported workflow, then inspect affected collections. When using separate copies, update each required resource deliberately and record completion.
Do not assume deleting and re-uploading is equivalent to replacement. It may change identifiers, break links, or discard associations. If the original must be preserved, issue a new version with a clear explanation instead.
5. Test every affected collection
Use the dependency list as a test checklist. Open each intended recipient URL in a fresh authorized session.
| Check | Expected result |
|---|---|
| Entry URL | Still reaches the collection |
| File title and position | Remain understandable |
| Visible revision | Matches the approved update |
| Access policy | Still fits each audience |
| Download, if offered | Supplies the correct revision |
| Other files | Are not changed unintentionally |
If one collection should retain the old version, verify it explicitly. A successful test on one client pack is not evidence about all the others.
6. Notify readers and preserve context
Explain material changes with the file title, revision, and practical consequence:
The implementation guide has been updated in the shared pack. Revision 3 changes the setup sequence. Please use the current link when following the instructions.
Keep the manifest and any approval record synchronized with the update. If readers may have downloaded the older copy, ask them to use the new one.
For analytics comparisons, preserve revision dates and scope. Old page activity can refer to different content if the document was reordered.
Frequently asked questions
Will every linked microsite update?
That depends on whether they reference the same underlying file. SendNow documents shared-file replacement effects; verify the actual dependencies before updating.
What if the original already has an NDA signature?
SendNow documents a replacement restriction after signing. Preserve the original and use the supported new-document process.
Can I change the collection's slug while updating?
Check the provider's behavior first. SendNow warns that changing an already-shared custom slug can break the original address.
Before you share
Update the resource and its surrounding relationships as one task. A revision is complete only after affected collections, permissions, manifests, and readers are accounted for.
Related articles
Sources and editorial disclosure
Primary documentation reviewed October 11, 2026. Product settings and entitlements can change; use the linked help for current details.
VDR Directory is published by the SendNow team. SendNow is included where relevant to the task. This guide is based on public documentation and editorial recommendations, not a claim that a signed-in product demonstration was performed. Stock photos illustrate the topic; they do not show the described product interface or prove feature behavior. Examples and verification checklists are illustrative unless explicitly stated otherwise.
Related Guides & Research
Recommended next reading for deal teams and transaction leaders.
Why Your Recipient Can't Open a File
Diagnose account, invitation, access, expiry, and preview problems without weakening confidentiality settings.
How to Revoke Shared File Access
Disable intended online access and understand the limits for ordinary downloaded or copied files.
How to Update a Shared PDF
Replace an outdated PDF while checking link continuity, recipient access, and version-specific analytics.