# Switch ### **Use Cases:** ✅ Toggling settings: Use the "Switch" component to allow users to easily turn specific settings on or off, such as enabling notifications, dark mode, or privacy options. ✅ Binary choices: "Switch" components are suitable for scenarios where there are two distinct states or options, and users need to make a choice between them. ✅ Real-time updates: "Switch" components are ideal for situations where users need to see an immediate change based on their selection, without the need for additional confirmation. ✅ Compact space utilization: "Switch" components offer a space-efficient way to present toggleable options, especially in settings panels or control bars. ### **Not to Use Cases:** ❌ Multi-option selections: "Switch" components are not suitable for scenarios where there are more than two options or where complex configuration is required. For such cases, consider using checkboxes, radio buttons, or dropdown menus. ❌ Complex interactions: Avoid using "Switch" components for actions that involve multi-step processes or require additional user input beyond a simple binary choice. ❌ Confusing usage: Do not use "Switch" components in situations where the meaning of the toggle action is unclear or where it might lead to user confusion. --- # 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/switch.md?ask= ``` 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.