TeamHub License
Every Helix TeamHub instance requires a license, which can be obtained by contacting Helix TeamHub Sales. The type of licenses and number of seats will depend on your installation, see License plan types and number of seats required.
- If required, you can reduce your active storage by deleting repositories, see Maintenance settings in the Helix TeamHub User Guide.
- When you delete content from your repositories:
- Helix Git repositories are versioned and track change history, repository data is not deleted from the Helix server.
- Git, Mercurial, and Subversion repositories are versioned and track change history. Files committed to the remote repository stay in the history even if you remove them. Those files continue to consume storage.
- Ivy, Maven, and WebDAV repositories are unversioned and do not track history. Removing files frees up storage.
- Docker repositories are unversioned and do not track history. Removing tags frees up storage.
Adding or updating the Helix TeamHub license file
To change the license, navigate to /admin URL of the Helix TeamHub installation, log in with the administrator account, and click Dashboard.
Click on Update license, paste the license contents, and hit Apply.
License plan types and number of seats required
This section will help you to decide what licenses you need and how many seats you need on each license. To buy or renew licenses, contact Helix TeamHub Sales.
Helix TeamHub Cloud license plan
Various seat and storage options are available for Helix TeamHub Cloud, see Pricing for Helix TeamHub on Perforce.com.
You cannot use Helix authentication for Git repositories with Helix TeamHub Cloud plans.
Helix TeamHub on-premise license plan
You must purchase enough seats on the license plan to cover all of your active Helix TeamHub Accounts. A seat is any individual account that logs in to Helix TeamHub, this includes user and collaborator accounts. For instructions on how to add or update your Helix TeamHub on-premise license plan, see Adding or updating the Helix TeamHub license file.
- Bots do not count against your Helix TeamHub license plan seats but each bot requires a background license. Request background licenses for your bots using the Background user request form on www.perforce.com.
- If you are using Helix authentication, all Git repositories are stored in the Helix server and you will also need Helix server licenses. To calculate the number of Helix server licenses you need, see Helix server license plan below.
Helix server license plan
If you are using Helix TeamHub Enterprise in conjunction with Helix authentication you also need a Helix server license. The number of seats required on Helix server license is:
Total number of seats on the Helix server license = Total number of Active Helix TeamHub Accounts (users and collaborators) + Total number of Helix TeamHub bots
For instructions on how to add or update your Helix server license plan, see Adding or updating the license file in the Helix Core Server Administrator Guide.
The Git Connector (gconn) user does not count against your Helix server license plan seats but it does require a background license. Request a background license for the Gconn user using the Background user request form on www.perforce.com.