Understand the unsaved changes warning
Learn when ATSReady warns about unsaved settings changes, which links are covered, and where that protection does not apply.
On this page
ATSReady warns about unsaved settings changes on some navigation paths and not others, and the split is narrower than it looks.
When ATSReady warns
- when you refresh the page
- when you close the tab or window
- when you click a destination row in the sidebar rail
- when you click the ATSReady brand link, in the sidebar or in the drawer on a phone
- when you switch conversations in the chat thread rail
In those in-app cases, ATSReady opens a dialog headed Discard unsaved changes?, telling you that your edits have not been saved and that leaving now discards them. Cancel keeps you where you are and is where focus lands; Discard changes leaves and drops the edits.
Where the warning does not apply
- Browser Back and Forward. The browser has already changed the history entry by the time the app hears about it, so there is nothing left to intercept.
- Ordinary links inside a page. Only the surfaces listed above ask the guard before navigating; every other link goes straight through.
- Sidebar rows that open an external site in a new tab. Those carry no handler at all, so they cannot reach the guard even in principle.
Which pages have anything to protect
Only Account and Preferences can hold unsaved edits: an in-progress display-name edit on Account, or a dirty section on Preferences. The General settings page saves each control as you change it, so there is nothing there for the warning to be about. Where each setting lives is the map of the three routes.
The resume editor has an unsaved-changes problem of its own, with its own guards and its own gap. It is described on Edit a resume rather than here.
If you have unsaved edits, save them before using browser history controls.
Result
If the warning appears and you choose to stay, your unsaved edits remain exactly as they were.
This page carries no screenshot. The dialog it describes only exists while a real account has unsaved edits pending, which is a state that cannot be set up for a capture without changing that account.