Skip to main content

Track the full history of your attachments — without losing anything along the way

Every new version of an attachment is now saved in Gino, complete with its history. You maintain a clear record of exchanges, feedback, and updates throughout the entire negotiation cycle.

Until now, attachments did not benefit from the same level of tracking as versioned documents in Gino. An update could overwrite the previous version, with no viewable history, no visibility on who made the change, and no clear indication of whether an attachment had been sent or returned as part of an exchange.

With this update, Gino versions attachments and retains their full history, including during exchanges with third parties.

🛠 What's changing

The attachment action menu now varies by file format:

  • Word / Excel / PowerPoint: edit, import a version, rename, delete

  • PDF / video / image / email: import a version, rename, delete

✅ Why it's useful on a daily basis

  • You no longer lose previous versions when updating an attachment.

  • You can more easily track the progress of an attachment throughout an exchange cycle.

  • You maintain better traceability of changes and feedback.

  • You can more easily retrieve a previous state if needed.

  • You retain the attachment history when a new version of a document is created.

💡 A few concrete use cases

Negotiation with a third party: an attachment sent by email comes back modified; it is added as a new version and its "badge: returned by contracting party" makes it easy to identify as a response.

External collaboration (Teams, Google, SharePoint): after collaborating in an external workspace, re-syncing to Gino creates a new version instead of overwriting the existing file.

Manual update of a supporting document: a user imports a more recent version of a PDF or image from their device, while retaining the previous history.

Creation of a new document version: attachments already present in the previous version remain available with their full history in the new version of the document.

⚙️ How it works

  1. From the attachment list, open the menu (⋮) for the relevant attachment.

  2. Depending on the file format, you can:

    • click Edit to modify the file directly in Gino (Word, Excel, PowerPoint)

    • click Import a version to add a new file from your device

  3. Each action that triggers a new version causes Gino to automatically create a Vn+1 with:

    • the author's identity recorded

    • a timestamp

    • an optional badge depending on the context

  4. If the attachment was sent within an exchange cycle:

    • the version active at the time of sending may display Sent to contracting party or Internal discussion

    • the version received in return or re-synced may display Returned by contracting party or Internal discussion

  5. If a new version is created by editing a version that already has a badge:

    • the badge remains attached to the previous version

    • the newly created version does not automatically inherit this badge

  6. When a new version of a Gino document is created:

    • the attachments from the previous version are copied

    • their full history is retained

    • this copy does not create a new attachment version

  7. Rights depend on the user profile:

    • all relevant profiles can view the history, view badges, download a previous version, and compare two versions when comparison is available

    • only authorised profiles can edit, import a version, re-sync, or delete an attachment

🎯 What this means for your teams

This update provides better visibility into the back-and-forth on annexes and working documents, secures file updates without the risk of silent overwrites, and improves continuity of tracking between document versions and collaboration spaces.

Gino's tip
Think of the attachment version history as a checkpoint during your exchanges. It is particularly useful for distinguishing what has been sent, what has been returned, and what has been manually updated in the file.

If you'd like to find out more, contact your project manager!

Did this answer your question?