> ## Documentation Index
> Fetch the complete documentation index at: https://docs.datavendor.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Organizations and roles

> Organizations, their marketplace roles, their members, and the agreements and notifications that come with them.

Everything on DataVendor belongs to an **organization**, never a personal account: listings,
inventory, purchases, the wallet, and API keys. An organization is a HUD team, so the same team
works on the [HUD platform](https://docs.hud.ai).

## Marketplace roles

An organization chooses its role in organization setup, at **Sell data** or **Buy data**.

| Role | How you get it | What it opens |
| - | - | - |
| **Vendor** | Granted as soon as setup finishes | The vendor workspace: inventory, listings, estimations, sales, and earnings. See [Become a vendor](/sell/become-a-vendor). |
| **Buyer** | Join the waitlist; DataVendor invites you | The catalog, checkout, bids, purchases, and opportunities you post. See [Become a buyer](/buy/become-a-buyer). |

One organization can hold both roles. It then switches between its vendor and buyer views with the
**Vendor** and **Buyer** tabs at the bottom of the sidebar.

## Members and admins

Open **Settings → Members** to invite teammates with **Invite**, see **Pending invitations**, and
**Remove** people. Each member is a **Member** or a **Team admin**; a team admin can change another
person's role from the same list, but not their own.

Members work in the workspace on the organization's behalf: they manage inventory and listings,
browse, and collect purchases. Moving money or making a deal needs a team admin:

* buying, sample checkout, and placing or completing a bid;
* sending or cancelling an invoice, and saving billing details;
* accepting or rejecting a bid on your listing;
* converting earnings to credits and withdrawing them.

Members see those actions disabled with **Ask a team admin to complete this action.**

## The Mutual NDA

Each person accepts the [Mutual NDA](/overview/glossary#nda) before the workspace opens. Acceptance
belongs to the person, not the organization, so every member accepts it, and everyone accepts
again when a new version is published. Buyers and vendors accept the same NDA. You can read it at
[datavendor.ai/legal/mutual-nondisclosure-agreement](https://datavendor.ai/legal/mutual-nondisclosure-agreement).

## Agreements and documents

Signed paperwork is kept in two places, each with **Download** for a copy:

| Page | What it holds |
| - | - |
| **Settings → Agreements** | Agreements your organization signed, such as the Platform Access Agreement for [Tier 2](/sell/tiers), listed as **Tier upgrade agreement**. |
| **Settings → Documents** | Documents you accepted yourself, such as the Mutual NDA. |

## Notifications

The bell in the sidebar shows in-app notifications; **See all notifications** opens the full
list. They cover bids received, accepted, rejected, or withdrawn, new listings submitted to your
opportunities, and new or updated opportunities you can respond to.

Vendor organizations also get email at key moments: when vendor access or Tier 2 is granted, when
a listing goes live or fails quality checks, and when an opportunity you can see opens or closes.
After the first listing email of a day, the rest arrive as a digest the next morning (UTC).

## Vendor tiers

Vendor organizations also carry a tier, which decides whether they can see buyer opportunities.
See [Vendor tiers](/sell/tiers).

## More than one organization

Create another organization from the organization switcher with **Add organization**. Each one
goes through its own setup and holds its own roles, listings, and wallet.

## API keys

A team API key from [HUD Settings → API Keys](https://hud.ai/settings/api-keys) acts as the
organization on the buyer API, the vendor API, and the MCP server. See
[Using the API](/overview/api).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.