> For the complete documentation index, see [llms.txt](https://jollyproxy.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jollyproxy.gitbook.io/docs/feature-configuration/sub-accounts.md).
# Sub-Accounts
{% hint style="danger" icon="exclamation" %}
**Usage Notice**: All JollyProxy proxy products must be used in an overseas network environment. Please ensure that you have configured the corresponding overseas network environment yourself.
{% endhint %}
This article will explain how to add and manage sub-accounts on the **JollyProxy** platform.
### **I. Log In to the Proxy Platform**
1. Open your browser and visit the [JollyProxy official website](https://www.jollyproxy.com/zh-cn/login). Enter your account and password to log in to the system.
### **II. Create a Sub-Account**
1. **Go to the management page**: After logging in successfully, click **Sub-Accounts** in the left sidebar.
2. **Click Add**: Click the **New Sub-Account** button.
3. **Fill in the information**: In the pop-up editing window, fill in the following configurations according to your actual needs:
* **Account Name**: A custom name for easy identification
* **Password**: Set the login password for the sub-account
* **Enable Status**: Choose whether to enable the account immediately
* **Traffic Limit Setting**: Allocate a usable traffic quota for the sub-account
4. **Confirm the addition**: After filling in the information, click the **Confirm** button.
5. **View the result**: The system page will refresh and display the newly created sub-account information.
---
# 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://jollyproxy.gitbook.io/docs/feature-configuration/sub-accounts.md?ask=&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.
