> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/feature-templates/account-settings/success-modal-screen-and-delete-account-confirmation-screen.md).
# Success Modal Screen & Delete Account Confirmation Screen
There are two modal screens that come with the Account Settings Feature Template — both are to confirm actions that have been taken.
The two remaining screens in the Account Settings Feature Template are modal screens, which are used as a Success State or a Confirmation State.
For the ‘Success Modal’ Screen — this screens acts as a confirmation that the user has updated their account info and provides a seamless transition to continue actions within the account.
The ‘Delete Account Confirmation’ Screen is a used as a “double-check” on whether or not the user would like to delete their account. This is standard practice in software since it is relatively easy to accidentally hit the wrong button. In this case, if a user clicks the “Delete Account” button on the ‘Account Settings’ Screen, they will get the opportunity to confirm this is the action they actually want to take.
## The Components
Each screen comes with a modal — in other words, a pop up to display the next steps. Typically these come with header text, body text, and a button. There is also a way for the user to cancel the action by clicking the icon in the upper right hand corner.
⚡ **Success Modal Actions**
* The OK Button links to the ‘Account Settings’ Screen
⚡ **Delete Account Confirmation Actions**
* Delete My Account Button
* Delete User
* Link Action to ‘Log In’ Screen
* Cancel Button
* Link Action to “Back”
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.adalo.com/feature-templates/account-settings/success-modal-screen-and-delete-account-confirmation-screen.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
