As your partner program scales, keeping track of who changed what and when can become critical. A renamed asset, an experience updated mid-quarter, or an access setting flipped from public to restricted can quietly break partner-facing content if no one notices.
Every change to an asset or a partner portal experience is logged automatically, and you can roll back to any previous version in one click — no support ticket, no manual restore, no lost work.
There are two types of versioning in Introw, each tracking a different surface of your partner program:
Asset versioning — covers every change to files and content in your asset library.
Experience versioning — covers every change to your partner portal experiences.
Asset versioning
Asset versioning protects everything stored in your asset library — PDFs, videos, images, links, and their metadata. Whenever someone uploads a replacement file, renames an asset, or changes who can see it, that change becomes a restore point.
What gets tracked on an asset:
Name changes — every rename of the asset
Asset replacements — when a new version of a PDF, video, image, or link is uploaded
Access changes — switches between Public, Portal, and Restricted access, including added or removed audience filters
Category changes — when an asset is recategorized or moved
Thumbnail updates — when a custom thumbnail is added, replaced, or removed
Archiving and restoring — including the reason provided when archiving
Viewing the asset history
Open any asset and select the History tab from the detail view. You'll see a chronological log of every change made since it was first created.
One-click version restore
Every asset replaced entry in the history log is a restore point. If a teammate replaces an asset with the wrong file, you can bring back the previous version instantly.
How to restore a previous version:
Open the asset or experience and go to the History tab.
Find the version you want to restore.
Click Restore next to that entry.
The object reverts to the selected version immediately. The restore itself is logged as a new entry in the history, so the audit trail stays intact and you can always roll forward again if needed.
💡 Tip: Restoring a previous version doesn't delete newer history entries — every change before and after the restore stays in the log. This means you can safely experiment with restores without losing the record of what happened.
Experience versioning
Experience versioning protects the partner portal experiences your partners actually see. Because experiences are made of sections, text, embedded assets, and styling, history captures changes at the section and content level — not just at the top of the page.
=> You can find the version history of an experience in the top right on the 3 dots.
What gets tracked on an experience:
Sections added or removed — when a new section is dropped into the experience, or an existing section is deleted
Text added or removed — every edit to a text block, including new paragraphs, deleted copy, and inline formatting changes
Name and title changes — every rename of the experience itself or any of its sections
Layout and visibility changes — when sections are hidden, shown, or layout updates happened
Each entry shows the user who made the change and the exact timestamp, giving you a complete audit trail for compliance reviews or internal investigations.
Governance best practices
Provide a reason when archiving. A short note explaining why something was archived helps your team decide later whether to restore or let it expire.
Review the history before making changes. A quick glance at the log tells you when the current version was last updated and by whom — useful context before overwriting.
Audit access changes regularly. Filter the history view for access-related changes to confirm that restricted assets and experiences are still scoped to the right partner segments.
Coordinate large edits. For portal experiences shared with many partners, check the history to see recent changes by other teammates before publishing — this avoids overwriting in-flight updates.