A saved story archive needs a custom configuration
The free desk runs a full AI edit on anything you import, but drafts live only in your browser session — export or email what you need to keep. Persistent, newsroom-only storage is set up as part of a custom configuration.
Preview
Kept in your newsroom's own database, with version history and per-editor access.
A look at how this runs once configured for your newsroom. It is a static preview — nothing here is saved.
What a custom configuration adds
- A private database only your desk can reach
- Full story history: versions, queries, resolved edits and who made them
- Per-editor accounts instead of a shared link
- Passcode-protected or role-restricted stories
- Exports and email handoff to writers from your own domain
Reach out to Vania at NewsWerks
This part of the desk has to be configured for your organization — your stylebook, calendar, accounts and CMS connections. Email Vania at vania@newswerks.io and we'll scope it with you.
More that can be configured for you
Editorial calendar
A live calendar has to belong to one newsroom: pub dates, reporters, first and second editors, visuals and social copy are internal planning. The free desk can't hold it privately, so the calendar runs on your own private workspace.
House style rules
Every newsroom's stylebook is different, and the rule database is what drives the AI edit. The free desk runs on a general rule set; your own stylebook lives in a private rule database only your desk can change.
Google Doc import
Pulling copy straight out of your Drive needs credentials for your Google Workspace, which only exist on your own private build. On the free desk, paste the doc text or upload a DOCX instead.
Staff accounts
The free desk is open by design: no password, no accounts, nothing stored that belongs to one newsroom. Locking the desk down to your staff is part of a custom configuration.