> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/qna/using-navixy/lock-down-device-activation.md).

# Lock down device activation

Restrict device activation to specific devices using activation codes, or remove the activation option entirely via Menu Editor for end users

## Question

Is it possible to lock down device activation for clients?

## Answer

Yes, you're able to do this via a couple of different ways, with activation codes or by removing the option physically from the end user.

1. With activation codes, you must first reach out to the Support Team. They will assist you in enforcing the activation codes for every device activation. This means that your user can't activate one unless they have a code from you. To get more activation codes, please contact the Support Team and they will provide you with however many codes you wish.
2. By removing the Device Activation option via the Menu Editor. This can be done within the Menu Editor option, and all that needs to be done is to simply remove the activation option. Unlike activation codes, this doesn't allow the user to activate devices at all.

## Links

* [Activation codes](/docs/admin/activation-codes.md)
* [Custom menu editor](/docs/admin/settings/custom-menu-editor.md)


---

# 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://navixy.com/docs/qna/using-navixy/lock-down-device-activation.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.