Connections & publishing
Undo a change or go back to an earlier version
Each project keeps a saved version every time a card finishes. Ask Lenexa to undo a change, show an older version, or make a staging copy first.
Published Updated
Can I undo a change the crew made?
It depends on when the change was made. Each project in your Studio keeps a saved version every time a card finishes, so you can ask Lenexa to undo the last change, show you yesterday's version, or bring one page back. The crew puts the earlier version back and Deployment publishes it again. A version from before your project's history began can't be brought back, and a WordPress site that stays on WordPress lives on your host, so ask for a backup before a change there.
Saved version: a snapshot of a project's folder, kept in your Studio each time a card on the Board finishes. It stays in your Studio and is never published or sent anywhere.
What's saved, and when
Every time a card on your Board finishes, your Studio saves a version of that project's folder: the pages, images, styles and the crew's private notes. Nothing is saved when nothing changed. A project whose history started after it already existed begins with a version called Starting point, so even the first change after that can be undone.
- Kept: everything the crew made for the project, including the private notes folder.
- Left out: temporary caches, key files, and any single file over 25 MB, like a large original video.
- Never sent anywhere: saved versions stay in your Studio. They are not published and not copied to any other service.
Ask for it in plain words
Tell Lenexa what to go back to
Say what changed and what you want back. The more specific, the fewer credits it takes.
The crew compares and brings it back
The Lead Developer finds the saved version, compares it with today's, and puts back what you asked for. The change you are undoing stays in the history too, so nothing is lost.
Approve the publish
Your live site changes only when Deployment publishes the earlier version, with the same checks as any publish.
Needs you: give the go-ahead to publish
Undo the last change to the home page and show me the preview before you publish it.
Show me yesterday's version of the services page next to today's, and tell me what changed.
Other things you can ask for
Make a staging copy before you change the home page, so I can check it first.
A staging copy is the change published to a test folder on your hosting, next to your real site. Deployment gives you the test address. Your real site changes only after you say it looks right. The test folder is public while it exists, so ask Lenexa to remove it when you're done.
Check my SSL and DNS.
Deployment opens your address with and without www, says whether each one loads with a valid certificate and shows your site, and tells you in one sentence what to change at your domain registrar or host if something is off. It looks only; it never changes your DNS.
What it costs
Keeping saved versions doesn't use credits. Comparing, bringing back and publishing a version is crew work, so it uses credits like any other card. See what a credit buys.
A WordPress site that stays on WordPress
If the crew works inside your WordPress on your host, the site isn't in your Studio's folders, so there's no saved version of it. Ask for a backup or a staging copy before an update. A site the crew moved off WordPress is a project like any other and has saved versions.
Next
Questions
Not until Deployment publishes it. Lenexa makes a card to publish the earlier version, with the same checks as any publish.
Keeping them doesn't. Asking the crew to compare, bring back or republish a version is crew work, so it uses credits like any other card.
Not as of October 2026. They stay in your Studio. Your live site is on your own hosting, where you can download it any time.