# Modal

### Use Cases:

✅ Displaying additional content or information that requires user attention or interaction without navigating away from the current page.

✅ Requesting user input or confirmation for critical actions, such as deleting data or making irreversible changes.

✅ Presenting complex forms or workflows that benefit from a focused and isolated user interface.

✅ Showing detailed information or media, such as images, videos, or documents, in a larger and more prominent view.

### Not to Use Cases:

❌ Using Modal for non-essential or trivial information that can be effectively communicated through less intrusive means, such as tooltips or inline messages.

❌ Overusing Modals, resulting in excessive interruptions or obstructing the user's workflow.

❌ Employing Modals for presenting lengthy content that is better suited for a separate page or scrolling interface.

❌ Using Modals as a substitute for proper navigation or organizing content. Modals should not serve as a primary means of content presentation or structuring.

<br>


---

# Agent Instructions: 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://2600hz.gitbook.io/sds/sds-3.0/sds-components/components/modal.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.