> For the complete documentation index, see [llms.txt](https://docs.crobox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crobox.com/security-and-compliance/legal/developer-mode.md).

# Developer Mode

## Overview

Developer Mode offers advanced users access to features that can significantly influence the platform's performance, security, and data integrity. This mode is designed for developers who need deeper control over customization and integration within the Crobox platform.

By enabling Developer Mode, users can:

* Inject custom JavaScript code
* Add NPM dependencies in the Javascript Snippet.
* Create advanced components using JSX.

These capabilities are intended for developers with a deep understanding of the technical aspects of web development and platform security.

{% hint style="warning" %}
Developer mode is not available for Essential package plans, nor for non-technical users.
{% endhint %}

## Enabling Developer Mode

To enable Developer Mode, users must agree to the Developer Mode Agreement, which includes accepting all legal terms and conditions as outlined within the app.

To enable this setting and confirm you agree with the legal considerations, go to:

1. Crobox platform
2. My profile
3. Enable Developer Mode
4. Read the terms and conditions
5. Click accept and request

Your request will be processed by authorized Crobox employees and approved for usage.

{% hint style="info" %}
Contact your Customer Success Manager for further details or questions surrounding the capabilities of developer mode.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.crobox.com/security-and-compliance/legal/developer-mode.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.