> For the complete documentation index, see [llms.txt](https://docs.goproxies.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.goproxies.com/proxies/self-service-dashboard/creating-subusers.md).
# Creating Subusers
### Intro
This article will explain how to create and manage subusers (also called API Proxy Users). These are accounts that you use to connect to the proxy itself.
### Accessing the Subusers Page
Navigate to the "Dashobard" tab on the self-service dashboard:
Press the Subusers button to access the subusers list.
This will open the My Subusers page. You can add up to 10 subusers per account.
Enter the username of your choice and press Create:
\
Make sure to copy the password that is generated in this window as it will not be displayed anywhere else! Afterward, either press “Add New Subuser” below to repeat the process and add a new one, or press “Back to My Subusers” to return to the subuser list:
Once you return to the list of subusers, you will now see your created API proxy user(-s). You may create up to 10 of these per account. Likewise, you may reset their password by pressing “Reset Password”, which will generate a new pop up with the newly reset password (which you will need to copy again before closing!):
Now you're ready to use the proxy users!
---
# 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.goproxies.com/proxies/self-service-dashboard/creating-subusers.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.