I’d pause edits first, then check Trash for deleted pages or Page History for overwritten text. Save any newer text before restoring an older version. Notion’s help docs state that, by default, pages remain in Trash for 30 days before permanent deletion (Delete & restore content); Enterprise owners can customize retention. Also see Back up your Notion data.
Here’s the recovery path I’d follow for your eBook workspace:
- Find the problem: Check page locations, database filters, permissions, and file access before assuming content is gone.
- Recover what you can: Restore available pages or earlier versions from Trash or Version history (Delete & restore). Ask Notion Support about unresolved losses; a whole-workspace restore isn’t guaranteed.
- Rebuild what’s missing: Repair your Book Hub, database relations, links, and permissions. An export is not a full workspace backup—Notion’s export help and backup guide explain what exports include and what they don’t recreate.
- Test before resuming: Check chapters, attachments, collaborator access, and automations.
- Keep an outside copy: Save dated exports, original files, and rebuild notes. Test recovery every quarter.
My rule is simple: recover the content, check the structure, then resume editing.
5 Ways To Recover Anything in Notion
Step 1: Identify Missing Content and Access Issues
First, check whether content was deleted, overwritten, moved, or blocked by access settings. Confirm your account email and workspace name. Ask a workspace admin to check your membership and page permissions. If your workspace uses SSO, have the admin check your sign-in access, too.
Use the row that matches what’s missing.
| Loss type | Checks to perform | Recovery action | Expected limitations |
|---|---|---|---|
| Missing chapters or drafts | Search by title, then check the parent page and Trash | Find moved pages or recover deleted pages | Recovering chapters does not rebuild the Book Hub |
| Overwritten chapter text | Check page history | Restore an earlier version | History may not contain the version you need |
| Missing database content | Check filters, hidden properties, and the source database | Fix the filter or restore the missing property | A hidden entry is not necessarily deleted |
| Missing Book Hub | Check its location and parent pages | Restore the Book Hub navigation | Links and structure still need verification |
| Missing files | Check attachments, external links, and original source files | Restore file access or upload a saved copy | Restoring a page may not restore external files |
| Missing workspace access | Ask an admin to check membership and SSO access | Restore membership, permissions, or SSO access | Page recovery is not a full-workspace restore |
Check Trash, Page History, and Database Properties
Check Trash to confirm whether a page was deleted. Use page history to see whether - and when - content was overwritten.
For databases, check filters and hidden properties before assuming data is gone. If a property was deleted, check which recovery controls are available.
Record the affected pages, missing items, and the last date and time the content was intact.
Check Access, Page Locations, and Files
Search for content and try saved links or bookmarks. A page may have moved outside its usual parent page. Before rebuilding, ask an admin to check for moved pages, permission changes, and membership changes. An inaccessible page is not proof of deletion.
Make an inventory of the page hierarchy, linked databases and their sources, navigation links, chapter images, PDFs, and external source files. Include saved exports and original source files.
Separate missing assets from inaccessible assets. An external file may still exist even if its link no longer works. Use these findings to choose the recovery path in Step 2.
Step 2: How do I recover deleted or overwritten content?
Use your Step 1 inventory to choose the smallest recovery method for each missing item. Before you start, check Notion’s current retention window and plan limits in the Help Center.
| Recovery option | Loss type | Availability | Expected result | Limitations |
|---|---|---|---|---|
| Trash | Deleted pages and database properties | Typically 30 days, subject to workspace settings and current policies | Restore available pages or database items | Check parent pages and nested content after recovery |
| Page history | Overwritten content | Depends on your plan and its retention window | Restore an available earlier page version | May overwrite newer edits |
| Copy blocks from history | Missing passages or sections | Only when page history allows block copying | Recover selected content without reverting the whole page | Not available in every interface or for every block type |
| Support help | Unresolved loss or an inaccessible workspace | Contact Notion Support promptly | Review of available recovery options | No guaranteed snapshot, recovery window, or whole-workspace restore |
Restore Deleted Pages and Database Properties
Open Trash, select the deleted chapter or parent page, and use the available restore control. Then check its parent page and nested content against your Step 1 inventory.
For a deleted database property, use the property recovery controls if available. Check the restored values and their relationships to other data. Not every database field can be restored.
Restore an Earlier Page Version
Use Page history for overwritten content, rather than deleted content. Choose a version from before the loss.
If the interface lets you copy historical blocks, retrieve only the missing content. Otherwise, restore an available earlier version and carefully merge the newer text you saved. Check the recovered chapter for missing sections and duplicate passages.
Contact Notion Support for Other Recovery Options
If the loss is still unresolved, send Notion Support your workspace name and URL, affected page URLs, the date and time of the loss with its time zone, and the steps you’ve already tried.
Ask what can still be recovered, which retention limits apply, whether required permissions affect recovery, and how any proposed action could affect newer work. Do not assume support can restore the entire workspace to a single point in time.
Know the clocks before you panic. Per Notion's delete and restore help (checked 2026-11-04):
| Where it lives | How long | What it means for you |
|---|---|---|
| Trash | 30 days by default | Restore from the sidebar; trashed pages cannot be edited until restored |
| After permanent deletion | 30 more days, then inaccessible to everyone | Contact Notion support promptly; it keeps backups to restore a snapshot from the past 30 days |
| Page version history | 7 days on Free, 30 on Plus, 90 on Business | A chapter overwritten last month may be gone on a Free plan |
Two details catch people out. Restoring a database restores its pages and properties but not the text inside those pages, so you must restore each page individually. And version history records a new version every 10 minutes of active editing, which means a very recent mistake may be captured only at coarse intervals.
Step 3: Rebuild the eBook Workspace Structure
If recovery brings back your pages but not their structure, rebuild the workspace manually. Leave exports untouched and work from copies. Exports may contain HTML or Markdown pages, CSV databases, and uploaded files, but they don’t restore workspace behavior. Rebuild in layers: the hub, chapters, databases, and workflow.
Recreate the Book Hub and Import Chapters
Start with the top-level eBook hub. Add sections for planning, drafting, editing, and review. Then import supported files or copy recovered manuscript text into the right chapter pages. Include supporting files and keep chapters in their original order.
Rebuild Databases, Links, and Permissions
Treat CSV files as data sources, not live databases. Recreate and check property types, relations, rollups, formulas, views, and templates. Reconnect chapters to planning records, research, and assets.
Fix broken links and set permissions carefully. Don’t assume imported pages keep their original access rules.
Rebuild the Agent Workflow
If you’re rebuilding an Interactive eBook Builder workspace, use the planning agents to recreate the outline. Review and edit the generated titles and descriptions before merging them with your recovered text.
Step 4: Check the Recovered Workspace
Treat your most recent export as a comparison point, not a complete record - it may not include newer edits. Compare it with the recovered workspace, note missing content or changes in structure, and use those differences to decide what to repair first.
Check every page, file, and link against the Step 1 inventory. Confirm page locations, chapter titles, and chapter order. Review prompts, exercises, worksheets, and checklists for missing text or broken instructions. Open attachments and follow navigation links to check their contents and destinations.
Test workspace settings as you use them. Check database properties and view filters, then create a temporary entry from each required template. Verify collaborators’ access and confirm that private manuscript pages remain private.
Run one sample through planning, drafting, and editing. Make sure each stage uses the intended source material and saves its output in the right place. Keep publishing and printing disabled until you’ve checked each automation’s connection, target, and trigger conditions.
Save a new external export to use as the starting point for Step 5. Keep the earlier export unchanged so you can compare them in that step.
Step 5: How do I save and test an external backup?
After recovery, export your Notion workspace and save it outside Notion before you start editing again. If you can’t export it, ask a workspace owner for help. Download the export before the link expires, then store it in a dated folder.
Example folder name:
2026-11-02
Use separate folders for source files, drafts, and final deliverables. Keep original assets and approved drafts apart from workspace exports. That way, you won’t have to rebuild the workspace just to recover your book.
These backup sources protect different parts of your work:
| Backup source | What it preserves | Limits | Rebuild needed? |
|---|---|---|---|
| Workspace exports | Exported text, database data, and included attachments | Does not preserve permissions, automation logic, or database relations | Import content and rebuild settings, relations, and connections |
| Source files | Original manuscripts, assets, and milestone drafts | Does not preserve workspace structure or database settings | Recreate the workspace around the recovered files |
Keep an external workspace blueprint for your rebuilt eBook workspace. Document its page hierarchy, database properties and views, templates, permissions, agent instructions, and automation dependencies. Include connection names and required inputs, but leave out passwords, API keys, and other credentials.
Export after each chapter, major revision, or database change. Every quarter, test recovery in a test workspace. Import sample chapters and check links, attachments, and database behavior. Save any repair notes with the backup.
Notion's export help says a full workspace export arrives as a link that expires after 7 days and can take up to 30 hours to process on large workspaces, and that you cannot simply re-upload an export to recreate your workspace. So test the backup: open the export, confirm the manuscript Markdown files and database CSVs are readable, and keep one dated copy outside Notion.
Conclusion: Recover Content and Verify the Rebuild
Use the inventory from Step 1 to identify whether the loss affects a page, property, or workspace. If recovery still fails, ask Notion Support whether a broader restore is available.
Page recovery restores specific items; a workspace restore rolls back broader structure and may require support. After restoring content, check chapter locations, database relations, deleted properties, orphaned pages, and sharing permissions. Test the workflow before relying on the workspace again.
Keep a tested external export and rebuild notes to make future recovery faster and reduce your dependence on retention limits.
Related reading: turning a Notion page into a PDF; a Notion book writing template; planning, drafting and editing with AI.
FAQs
How can I assess the full scope of workspace loss?
Check your Notion sidebar for missing pages, subpages, or databases. Look in Trash for anything deleted by mistake. Deleted items can only be recovered for a limited time.
Review shared workspace permissions or recent activity logs to check whether access changed or collaborators moved pages.
Compare your current workspace with your project requirements to spot missing pieces, such as eBook planning agents or chapter drafts.
When would I need more than page recovery?
When your workspace structure is corrupted or accidentally deleted, recovering individual pages may not be enough. Database relationships, agent configurations, and connected chapter templates may still need repair so they work together as intended.
If this disrupts your Interactive eBook Builder workflow, you may need to rebuild that structure so your AI agents can plan, draft, and polish your eBook.
How can I merge recovered chapters without losing edits?
Copy content manually from the restored pages into the master chapters in your template workspace. Paste the revised text into the designated draft fields, keeping your current edits and the chapter blocks the agents use intact.
Before finalizing, confirm that each chapter follows Agent A’s structure and check the pasted text for formatting issues. Avoid bulk imports or overwriting existing chapter records, which can cause data conflicts.