Limitations with Helix authentication

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

Helix authentication implies that part of the configuration and management happens in Helix 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	Helix Server Documentation (where applicable)
Installation type	Helix authentication for Git is not supported by Helix TeamHub Cloud plans. Helix 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 Helix Server. View Helix 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 Helix Server Create SVN, Mercurial, WebDav, Ivy, Maven, and Docker repositories Configure the garbage collection feature for Git repositories managed by Helix Server Git repositories managed by Helix 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 Note With Helix authentication, TeamHub supports only one company per instance. Company creation is disabled.