Stories History and Recovery
Overview
The Deleted Stories feature provides a safety net for your workflow by allowing you to view and restore stories that have been removed from your rundowns. All deleted stories are retained and can be recovered when needed.
Accessing Deleted Stories
-
Open any rundown in your project
-
Click the Bin button in the story list toolbar
-
The view switches to a three-column layout:
-
Left column: Your normal story list (for reference)
-
Middle column: List of all deleted stories from the current rundown
-
Right column: Read-only preview of the selected deleted story
-
Viewing Deleted Stories
The deleted stories list displays:
-
Story title and sequence number (if it had one)
-
Deletion timestamp showing when the story was removed
-
Who deleted it (the user who performed the deletion)
Sorting behavior:
-
Stories are sorted chronologically, with the most recently deleted appearing first
Restoring Deleted Stories
To restore a deleted story back to your rundown:
-
Click on the story in the deleted stories list to select it
-
Preview the content in the right column to verify it’s the correct story
-
Click the Restore button next to the story
-
The story will immediately reappear in your rundown’s story list
-
The restored story will be placed at the end of your rundown
Note: Restored stories retain their original content, including all text, formatting, tags, and sidenotes.
Permanently Deleting Stories
If you want to permanently remove a story from the trash:
-
Select the deleted story from the list
-
Click the trash icon button
-
Confirm the permanent deletion
Warning: This action cannot be undone. The story will be permanently removed from the system.
Closing the Deleted Stories View
-
Click the Close button in the toolbar to return to the normal rundown editing view
-
Your main story list and editor will reappear
Versions (Story History)
Overview
The Versions feature automatically tracks every change made to a story, creating a complete timeline of revisions. This allows you to review previous versions, compare changes, and restore earlier content if needed.
Accessing Story History
-
Open a story in the editor
-
Click the clock/timemachine icon (?) button in the editor toolbar
-
The Story History view opens, showing all saved versions of that story
Note: If the history feature is not available in your plan, the button will appear dimmed with a tooltip indicating Not available in your plan.
Understanding the History View
The Story History view displays:
-
Version timestamp: When each version was saved
-
Editor name: Who made the changes
-
Content preview: A read-only view of the story content at that point in time
Listing behavior:
-
Versions are listed in reverse chronological order, with the most recent version at the top
How Versions are Created
Versions are automatically saved when:
-
You make edits to a story and the content is auto-saved
-
You explicitly save using keyboard shortcuts (for example CTRL + F10)
-
You release the content lock on a story after editing
-
The system performs periodic auto-saves during active editing
Viewing a Specific Version
-
Click on any version entry in the history list
-
The content preview updates to show that version’s content
-
Review the text, formatting, tags, and sidenotes as they appeared at that time
Restoring a Previous Version
To revert a story to an earlier version:
-
Navigate to the version you want to restore
-
Click Restore this version
-
Confirm the restoration
-
The current story content will be replaced with the selected version
-
A new version entry is created, preserving the restoration as a new change
Important: Restoring a version doesn’t delete the history between that version and the current one. All versions remain accessible.
Comparing Versions
To see what changed between versions:
-
Select a version to view it
-
Note the timestamp and editor
-
Select an adjacent version (before or after)
-
Compare the content in the preview area
-
Changes will be visible in formatting, text content, or structural elements
Best Practices
-
Regular saves: The system auto-saves, but explicit saves (CTRL + F10) create clear checkpoints
-
Meaningful edits: Each save creates a version, so make substantive changes between saves
-
Review before major changes: Check recent history before making significant rewrites
-
Use for collaboration: See who made what changes and when during team editing
-
Audit trail: The version history serves as a complete audit log for editorial workflows
Limitations
-
Version history is tied to the story, not the rundown
-
Moving a story between rundowns preserves its full history
-
Deleted stories retain their version history
-
Very old versions may be archived depending on your plan’s retention policy
Closing the History View
-
Click the Close button in the toolbar to return to normal story editing
-
The current version of the story will be displayed in the editor
Tips for Using Both Features Together
Scenario 1: Accidental deletion
-
Go to Deleted Stories (Bin button)
-
Find and restore the deleted story
-
Open the restored story’s history to verify the content is complete
Scenario 2: Recovery from unwanted edits
-
Open the story’s history view
-
Find the version before the unwanted changes
-
Restore that version
-
If needed, compare with deleted versions to ensure nothing was lost
Scenario 3: Content audit
-
Use Deleted Stories to see what was removed from the rundown
-
Use Story History to see how remaining stories evolved over time
-
Together, they provide complete editorial oversight