Versions and history
Each artifact keeps a numbered history of its content. Approval freezes the current version; after that, the version cannot be edited. Starting a new draft, pressing New Version on an approved artifact, or returning a draft from review opens the next numbered version.
What freezes a version
Approving an artifact locks the content of its active draft version. That version becomes the artifact's approved record. The artifact reverts to draft status when you create a new version from it.
The content of a version cannot be changed once it is in review. Attempting to save while the artifact is in review shows a message: the reviewer must request changes before you can save.
Comparing versions
When an artifact has more than one version, View Changes is available from the overflow menu (⋮). It opens a side-by-side diff of the two most recent versions. At version 1, the item is disabled and shows: "Only one version exists."
Starting a new version
Press New Version in the header when the artifact is Approved or Locked. The button shows Creating... while the draft is prepared. The new draft starts from the approved content and receives the next version number.
Returning a draft from review also advances the version counter. See Review and approve artifacts for the request-changes flow.
Discarding a draft
Opened a new version by mistake? Choose Discard Draft from the overflow menu (⋮) and confirm. The draft is thrown away and the approved version becomes current again, with the artifact back in Approved. The discarded draft stays in the version list, marked discarded. The item appears only while the artifact has an approved version to return to; a draft that is in review must be rejected instead.
Designs
On a design (UI/UX design, wireframe or brand kit), the first change to an approved design opens a draft: a design chat message, a canvas edit, a new screen or a restyle. The approved design stays as it was reviewed until the draft is approved. A design system or brand change applies to every screen in the project, so it opens a draft for every approved design there.
Discard Draft on a design puts the approved screens, theme and screen list back on the canvas and removes screens added in the draft. If a design chat edit, restyle, variant or flow is still running, from any tab, it is stopped first, so nothing is written over the restored design. Pressing stop in the design chat also stops the edit on the server, not just in your browser. A design approved before this snapshot existed has no saved copy, so its draft cannot be discarded.
Records of a source
Some artifacts mirror something outside Flezise, and change only when it does: the stakeholder interview, uploaded documents, documents synced from Confluence, Notion or SharePoint, meeting transcripts, tickets and chat threads, and the codebase audit a repository scan builds. They have no New Version, edit, rename, Submit for Review, Request Changes or Regenerate.
Each change at the source becomes a new version, so a record keeps its history and View Changes compares the last two:
- A synced page that passes the quality check is approved straight away. One the check holds back waits In Review while the previous approved text stays in use; Approve puts it in the knowledge base, Reject drops the change.
- To update an uploaded file, choose Replace File from the overflow menu (⋮) and pick the newer file. It becomes the next version of the same
DOC-n, so links to it keep working, and the knowledge base re-indexes it. - When a page is deleted at the source, the next sync marks its document superseded and removes it from the knowledge base. A sync can only tell a page is gone when it read the whole source; past 2,000 documents, or the connection's own limit, it does not remove anything. If the page comes back, the document is restored.
The stakeholder interview (INT-n) is updated when a late answer arrives, and the system approves the update itself. Its Questions & Answers table names who gave or decided each answer, and a Divergences & decisions section lists every answer when people disagreed, the final decision, who made it, when, and why.
Restoring an earlier version
Open the Version property in the properties sidebar to see the full version list. Each row other than the current one has a restore icon. Pressing it copies the historical version's content into a new draft with the change summary "Restored from version N". The restore is non-destructive: the full history is preserved and the restored content goes through the normal review and approval pipeline before it becomes the approved record.
A superseded artifact shows Restore in the header. Pressing it works the same way.
From the terminal
FAQ
What happens to the knowledge base when I create a new version?
The approved content stays in the knowledge base while the new draft is in progress. The knowledge base updates when the new version is approved, replacing the previous version's indexed content. You can also trigger re-indexing at any time with Re-run RAG in the overflow menu.
Does restoring a version change the artifact's status?
Yes. Restoring creates a new draft from the historical content, so the artifact returns to draft status and must go through review and approval again before the restored content is approved.