Icons

P4V icons and badges represent P4 Server objects and their status. File icons appear throughout the interface, mostly in the Tree pane, and may include one or more badges to indicate file state or activity. Hover over a file to view a tooltip with detailed status information.

On this page:

File badges

Red badges indicate actions taken by you.
Blue badges indicate actions taken by another user.
Multiple badges can appear on the same file to show combined states.

Icon	Description
	You opened the file for add in your workspace
	You opened the file for delete
	You have the file checked out
	You have the file open for edit
	You have the file open for rename or move
	You have the file open for delete or move
	The workspace version is up to date
	You placed a global lock preventing others from editing the file
	Another user opened the file for add
	Another user opened the file for delete
	Another user has the file checked out
	Another user opened the file for edit
	Another user opened the file for rename or move
	Another user opened the file for delete or move
	The workspace version is not latest version
	Conflicting changes exist and must be resolved before the file can be submitted

File status icons

File status icons indicate the current state of the files in the depot.

When a user connected to an edge server locks a file, the lock is global and is promoted to the commit server. As a result, the locked status is visible to users connected to other edge servers and to the commit server.

A file remains locked until the file is submitted, reverted, or unlocked.

Icon	Description
	File is in the depot
	File is in the depot but not mapped to the current workspace view
	File in the workspace differs from the head revision
	File is in the workspace but not in the depot
	File is synced to the head revision
	File is synced to the previous revision
	File needs to be resolved
	File is locked by you
	File is globally locked by you and cannot be edited by others
	File is locked or globally locked by other user
	File is open for add by you
	File is open for add in another users' workspace
	File is open for edit by you
	File is open for edit by another user
	File is open for delete by you
	File is open for delete by another user
	File is deleted in depot
	File is open for rename/move
	File is open for rename/move
	File is open for branch
	File is open for branch by another user
	File is open for integration and does not require resolution
	File is open for integration and requires resolution
	File is open for integration by another user
	File is imported from another stream and cannot be submitted to the current stream, or it is shared from the parent stream of a sparse stream
	File is ditto-mapped to more than one directory in the workspace
	File is a placeholder and includes metadata only, not the file's content
	File is a symbolic link that points to another file or directory instead of containing its own content

Stream icons

Stream icons indicate stream status. To learn more about stream icons, see Streams icons and indicators.

Icon	Description
	Stream appears on the Streams tab. If the stream is deleted, the deleted icon is displayed.

Changelist icons

Changelist icons indicate the status and type of changelists. To learn more, see Submit (Check in) files.

Icon	Description
	Shelved file in a pending changelist A unit of versioned work that is not submitted. A changelist is created when you check out any file. A changelist is pending until you submit or revert the change.
	Shelved items
	Shelved items are globally accessible because they are promoted from the edge server to the commit server
	A pending changelist with at least one open file, such as the default changelist, which is listed first on the Pending changelists tab
	Pending changelist with an open stream and at least one open file
	Pending changelist with files to resolve
	Pending changelist with shelved files
	Pending changelist with 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

Folder icons

Folder icons indicatethe type of folder.

Icon	Description
	Folder in the P4 Server depot
	Folder in your client workspace
	Folder in a stream and stream depot. In this example, `D1` is a folder in the `//flow/D1` stream, which belongs to the `flow` stream depot.
	Folder that maps to a graph repo

Depot icons

Depot icons indicate the depot type and how files are stored and managed. To learn more about depot types and how to work with depots, see Work with depots in the P4 Server Administration Documentation.

Icon	Depot type	Description
	Local (classic) depot A repository of P4 files that is not streams-based. Uses the Perforce file revision model, not the graph model. The default depot name is depot. See also 'stream depot' and 'graph depot'.	A local depot is writable, and is the default depot type. Files reside in the P4 Server root directory and are managed directly by the server. By default, there is one local depot named depot on every P4 Server installation. To learn more, see Local depots in the P4 Server Administration Documentation.
	Stream depot	Where stream An enhanced type of branch with a dedicated view for clients of the stream (see 'stream view') and built-in rules that determine how changes flow across the stream depot (see 'stream hierarchy'). A stream specification defines a stream. In P4V, stream specs are visible in the Streams Graph and the Streams tab. files are stored. Stream specifications are represented in the Stream Graph and the Streams tab. To learn more about the Stream Graph, see Stream hierarchy in the Stream Graph, to learn more about the Streams tab, see View and add tabs.
	Remote depot	If configured by your P4 Server administrator, maps a portion of another P4 Server repository as if it is a depot. Typically used so that you can import and export third-party files without providing outsiders with access to your P4 Server.
	Spec depot	When enabled by your P4 Server administrator, stores the history of changes to P4 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, the submitter of the changelist, and the submitter's description of the changes. A changelist is the unit of versioned work..
	Graph depot	Stores files in a repo , which uses the graph model associated with Git instead of the classic P4 file revision model.

Workspace icons

Workspace icons help you identify the status and type of workspaces at a glance. To learn more, see Create and manage workspaces.

Icon	Description
	Workspace associated with a local (classic) depot
	Workspace associated with a stream depot
	Workspace with the stream spec checked out for edit
	Workspace associated with a graph depot, which could be a hybrid workspace A client workspace that supports both repos of type graph (see also 'Git Connector') and the classic P4 file revision model.

P4 Code Review icons

P4 Code Review icons indicate review status and activity. To learn more about P4 Code Review, see the P4 Code Review Documentation.

Icon	Description
	Pending changelist with shelved files in P4 Code Review
	Empty pending changelist with shelved files in P4 Code Review
	Submitted changelist with P4 Code Review
	Folder history, which shows P4 Code Review activity for all files in a folder. This lets you review changes at the folder level instead of per file.

Repo file icons

Repo file icons indicate file status in a repository. To learn more about repo files, see Repo file information.

Icon	Description
	Repo file is synced to headBlob and at headCommit
	Repo file is at headBlob but not at headCommit
	Repo file is not at headBlob and not at headCommit