Configuring P4V settings

Not every site (nor every user at every site) requires the full suite of functionality in P4V, the Helix Visual Client. By using the p4 property command, it is possible for a user with at least admin privileges to control which P4V features are available for a given site, group, or user. Properties relate to performance, features, and Helix Swarm integration. Performance- and feature-related properties set at the server level override local P4V settings. Some properties can only be set on the server side.

If you add or update a property while P4V is running, P4V requires a restart before the new value takes effect. P4V reads properties that control features once, at startup, from the Helix Server to which the user connects. For performance-related properties, if a user connects to a new Helix Server after P4V startup, P4V reloads the properties from the server most recently connected to.

For information about configuring settings locally in P4V, see the Helix Core Visual Client (P4V) Guide.

This section provides information about:

For more information on the p4 property command, see p4 property in the Helix Core Command-Line (P4) Reference.