P4 authentication prerequisites

Configuring Perforce TeamHub with P4 authentication requires specific setup in P4 Server. You need:

• An installation of the following products, each on its own dedicated computer:

  • Perforce TeamHub 2024.4 or later. The latest version is Perforce TeamHub 2025.3.1 Enterprise.

    We recommend at least 3-4 GB of memory and proper provisioning.

  • Perforce TeamHub works with supported versions of P4 Server (Standard Maintenance).

    The versions supported in this release of Perforce TeamHub are (latest patch of server version required):

    • P4 Server 2023.2

    • P4 Server 2024.1

    • P4 Server 2024.2

    • P4 Server 2025.1

    We recommend a server security level of 1 or higher. To learn more, see Server security levels in the P4 Server Administration Documentation.

  • Git Connector

    If Perforce TeamHub resides on the same computer as Git Connector, port conflicts occur. For best results, set up all 3 components on separate computers.

• A P4 Server license with the correct number of seats for your users, your gconn-user (Git Connector), and your Bots. For instructions on how to calculate the number of licensed seats you need, see Perforce TeamHub license.

• One P4 license seat to give TeamHub super level access to P4 Server with an optional unlimited timeout ticket if ticket-based authentication will be used (recommended). For more information, see Setting protections with p4 protect and Ticket-based authentication in P4 Server Administration Documentation.

• Host name, protocol, port, and user information for the Git Connector. For more information, see Work with Git in P4 Server Administration Documentation.

• Admin permission for the gconn-user on any manually created graph depots. See Grant permissions in P4 Server Administration Documentation.

• Users with appropriate access to P4 Server. All user and group administration occurs in P4 Server.

  Make sure that the names of P4 Server users that need access to Perforce TeamHub do not exceed 100 characters. TeamHub only supports usernames up to 100 characters.

• An entry in the protections table for all users who require access to TeamHub. To learn more, see Setting protections with p4 protect in the P4 Server Administration Documentation. The administrator needs superuser access to the protections table to view permissions.

• An access level of either admin or create-repo for users that need the ability to add repos in specific depots For more information, see p4 grant-permission in P4 CLI Reference.

High level architecture diagram

To get a better understanding of the underlying architecture, the following diagram gives a high-level overview of the architecture:

Installation and configuration flow

The following table outlines the flow of setting up P4 authentication in Perforce TeamHub and specifies the product it pertains to.

Step	Description	Product	Instructions
1.	Install Perforce TeamHub.	Perforce TeamHub	Installation
2.	If you start from a new P4 Server, add users and groups in P4 Server. For existing P4 Server installations, verify that the protections table includes the required entries for the users that need access to Perforce TeamHub.	P4 Server	Add users and groups in P4 Server P4 Server Administration Documentation: Managing users Granting access to groups of users Setting protections with p4 protect Ticket-based authentication P4 CLI Reference: p4 grant-permission command p4 group command p4 protect command
3.	Configure Perforce TeamHub to use P4 Server authentication.	Perforce TeamHub	Set up P4 Server authentication
4.	Install extensions on P4 Server to enable the activity stream in Perforce TeamHub.	Perforce TeamHub	Configuring P4 Server extensions
5.	Create a new project and repository.	Perforce TeamHub	Getting started Version control with Git
6.	Configure group access to the newly created project.	Perforce TeamHub	Add users and groups in P4 Server
7.	Clone the new repository to your local workspace.	Perforce TeamHub	Cloning a repository