> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/connectivity/configuration/add-wi-fi-gateway-to-command/wi-fi-network-management-for-gw31-e.md).

# Wi-Fi Network Management for GW31-E

Learn how you can manage your password for different Wi-Fi networks

You can add a hidden network to your network settings and configure a secondary credential. This is useful for connecting to networks that don’t broadcast their SSID and for continued connectivity if the primary credential expires.

***

## Hidden Network

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Devices .**
{% endstep %}

{% step %}
**Select your gateway.**
{% endstep %}

{% step %}
**In the top right, click Settings.**
{% endstep %}

{% step %}
**Under Network > click Other Networks.**

a. Enter the **Network Name.**\
b. Enter the **Security** type.\
c. Enter the **Password.**\
d. Check **Hidden Network**.\
e. Click **Save.**

<div align="left" data-with-frame="true"><img src="https://1814166542-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiAGnzScvko5PkG7YBy3i%2Fuploads%2Fgit-blob-7f173f82bcd9c200aa23607377354f752418a83e%2F3b1436b39b80bcf794bcd0341b239ec63bd3246b.png?alt=media" alt=""></div>
{% endstep %}

{% step %}
**The device will connect to the hidden network and display under Wi-Fi > Known Networks.**
{% endstep %}
{% endstepper %}

***

## Pre-change password

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Devices.**
{% endstep %}

{% step %}
**Select your gateway.**
{% endstep %}

{% step %}
**In the top right, click Settings.**
{% endstep %}

{% step %}
**Under Network > click Other Networks.**
{% endstep %}

{% step %}
**Next to your network, click > Credentials.**

<div align="left" data-with-frame="true"><img src="https://1814166542-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiAGnzScvko5PkG7YBy3i%2Fuploads%2Fgit-blob-98c4bfdf6842cf58c90fc5ae2f49ab8178ba1c33%2F2c1a22e4fbc46510d16c9fa8ecb5c7510b4a6a9f.png?alt=media" alt=""></div>
{% endstep %}

{% step %}
**Click Add New Credentials**

a. Enter the **Username.**\
b. Enter the **Security** type.\
c. Enter the **Password.**\
d. Click **Done.**
{% endstep %}
{% endstepper %}


---

# 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://help.verkada.com/connectivity/configuration/add-wi-fi-gateway-to-command/wi-fi-network-management-for-gw31-e.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.
