
Frame.io V4 can share a restricted folder for review without removing its restrictions, but the documented Share includes only one restricted-folder level. Subfolders inside that restricted folder are not included. A client can therefore receive the main film while missing the nested crop exports or caption files.
Key Takeaways
- Restricted folders have a specific sharing-depth rule in V4.
- Missing nested files do not justify making the whole project unrestricted.
- Verify every agreed deliverable through the actual recipient's route.
Diagnose the package boundary before permissions
The restricted-folder documentation explicitly distinguishes safe sharing of restricted content from removing a folder's restrictions. It warns that subfolders inside a restricted folder are not shared through that folder's Share link.
First locate the exact missing item. Is it directly in the shared restricted folder, or inside a child folder? Then confirm which Share the recipient opened. An owner's ability to browse the entire project does not prove the link contains all those objects.
General advice about ordinary shared folders retaining their structure should not replace this restricted-folder exception. Treat the actual container type as part of the diagnosis.
Build a deliverable inventory with locations
For a proposed wedding-film delivery, the top restricted folder contains the landscape master while child folders hold the vertical teaser and subtitles. The package may look complete in the editor's project tree but be incomplete through its Share.
| Required item | Record before sending | Recipient check |
|---|---|---|
| Main film | Exact revision and direct location | Correct picture and sound play |
| Alternate crop | Its own asset and folder path | The intended crop is accessible |
| Captions | Language, file and matching cut | The required text can be obtained or selected |
Keep this list connected to an approved-version record. The list documents the intended package; it does not itself grant access.
Choose an authorized sharing arrangement
Use supported sharing controls to include the required assets or separately share the necessary restricted level. Frame.io documents sharing an asset inside a restricted folder as well as sharing the folder. Follow the warning shown for restricted content and confirm that every selected item is appropriate for the recipient.
Do not turn off Make Restricted as a quick experiment. The guide says doing so returns access to all project members. That is broader than repairing one customer's missing subtitle file. If you lack sharing authority, ask the responsible project member to configure the intended route.
Check recent changes too. Frame.io says content that becomes restricted while actively shared is immediately removed from existing Share links. An old link may therefore become incomplete after a privacy change, even though no upload failed.
Verify completeness without widening the audience
Open the final destination in a recipient-appropriate session and check each listed asset. Confirm download access only where delivery requires it, and use the review-versus-master guidance to label the file's purpose.
For sensitive footage, preserve the audience decisions described in the private wedding-film and public-teaser guide. Accept when the recipient can access the complete agreed package and unrelated restricted content remains outside it.
Related tasks
- Should I Send a Review Copy or the Final Master of an AI Video to a Client?
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
- How to Make a Public Wedding Teaser From a Private AI Film
Sources and scope
- Frame.io: Creating Folders and Restricted Folders: V4 restricted folders can be shared without removing restrictions. Only one restricted folder level can be shared at a time; subfolders inside a restricted folder are not included in its Share link. Making actively shared content restricted removes it from existing Shares.
Based on the full official restricted-folder source captured October 29, 2026. No permissions, folders or live shares were changed. The delivery inventory and recipient verification procedure are proposed. General folder recursion must not override the documented restricted-folder exception.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.