Quick taskPublishing
Make the change. Keep the link.
Revise a published guide or project page without asking everyone to save a new address.
A complete worked example
Change the plan without sending everyone a new link.
Acorn's client guide is already shared. Photography is delayed, but the rest of the project remains on schedule.
Fictional project and sample data. This preview does not submit, publish, or change access.
Existing client access · illustrative result
Autumn launch plan
The current plan before the photography change.
- Photography due
- October 9
- Content review
- October 13
- Launch target
- October 15
Working from one page
The guide contains the agreed milestones and open decisions. Readers use the same published link throughout the project.
What the recipient can access
The same guide under its current password setting.
Kept out of this handoff
Internal scheduling discussion and unrelated project files.
How it runs
- Find the pageOpen the existing document and inspect its current version.
- Apply the changesGive your connected agent the edits or change the document in the app.
- Keep the referencePublish the revision in place and check the original link.
- You getA new document version at the original URL.
A prompt to start with
Copy this into your AI tool after connecting it to Fermium. Replace the bracketed details and let it ask for the context it needs.
Update [existing page] with [changes]. Read the current version first, preserve its audience and URL, and summarize the edits after saving.
What this workflow needs
Editing requires access to the document. Restoring an older version depends on the history retained by your plan.
Will people need a new link?
No. Updating the existing document preserves its URL.