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

# Team License

> Project-based license for team collaboration

## Overview

A Team License provides shared access to Uniwind Pro for all members of an organization working on a specific project. Unlike Individual Licenses which are tied to a person, Team Licenses are tied to a project and can be used by any organization member.

<Info>
  Team Licenses are ideal for shared projects where multiple developers need access. All organization members can use the Team License without consuming their Individual License quota.
</Info>

## How It Works

1. **Create an organization** in your [dashboard](https://uniwind.dev/dashboard)
2. **Add team members** to your organization (minimum 2 active members required)
3. **Create a project** in your organization
4. **Generate a Team License** for that project

Any organization member can then authenticate and download Uniwind Pro using the Team License for that project.

## Download Limits

| Metric            | Limit                 |
| ----------------- | --------------------- |
| Monthly downloads | **1,000 per project** |
| Reset period      | 1st of each month     |

<Info>
  Each project gets its own 1,000 download limit. The limit is shared across all organization members using the Team License for that specific project.
</Info>

<Tip>
  Need higher limits? Contact [support@uniwind.dev](mailto:support@uniwind.dev) to discuss extended quotas for your team.
</Tip>

## Requirements

<Warning>
  Team Licenses require **at least 2 active members** in your organization. If membership falls below 2, existing Team Licenses will be automatically revoked.
</Warning>

To create a Team License, you need:

* Active Uniwind Pro subscription with 2+ seats
* An organization with at least 2 members with active Individual Licenses
* A project created in your organization

## Creating a Team License

1. Navigate to your [dashboard](https://uniwind.dev/dashboard)
2. Go to **Projects** and create a project (or select existing)
3. Go to **Licenses** section
4. Click **Add License**
5. Select **Team** license type
6. Choose the project to associate with the license
7. Click **Create**

<Tip>
  Project names must match the `name` field in your `package.json` exactly for the Team License to be recognized.
</Tip>

## Project Matching

Team Licenses are matched based on the `name` field in your `package.json`. The CLI reads the `package.json` from the directory containing the `node_modules` where `uniwind-pro` is installed.

```json package.json theme={null}
{
  "name": "my-awesome-app",  // This must match your project name in the dashboard
  "version": "1.0.0"
}
```

<Info>
  In monorepos, the location depends on where your package manager hoists `uniwind-pro`. If it's hoisted to the root `node_modules`, the root `package.json` name is used. If it's installed in a workspace's `node_modules`, that workspace's `package.json` name is used.
</Info>

<Warning>
  Make sure the project name in your dashboard matches exactly with the `name` field in your `package.json`. The matching is case-sensitive.
</Warning>

## License Priority

When downloading Uniwind Pro, the system checks licenses in this order:

1. **Team License** for the specific project (if available and has quota)
2. **Individual License** for the authenticated user (fallback)

This means team members automatically benefit from the higher Team License limits when working on licensed projects.

## Managing Team Licenses

From your dashboard, organization owners can:

* View Team License usage per project
* See which members are using the license
* Monitor download counts
* Revoke or recreate licenses

## Automatic Revocation

Team Licenses are automatically revoked when:

* Organization membership falls below 2 active members
* The associated project is deleted
* The subscription is canceled or expires
* Subscription seats are reduced below the required threshold

<Warning>
  When a Team License is revoked, the download usage at the time of revocation is preserved. If you recreate the license in the same billing period, usage carries over.
</Warning>

## Best Practices

<CardGroup cols={2}>
  <Card title="One license per project" icon="folder">
    Create separate Team Licenses for different projects to track usage independently.
  </Card>

  <Card title="Monitor usage" icon="chart-line">
    Check team usage regularly, especially for active projects with many contributors.
  </Card>

  <Card title="Combine with CI/CD" icon="server">
    Use Team Licenses for development, CI/CD License for automated builds.
  </Card>

  <Card title="Plan for growth" icon="arrow-up">
    If approaching limits, consider upgrading your subscription.
  </Card>
</CardGroup>

## Related

<CardGroup cols={2}>
  <Card title="Individual License" icon="user" href="/pro/individual-license">
    Personal license for individual developers
  </Card>

  <Card title="CI/CD License" icon="server" href="/pro/cicd-license">
    Automated pipeline access
  </Card>
</CardGroup>