> For the complete documentation index, see [llms.txt](https://docs.cloudscaff.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudscaff.com/general-tools-and-features/toggles.md).

# Toggles

## Purpose

Toggles are designed to make actions simple and visual — when something is **ON**, it’s clearly active, and when it’s **OFF**, it’s inactive. This helps users easily see what features or options are currently in use.

***

## How Toggles Work

#### Toggle **ON** (Orange)

* The setting or feature is **active**.
* The system recognizes that action or function as **enabled**.
* The switch appears **orange** to show it’s turned on.

#### Toggle **OFF** (Grey)

* The setting or feature is **inactive**.
* The system ignores that action or function.
* The switch appears **grey** to show it’s turned off.

{% columns %}
{% column %}
**Toggle is OFF**

<div align="left" data-with-frame="true"><figure><img src="/files/GjSma74PmCukVp84eSsG" alt="" width="99"><figcaption></figcaption></figure></div>
{% endcolumn %}

{% column %}
**Toggle is ON**

<div align="left" data-with-frame="true"><figure><img src="/files/SnRTvAtOSItn9j7yDYhN" alt="" width="98"><figcaption></figcaption></figure></div>
{% endcolumn %}
{% endcolumns %}

***

### Example

If a toggle for **Notifications** is turned **ON**, the system will send you alerts or updates.

If the toggle is **OFF**, you won’t receive any notifications.

***

### Best Practices

* Always double-check toggle states before making changes.
* Use toggles for quick adjustments rather than detailed configurations.
* Remember that toggles update instantly — turning one on or off applies immediately.


---

# 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://docs.cloudscaff.com/general-tools-and-features/toggles.md?ask=<question>&goal=<endgoal>
```

`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.