> For the complete documentation index, see [llms.txt](https://docs.cubilock.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cubilock.com/profile-management/privacy-settings/developer-settings.md).

# Developer Settings

The **Developer Settings** profile option allows administrators to control access to Android’s developer settings — including **Developer Options** and **Safe Boot** — on managed devices. These settings are normally used for debugging, testing, and advanced OS configuration. In an enterprise environment, restricting access can help improve device security by preventing users from enabling features like USB Debugging or other system‑level tools.

#### Navigation:

Device Management → Device Profiles → Edit Profile → Privacy Settings → Developer Settings

#### **What This Setting Controls**

Android devices include a hidden **Developer Options** menu that grants access to advanced settings like USB debugging, animation control, hardware acceleration options, and more. In a corporate‑managed environment, allowing end users to access these options can pose security risks or undermine policy enforcement.

The **Developer Settings** dropdown in CubiLock allows you to control this behavior:

* **Unspecified** – No explicit override is applied; the default Android management behavior remains in effect.
* **Disabled** – All developer settings are **blocked**. The device user will not see or be able to enable Developer Options or Safe Boot via the system settings.
* **Allowed** – Developer settings are **permitted**. Users may see and enable Developer Options if they can access them through the Android system UI (e.g., tapping the build number).

These options map to the `developerSettings` enumeration used in the Android Management API, where:

* `DEVELOPER_SETTINGS_DISABLED` **prevents users from accessing developer settings**, and
* `DEVELOPER_SETTINGS_ALLOWED` **permits access**.

#### **Why Use Developer Settings Restrictions**

Controlling developer settings can help:

* **Prevent misuse of debugging features** such as USB debugging or secure‑boot disabling.
* **Stop unauthorized bypasses** of security controls or device lockdown measures.
* **Ensure consistency of managed policy enforcement** across all devices in an enterprise deployment.

💡 On some device types or enrollment configurations (especially personally‑owned devices), restrictions on developer settings may function differently or be limited in scope.

<figure><img src="/files/D4ekXBSPHcfcKjeeXzFD" alt=""><figcaption></figcaption></figure>


---

# 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.cubilock.com/profile-management/privacy-settings/developer-settings.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.