> For the complete documentation index, see [llms.txt](https://docs.klai.studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.klai.studio/engineering-reference-docs/software-testing-overview/ux-ui-checklist/flows/saving-changes.md).

# Saving changes 💾

Users are constantly updating their details. They might be changing an email address, fixing a typo in their name, or updating their payment details. That's why it's important to confirm that a change has been saved, in the clearest way.

* [ ] Show the action to save changes

  An action should be visible as a source of confirming changes to be saved - this is usually a button.

  Initially, the action can be disabled. It indicates no changes have been made, and there is nothing to save.

  A common location for this action is in the navigation above the fold, so it's always visible over the content. Another option is after all the content that's editable.
* [ ] State changes to active once a change is made

  In the example, we've changed the email address, which means a change is waiting to be saved. Changing the state to active brings the action to the user's attention.
* [ ] Action changes to loading state when pressed

  Once the user

  Now that the changes are being saved, you want to show that action is in progress.

  You can do so with a loading spinner in the action, as the user's view will be on that element.
* [ ] Notify changes have been saved

  The page will reload or update, and this is the critical part. The user should now be informed that their changes have been saved.

  They can now safely leave the page, knowing the details are locked in until they choose to change them again.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.klai.studio/engineering-reference-docs/software-testing-overview/ux-ui-checklist/flows/saving-changes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.