p4 property
Add, delete, or list property values.
Syntax
p4 [g-opts] property -a -n name -v value [-s sequence] [-u user | -g group]
p4 [g-opts] property -d -n name [-s sequence] [-u user | -g group]
p4 [g-opts] property -l [-A] [-n name [-s sequence] [-u user | -g group]]
[-F filter] [-T taglist] [-m max]
Description
The p4 property command can be used by administrators to view and update property definitions stored in the P4 service. Administrators can also manage properties using the Properties tab in P4 Admin 2026.3 and later. The service does not use the property definitions directly. Instead, it provides this capability for client applications, such as P4V and P4 Code Review.
The P4 service offers three ways of storing metadata: counters/keys, attributes, and properties.
If your application requires only the flat storage of simple key/value
pairs, and attempts to implement no security model, use the p4 counters and p4 keys commands.
If your application’s metadata is associated with particular files, use
p4 attribute.
If your application’s metadata is not associated with files, and if you
have a requirement to restrict its visibility to users, groups, or to
control the precedence of multiple values using sequence numbers, use
p4 property.
When specifying multiple property values for the same property, use distinct sequence numbers to specify the precedence order. A value with a higher sequence number is ordered before a value with a lower sequence number. Values with the same sequence number have an undefined ordering relationship.
Some properies might be automatically set by an application, such as P4.Swarm.CommitURL. To learn more, see Commit-edge deployment in the P4 Code Review Documentation.
As of P4 Admin 2026.3, administrators can view, create, edit, and delete server properties from the Properties tab in P4 Admin. The p4 property command remains available for command-line and automation workflows.
Options
| Option | Description |
|---|---|
|
|
Update a property value, or add a property value if it is not
yet present. Requires |
|
|
List properties for all users and groups, as well as the
property sequence number of each property value. Requires
|
|
|
Delete a property value. Requires |
|
|
Limit the properties displayed to those that match the
|
|
|
Specify the user group to which this property applies. |
|
List one or more property values. Performance is substantially
improved when you supply a 2025.2 and later: The order of precedence for properties returned by Prior to 2025.2: A global scoped property took precedence over any user- or group-scoped properties with the same sequence number. The sequence number can be used to explicitly control the order. |
|
|
|
Limit output to the first max matching properties. |
|
|
Specify the name of the property. |
|
|
Specify the sequence number of the property. If not specified,
the default value is |
|
|
Limit the fields that are displayed to the fields listed in
|
|
|
Specify the user to whom this property applies. |
|
|
Specify the value of the property. |
|
|
See Global options. |
Usage notes
| Can file arguments use revision specifier? | Can file arguments use revision range? | Minimal access level required |
|---|---|---|
|
N/A |
N/A |
|
-
P4 Server administrators can centrally manage P4V performance settings and selectively enable or disable features by using either the
p4 propertycommand or the Properties tab in P4 Admin 2026.3 and later. See Server-side P4V settings in the P4 Server Administration Documentation.
Examples
To set a property:
p4 property -a -n P4V.Features.Markdown -v Off
To see a list of all the properties that have been set:
p4 property -l
To see a list of all the properties that have been set for a specific subset of properties:
p4 property -l -n P4V.Features
p4 property -l -n P4V.Performance