> For the complete documentation index, see [llms.txt](https://docs.iproyal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.iproyal.com/proxies/residential/sub-users.md). # Sub-Users Our system's sub-user feature is a powerful tool designed to enable our users to become resellers, thereby opening up new business opportunities. By leveraging this feature, users are empowered to create and manage numerous sub-users, essentially setting up a network that can be offered to other parties. This feature not only facilitates the expansion of our users' service offerings but also allows them to establish and grow their own businesses. It's a seamless way for users to scale operations, diversify their business models, and explore new revenue streams by reselling access to sub-users. Users can easily manage their sub-users directly through our streamlined dashboard. This allows for quick adjustments and oversight of sub-user activities, ensuring the smooth operation of their reseller functions. {% content-ref url="/pages/mBCMOxxUALC0M6dRVj4r" %} [Sub-Users](/proxies/residential/dashboard/sub-users.md) {% endcontent-ref %} --- # 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.iproyal.com/proxies/residential/sub-users.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.