> For the complete documentation index, see [llms.txt](https://help.proxidize.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.proxidize.com/account-and-billing/account-management/adding-sub-accounts-in-the-proxidize-dashboard.md).

# Adding Sub-Accounts in the Proxidize Dashboard

The Sub-Accounts feature allows you to grant team members access to your Proxidize dashboard and proxies using their own email addresses. This enables better collaboration, accountability, and separation of responsibilities when managing proxies as a team.

### Overview

With Sub-Accounts, you can:

* Allow multiple team members to access and manage proxies
* Maintain accountability by assigning access via individual email addresses
* Improve operational workflows (e.g., proxy monitoring, alerting)
* Enable email-based alerting for Proxy Builder setups

![](/files/04478b3572075ee50e58fcf1603eed92c64f94e8)

***

### Permissions & Limitations

#### Role Access

* All Sub-Users are assigned the role **“Proxy Manager”**
* This role provides **full access to the dashboard and proxies**, similar to the account owner

#### Restrictions

Sub-Users cannot:

* Access the **billing portal**
* Add or remove other sub-users

![](/files/a7c3f4a2b03cf6f847573eb714f6389b46b92d77)

***

### Important Requirement

Before creating a Sub-User:

* The email address **must not have been previously used** to create a Proxidize account
* If the user has already signed up before, they must **delete their existing account first.** For assistance, contact [**Proxidize Support**](mailto:support@proxidize.com)

***

## How to Create a Sub-User

{% stepper %}
{% step %}

### Step 1: Navigate to Account Settings

* Log in to your Proxidize dashboard.
* Go to [Account Settings](https://app.proxidize.com/settings/) by clicking on the Profile Icon on the top right of your screen.
* Click on **“Create User”**
  {% endstep %}

{% step %}

### Step 2: Enter User Details

* Fill in:
  * First Name
  * Last Name
  * Email Address
* Click **“Confirm”**

![](/files/e8b4569e9c310c1d59f276d3a8b6f45dc590938f)
{% endstep %}
{% endstepper %}

### What Happens Next (For the Sub-User)

#### Once the user is added

1. The user should go to the login page and enter their email address
2. They will receive a **6-digit verification code via email**
3. Enter the code to log in

#### First-Time Setup

After logging in, the user will need to:

* Complete their profile:
  * First Name
  * Last Name
  * Account Type
  * Organization details *(if applicable)*
* Accept all license agreements

***

### Best Practices

* Use Sub-Accounts to assign responsibilities across your team (e.g., monitoring, maintenance)
* Ensure each team member uses their own email for accountability
* Use email-based alerts effectively when managing Proxy Builder setups

***

### <mark style="color:$primary;">Need Help?</mark>

If you have any questions, concerns, or need further clarification, feel free to reach out to us via live chat or email us directly at **<support@proxidize.com>**.


---

# 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://help.proxidize.com/account-and-billing/account-management/adding-sub-accounts-in-the-proxidize-dashboard.md?ask=<question>&goal=<endgoal>
```

`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.
