# Dropdown

### **Use Cases:**

✅ Space-efficient options: Use Dropdowns to present a list of choices when space is limited, as they occupy minimal screen real estate until activated.

✅ Simplified selection: Provide users with a convenient way to select one option from a list without cluttering the interface.

✅ Categorization and grouping: Use Dropdowns to group related options under different categories, enhancing organization and ease of selection.

✅ Dynamic filtering: Implement Dropdowns to allow users to filter content or data based on the selected option, dynamically updating the displayed content.

✅ Configurable settings: Utilize Dropdowns to offer users a way to configure settings, preferences, or customization options.

### **Not to Use Cases:**

❌ Overuse: Avoid using Dropdowns for every interaction, as they can make the interface overwhelming and less user-friendly.

❌ Long lists: Do not use Dropdowns for displaying excessively long lists of options. Scrolling through a lengthy dropdown can frustrate users and hinder their ability to find desired options.

❌ Critical actions: Avoid using Dropdowns for critical actions that require immediate attention or confirmation, as they might not provide the necessary prominence.


---

# 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/dropdown.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.