> For the complete documentation index, see [llms.txt](https://docs.vectra.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vectra.ai/deployment/appliance-operations/changing-sensor-cli-password.md).

# Changing Sensor CLI password

Change the CLI password for a Vectra Sensor.

If you need to change the password for the Vectra user on the Sensor, you can do so by logging to the sensor CLI and following the command below:

```language-markup
vscli >  set password
(current) password: ************
Passwords must be at least 8 characters long and contain at least
1) one digit (0-9)
2) one upper case letter (A-Z)
3) one lower case letter (a-z)
4) one symbol (~!@#$%^&*_-+=`|\(){}[]:;"'<>,.?/)

Enter new password: ************
Re-Enter new password: ************
new passwd entered
Password Change: success
```

```language-c
vscli > set password -h
Usage: set password

  Change the system password - not available on sensors if password managed by
  brain
```

**Note**: While the sensor is paired to the brain, using "set password" command on the sensor CLI will not work and is not supported.

**If you are unable to change the password or log into the CLI, please contact Vectra Support at** [**support@vectra.ai**](mailto:support@vectra.ai) **for further assistance.**


---

# 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.vectra.ai/deployment/appliance-operations/changing-sensor-cli-password.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.
