> For the complete documentation index, see [llms.txt](https://docs.dataimpulse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataimpulse.com/dashboard/team-management.md).

# Team Management

Invite your teammates to your DataImpulse account and give each of them the right level of access. Everyone gets their own login, so you never have to share your password.

With **Team**, several people can work in one DataImpulse account. Each teammate signs in with their own email and password, and sees only what their role allows. For example, your developer can work with proxies but never sees your payments, and your accountant can pay invoices but never sees proxy credentials.

You'll find it under **Profile → Team**.

{% embed url="<https://youtu.be/f752IMBCqPY>" %}

#### Roles

When you invite someone, you choose one of three roles. You can change it later.

| Role          | Who it's for                     | What they can do                                                                                               |
| ------------- | -------------------------------- | -------------------------------------------------------------------------------------------------------------- |
| **Admin**     | Managers, co-owners              | Full access, including billing, the reseller area and team management.                                         |
| **Billing**   | Finance, accounting              | Top-ups, payments, invoices and affiliate payouts, plus usage stats. No proxy credentials, no team management. |
| **Developer** | Engineers, scraping team members | Proxy access, proxy configuration, the API and SubUsers. No billing, no payments, no team management.          |

The person who created the account is the **Owner**. The Owner has full access and can't be removed from the team. The Owner isn't shown in the list of team members.

{% hint style="info" %}
You can have more than one Admin. Admins have the same access as the Owner, but the account itself still belongs to the Owner.
{% endhint %}

#### Invite a team member

1. Click your name in the top-right corner and choose **Profile**.
2. Open the **Team** tab.
3. Click **Invite team member**.
4. Enter your teammate's **Email**.
5. Choose a **Role**: Admin, Billing or Developer.
6. Click **Send invite**.

Your teammate appears in the list as **Pending registration** with the status **Invitation Sent**. Changed your mind? Click **Cancel** next to the invitation.

{% hint style="warning" %}
**Important: an email that already has a DataImpulse account can't join a team.**

If your teammate already has their own DataImpulse account, they can't become a team member with that email. Invite them with a different email address instead, one that isn't registered with DataImpulse.

If that doesn't work, [contact our support team](https://docs.dataimpulse.com/support.md) and we'll help you sort it out.
{% endhint %}

{% hint style="info" %}
Only the Owner and Admins can see the Team tab and invite people.
{% endhint %}

#### How your teammate joins

1. Your teammate gets an email titled **You are invited to join a DataImpulse team**. It shows who invited them, the team name and their role.
2. They click **Join the Team**. The link is valid for **48 hours**.
3. On the **Join Team** page, they see the team they're joining and their role. They enter their **Full name**, create a **Password**, confirm they are human and click **Get Started**. They can also click **Decline invitation** if they don't want to join.
4. Two-factor authentication is required for every team member. Each time they sign in, they enter the **6-digit code** we send to their email.

Once they've joined, their status in your list changes to **Active**.

#### Team member statuses

| Status              | What it means                                                               |
| ------------------- | --------------------------------------------------------------------------- |
| **Invitation Sent** | The invitation is on its way. Your teammate hasn't created their login yet. |
| **Active**          | Your teammate has joined and can sign in with their own login.              |

#### Change a role

1. In the **Team** tab, open the **Role** dropdown next to the teammate.
2. Choose the new role.
3. Click **Change role** to confirm.

Their access changes to match the new role.

#### Remove a team member

1. In the **Team** tab, click **Remove** next to the teammate.
2. Click **Remove** to confirm.

They are signed out right away and can no longer open your dashboard. You can invite them again later if you need to.

#### Who can do what

You can always see this table in the dashboard: open **Profile → Team** and expand **Roles and permissions** at the bottom of the page.

✅ allowed · — not available

**Main dashboard**

| Section                         | Owner | Admin | Billing | Developer |
| ------------------------------- | :---: | :---: | :-----: | :-------: |
| Dashboard (Usage)               |   ✅   |   ✅   |    ✅    |     ✅     |
| Plans (list)                    |   ✅   |   ✅   |    ✅    |     ✅     |
| Edit plan name                  |   ✅   |   ✅   |    —    |     ✅     |
| Proxy Access (credentials)      |   ✅   |   ✅   |    —    |     ✅     |
| Proxy Configuration             |   ✅   |   ✅   |    —    |     ✅     |
| Add new plan                    |   ✅   |   ✅   |    ✅    |     —     |
| Add GBs / Add Funds             |   ✅   |   ✅   |    ✅    |     —     |
| Payments (history, invoices)    |   ✅   |   ✅   |    ✅    |     —     |
| Affiliate (referrals & payouts) |   ✅   |   ✅   |    ✅    |     —     |
| Team (management)               |   ✅   |   ✅   |    —    |     —     |
| Integrations                    |   ✅   |   ✅   |    —    |     —     |
| Proxy Locations                 |   ✅   |   ✅   |    —    |     ✅     |
| Docs                            |   ✅   |   ✅   |    —    |     ✅     |
| Own Profile / Security          |   ✅   |   ✅   |    ✅    |     ✅     |

**Reseller area** (only for accounts in the [Reseller program](https://docs.dataimpulse.com/resellers.md))

| Section                      | Owner | Admin | Billing | Developer |
| ---------------------------- | :---: | :---: | :-----: | :-------: |
| API Management               |   ✅   |   ✅   |    —    |     ✅     |
| SubUsers                     |   ✅   |   ✅   |    —    |     ✅     |
| Deposit (reseller balance)   |   ✅   |   ✅   |    ✅    |     —     |
| Overview (Traffic Transfers) |   ✅   |   ✅   |    ✅    |     ✅     |

#### Good to know

* **No shared passwords.** Every teammate has their own login. When someone leaves, remove them, and the rest of the team doesn't need to change anything.
* **One account, one balance.** Plans, traffic and payments belong to your account. Teammates don't get separate plans or balances.
* **Team members are not SubUsers.** SubUsers in the Reseller program are your customers who get proxy access. Team members are people who work in your dashboard.
* **Deleting the account or changing the Owner's email** is done through our support team.

***

Have a question about your team setup? [Contact support](https://docs.dataimpulse.com/support.md), we're available 24/7.


---

# 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.dataimpulse.com/dashboard/team-management.md?ask=<question>&goal=<user_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.
