> For the complete documentation index, see [llms.txt](https://developers.oxylabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.oxylabs.io/dashboard/team-and-account-settings.md).
# Team & Account Settings
Manage your team members, account settings, and notification preferences in the Oxylabs Dashboard.
The **Settings** section is accessible from the Overview page and includes **Settings**, **Team**, and **Email notifications**.
From here you can:
* Change your password
* Select your region
* Manage team members
* Configure email notifications
## Team roles
Oxylabs Teams consist of two roles:
* **Team owner** – Manages the team, invites members, and controls subscriptions.
* **Team member** – Has access to dashboard features but cannot manage subscriptions or invite other members.
#### **Team member restrictions:**
* Only the team owner can add new members.
* Maximum of `50` active team members.
* Team members purchase subscriptions.
* A user with **Free plan** who joins a team loses their plan and gains access to the team's dashboard and products instead.
* A user with an active subscription must cancel it (under **Billing & Spending**) before joining a team.
* A user can belong to only one team at a time. To create a new team, they must first leave their current one.
## Inviting team members
1. Go to **Settings → Team**.
2. Click **+ Invite team member**.
3. Enter the teammate's email address and send the invitation.
The invitee receives an email invitation and, if they already have an account, a dashboard notification too. Once they accept, their status changes to **Active**. You can resend invitations or remove team members at any time.
### Team member onboarding
1. The invitee receives an email invitation.
2. Clicking **Accept invitation** takes them to the dashboard – they'll need to register first if they don't already have an account.
3. Once accepted, they get access to all dashboard features except subscription management and team invitations.
4. They can view their membership details, or leave the team at any time, under **Settings** → **Team**.
### Transferring team ownership
1. The current owner selects a new owner from the existing team.
2. They confirm the transfer in the dashboard and via email verification.
3. The new owner accepts via the dashboard or email.
Once complete, the new owner has full administrative control, and the previous owner becomes a regular team member.
## Email notifications
The email notification settings let you configure account-level alerts, plus the email addresses that should receive them. **Spending limit notifications** notify you as you approach and reach your overall monthly spending limit (e.g., at `50%`, `80%`, or `100%`).
{% hint style="info" %}
By default, `80%` and `100%` spending alerts are set. See [Product Instances](/dashboard/product-instances.md) for instance-level alert configuration (separate from these account-level alerts).
{% endhint %}
## Account verification
Oxylabs may require account verification as part of compliance and platform-security processes. If verification is needed, the team owner receives instructions in the dashboard for submitting the requested 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://developers.oxylabs.io/dashboard/team-and-account-settings.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.