> For the complete documentation index, see [llms.txt](https://docs.roamingiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roamingiq.com/network-administrator-console/network-operator-settings/ruckus-r1-dpsk3.md).
# Ruckus R1 DPSK3
### Important Information
Presently, the Ruckus R1 integration with VAULT is exclusively for support of Ruckus WPA3/DPSK3 system. For traditional VAULT deployments, please refer to our [R1 Configuration guide.](/network-equipment/access-point-configuration-guides/ruckus-one.md)
### How Do I Add My R1 Controller to VAULT?
1. From the Operator Information page, select the "Ruckus R1" tab.
2. Click, "Add Ruckus R1 Controller"
3. Enter the required Information. If you do not have this information available, please reach out to your Network Engineering team or your VAULT Account Manager for assistance.
4. If you want to immediately begin Syncing PSKs for the connected sites, select Sync PSKs. You can also enable this later. As noted, keypools will begin syncing immediately when you select "Add Ruckus R1 Controller"
5. To confirm your Keypools/SSIDs began to sync, navigate to the [Keypools ](/network-administrator-console/network-operator-settings/keypools.md)page within your operator settings. There, you should see Keypools from R1 listed with an "Auth Mechanism" of WPA3.
6. Now that you're controller is setup, you'll need to link it to the specific Venues that will be using the R1 DPSK3 integration
---
# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.roamingiq.com/network-administrator-console/network-operator-settings/ruckus-r1-dpsk3.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.