> For the complete documentation index, see [llms.txt](https://design.mirakl.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://design.mirakl.com/design/components/actions/save-bar.md).
# Save bar
## Overview
Save Bar is always located at the bottom of the screen and stays fixed as you scroll through the page. It appears after a user performs an action (edit a form, tick a checkbox, etc.) from the bottom and should persist until the task is submitted or canceled.
Sticky Save should be used to save or discard in-progress changes. It contains a `Button Group` with a Save button as a primary action and a cancel button.
Sticky save should be used on all forms and is visible when there are unsaved changes.
To limit the user's mental load, we restrict `Save Bar` actions to two `Buttons` : "**Save**" (as a `Primary Button`) and "**Cancel**" (as a `Secondary Button`)**.**
Sometimes, we may want to offer users a third option: "**Save as draft**". As this option isn't prevalent in all of our forms, we decided to introduce a specific pattern with "**Save**" as a Primary Split Button and "**Save as draft**" as a Split option.
## Guidelines
### **How to use**
`Save Bar` behavior is automated by Roma; it will always stick to the bottom of the page and allow the user to scroll down the page.
The Save Bar has been created to be visible enough for users to notice it without disturbing them to perform their actions.
{% hint style="info" %}
[Learn more on how to use Save Bar in a form, depending on the form mode (creation or edition)](https://design.mirakl.com/~/changes/DpgERwSwrKIthStzL4D6/patterns/forms/creation-and-edition-modes)
{% endhint %}
## Key takeaways
{% hint style="success" %}
* Align Save Bar buttons with page content
* Respect Button content guidelines
{% endhint %}
{% hint style="danger" %}
* Do not show Save Bar if no actions are required from users
* Do not display more than 2 actions in the Save Bar
{% endhint %}
---
# 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, and the optional `goal` query parameter:
```
GET https://design.mirakl.com/design/components/actions/save-bar.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.