Limitations with P4 authentication

Perforce TeamHub is integrated with P4 Server. If your TeamHub instance is configured to use P4 authentication, you can manage repositories and kick off reviews using the TeamHub user interface.

P4 authentication implies that part of the configuration and management happens in P4 Server. As a result, some elements in the TeamHub UI have been removed or disabled and others have been added, as detailed in the following table.

Entity	Change	P4 Server Documentation (where applicable)
Installation type	P4 authentication for Git is not supported by Perforce TeamHub Cloud plans. P4 authentication is only supported by TeamHub on-premise installations.
Collaborators	Removed the Collaborators view and ability to view or add collaborators in Team view	N/A
Bots	Disabled ability to change a bot's short name
Repositories	Added ability to: Create Git repositories stored in P4 Server. View P4 Server connection details (port and path) by selecting the Clone > Helix P4 option Removed ability to: Archive repositories Fork native Git repositories Rename Git repositories stored in P4 Server Create SVN, Mercurial, WebDav, Ivy, Maven, and Docker repositories Configure the garbage collection feature for Git repositories managed by P4 Server Git repositories managed by P4 Server do not require garbage collection because they do not store data on the disk where the TeamHub instance resides.
Company settings	Authentication tab: Disabled ability to configure SAML authentication With P4 authentication, TeamHub supports only one company per instance. Company creation is disabled.