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.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.
How It Works
- Create an organization in your dashboard
- Add team members to your organization (minimum 2 active members required)
- Create a project in your organization
- Generate a Team License for that project
Download Limits
| Metric | Limit |
|---|---|
| Monthly downloads | 1,000 per project |
| Reset period | 1st of each month |
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.
Requirements
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
- Navigate to your dashboard
- Go to Projects and create a project (or select existing)
- Go to Licenses section
- Click Add License
- Select Team license type
- Choose the project to associate with the license
- Click Create
Project Matching
Team Licenses are matched based on thename field in your package.json. The CLI reads the package.json from the directory containing the node_modules where uniwind-pro is installed.
package.json
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.License Priority
When downloading Uniwind Pro, the system checks licenses in this order:- Team License for the specific project (if available and has quota)
- Individual License for the authenticated user (fallback)
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
Best Practices
One license per project
Create separate Team Licenses for different projects to track usage independently.
Monitor usage
Check team usage regularly, especially for active projects with many contributors.
Combine with CI/CD
Use Team Licenses for development, CI/CD License for automated builds.
Plan for growth
If approaching limits, consider upgrading your subscription.