> For the complete documentation index, see [llms.txt](https://docs.blynk.io/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blynk.io/en/concepts/developer-mode.md). # Developer Mode **Developer** is a special user who has access to all the functionality required to configure the platform for the use by end-users (also called as clients or end-customers). This is usually someone who builds the hardware, develops the firmware, and does all the device configurations. By default, first user in the Organization becomes a Developer. Developer can: * Create and configure Device Templates in Blynk.Console * Create and configure web dashboard UI * Create and configure mobile dashboard UI * Add new devices to the account * Publish Templates to Blynk.Marketplace (work in progress) * Use other features accordingly to the chosen [plan](https://blynk.io/pricing) ## **How To Enable Developer Mode** 1. In the Blynk app or in [Blynk.Console](https://blynk.cloud) 2. Navigate to **My Profile** in the left menu of a Blynk app or in the top right menu on Blynk.Console 3. Check that **Developer Mode** switch is set to ON ### Multiple developers It’s allowed to add multiple developers per Organization within the [PRO or Enterprise plans](https://blynk.io/pricing). Assign a user the Admin role in your Organization so they can switch to the Developer mode. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.blynk.io/en/concepts/developer-mode.md?ask=&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 `build a script that syncs our docs to a CMS` 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.