P4V Documentation | 2025.1

# P4V icons

P4V uses a variety of icons and badges (decorations) to depict Helix Core Server objects and their status. The following table describes commonly encountered icons.

P4V displays file icons in the Tree pane and throughout the user interface, with file status indicated as shown in the following table. Note that file icons might be displayed with multiple "badges" (for example, check marks, lock indicators), each indicating an aspect of the file’s status. This table does not list all possible combinations. Note that red badges indicate actions taken by you, and blue badges indicate actions taken by another user.

To display a tooltip containing more details about a file’s status, hover the mouse pointer over the file. For example, this tooltip indicates another user has an "exclusive checkout" on the `variable.h` file:

Category | Icon | Description
--- | --- | ---
Files |  | File in depot
| File in depot but not mapped by workspace view
| File in workspace differs from head revision
| File in workspace but not in depot
| File synced to head revision
| File synced to previous revision
| File needs to be resolved
| File locked by you
| File globally locked by you
| File locked (or globally locked) by other user
| File open for add by you (red "+")
| File open for add in other workspace (blue "+")
| File open for edit by you (red check mark)
| File open for edit by other user (blue check mark)
| File open for delete by you (red "x")
| File open for delete by other user (blue "x")
| File deleted in depot
| File open for rename/move ("x" indicates source)
| File open for rename/move ("+" indicates target)
| File open for branch
| File open for branch by other user
| File open for integrate (no resolve needed)
| File open for integrate (will need resolve)
| File open for integrate by another user
| File imported from another stream (cannot be submitted to current stream), or file shared from the parent stream of a sparse stream.
| File is "ditto" mapped to more than one directory in the workspace
| File "placeholder" with metadata, not file content
| Symbolic link
Streams |  | Stream on the Streams tab. If deleted,
Repo Files |  | Repo file synced to headBlob and at headCommit
| Repo file at headBlob but not at headCommit
| Repo file not at headBlob and not at headCommit
Changelists |  | Shelved file in a pending changelist A changelist that has not been submitted.
| Shelved items
| Shelved items "globally" accessible because promoted from edge to commit
| A pending changelist with at least one open file, such as the default changelist, which is listed first on the Pending Changelists tab
| A pending changelist with an open stream and at least one open file
| Pending changelist has files that need resolve
| Pending changelist contains shelved files
| Pending changelist has no open files
| Pending changelist with an open stream but no open files
| Pending changelist with shelved files but no open files
| Pending changelist not associated with the current workspace or user, with or without open files
Folders |  | (Blue folder) A folder in the Helix Core Server depot
| (Yellow folder) A folder in your client workspace
| `D1` is a folder of the `//flow/D1` stream in the stream depot named `flow`.
| A folder that maps to a Graph repo
Depots |  | Classic depot A repository of Helix Core files that is not streams-based. Uses the Perforce file revision model, not the graph model. The default depot name is depot. See also default depot, stream depot, and graph depot.
| Stream depot: A depot where stream A branch with built-in rules that determine which changes to propagate to files in a stream depot, and in what order. A stream specification defines a stream. A user creates a stream spec by using the 'p4 stream' command or in P4V with File > New Stream. In P4V, stream specs are visible in the Streams Graph and the Streams tab. files are stored. (Stream specs are represented in the Stream Graph (see Stream hierarchy in the Stream Graph) and the Streams tab (see View and add tabs).
| Remote depot: if configured by your Helix Core Server administrator, a remote depot maps a portion of another Helix Core Server repository as if it were a depot. Typically used to enable you to import and export third-party files without providing outsiders with access to your Helix Core Server.
| Spec depot: when enabled by your Helix Core Server administrator, a spec depot stores the history of changes to Helix Core Server specifications, such as changelists The changes to files or stream specifications along with metadata, such as the list of changed files, their version numbers, who submitted the changelist to the depot, and the submitter's description of the changes. A changelist is the unit of versioned work. See also atomic change transaction and changelist number..
| Graph depot: A depot for storing files in a repo , which uses the graph model associated with git instead of the "classic" Perforce file revision model.
Workspaces |  | Workspace associated with a classic depot
| Workspace associated with a stream depot
| Workspace when stream spec is checked out for edit
| Workspace associated with a graph depot, which might or might not be a hybrid workspace A client workspace that supports both repos of type graph (see 'Git Connector') and the classic Helix Core file revision model.
Swarm |  | Pending changelist with shelved files in Swarm review
| Empty pending changelist with shelved files in Swarm review
| Submitted changelist with Swarm review
| Folder History with Swarm review

Your search for returned results