Perforce

Record your Perforce connection as version control evidence. Automated collection is not available for this provider yet.

Connect with an API token

1. In Perforce:

   1. Perforce P4 Server (Helix Core) has no web UI for API tokens; the credential is a login ticket obtained with the P4 command line.
   2. As the user Safeguard should connect as, run p4 login -a -p. -p displays the ticket instead of storing it in the local ticket file, and -a makes the ticket valid on all client workstations of this P4 Server.
   3. Copy the displayed ticket and paste it into the API token field.

   Where to find the other values:

   • Base URL (optional): The address of your P4 Server (the server and port your P4 clients connect to).
   • Account / Org / Workspace (optional): The P4 user name the ticket was issued for.

   Perforce issues this credential through its API or its support team, not through its admin screens.

   By default tickets are valid for 12 hours; an administrator can set a longer timeout for a group in the p4 group form, so use a dedicated service user in a group with a long ticket timeout. Least-privilege protections (p4 protect read access) were not verified from fetched docs. Use a read-only user.

   Source: help.perforce.com, checked 2026-10-07.

2. On Compliance › Connectors, open Perforce, click Connect, choose API token and fill in:

   Field	What to enter
   API token / Personal access token	Required. Stored encrypted and never shown again.
   Base URL (optional)	—
   Account / Org / Workspace (optional)	—

3. Click Connect with token.

Frameworks

No automated compliance test reads Perforce yet, so no framework lists it. How connectors provide evidence for frameworks: Frameworks and connectors.

Related

• Version Control connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks