Perforce Public Knowledge Base - Disabling Features in P4V
× PRODUCTS SOLUTIONS CUSTOMERS LEARN SUPPORT
Downloads Company Partners Careers Contact Free Trials
Menu Search
Perforce
Reset Search
 

 

Article

Disabling Features in P4V

« Go Back

Information

 
Problem
It is possible to limit the feature set available in P4V. 
There are various ways in which this can be achieved, some by the user themselves, others are done at an administrative level and impacting one or more users, groups of users, or everyone accessing the server instance.

P4V's "System Info" dialog, accessed from the Help menu, will indicate which features are currently enabled. 

'System Info' showing disabled features in P4V
Solution
A user can choose the features they want enabled in P4V's preferences. 

Enabling features in P4V's preferences

Note that settings disabled by an administrator cannot be re-enabled here by the user. 
Configuring P4V Preferences          

An administrator can control features using property settings; for example, to disable 'Streams' they can run this:
p4 property -a -n P4V.Features.Streams -v Off

and by including '-u userName' or '-g groupName' this can be applicable to either a user or a group. 

For more on P4V settings, please review Setting P4V preferences for your users and P4V 2013.1 Global Preferences

To control P4Swarm, the administrator would need to add the property 'P4.Swarm.URL' at least.


Some features can be added if using a centralized installation process - these are set in the 'p4vfeatures.xml' file in the P4VResources directory in P4V's installation directory. This is described here: Automated Deployment of Perforce and Automated Deployment Properties.


In addition to property settings, an administrator can create a 'central settings' file which is then used to define per-user and per-group logic relating to features, centrally-managed scripts and various other aspects of P4V's control. This is explained in more detail here: The Central Settings File


Finally, some features are determined by the existence of related entities, or the protections denying a user access to those entities. For example, if there is no 'unload' depot, then UnloadReload functionality is disabled. Similarly, if there is no Streams depot or a user's protections deny them access, then 'Streams' functionality will be disabled. 
Protections are covered here: Authorizing Access
Related Links

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255