Client Portal & Files
File Version Control & Revision History
Manage iterative design and document revisions without cluttering your folders with files named "final_v2_really_final.pdf".
Every freelancer has experienced the nightmare of messy file names like `Homepage_Design_Final_v3_revised_FINAL.png`. Flanceflow eliminates this chaos with native File Version Control—stacking new revisions neatly under a single deliverable asset card.
How to upload a new version
- In the project "Files & Deliverables" tab, locate the original deliverable card (e.g., "Landing Page Wireframe").
- Click the three dots on the file card and select "Upload New Version".
- Select the updated file from your computer.
- Add a Changelog Note explaining what changed (e.g., "Adjusted hero typography and lightened background per client feedback").
- Click "Save Version". Flanceflow will increment the version badge to V2, V3, etc.
- Past versions remain accessible in the "Version History" drawer, but the primary link always points to the latest approved file.
Version control lifecycle
| Version badge | Status | What client sees | Rollback capability |
|---|---|---|---|
| V1 (Original) | Superseded | Stored in collapsible version history archive | Can be restored to active with one click. |
| V2 (Latest) | Active / Under Review | Prominently displayed as the current deliverable | Accepts client comments and approval stamps. |
| V3 (Approved) | Final Locked | Marked with green "Client Approved" badge | Locked against further overwriting. |
Revision control tips
- Clear changelogs: Always write a 1-sentence changelog note when uploading a revision to clearly document how you addressed client feedback.
- Restoring older versions: If a client changes their mind and wants V1 back, click "Make V1 Active" to cleanly revert without re-uploading.
- Approval lock: When a client clicks "Approve" in their portal, Flanceflow automatically locks that version and stamps it with the approver’s name and timestamp.
Was this guide helpful?
👍 Yes
👎 No