User Guide Procore Connect For RFIs

Procore Connect for RFIs allows connected projects to sync closed RFIs for permanent recordkeeping (Data Retention) and actively collaborate on live RFIs across accounts (Cross-Account Collaboration).

With the Cross-Account Collaboration feature in Open Beta, teams can initiate an RFI in a Receiving account, automatically generate a linked Draft RFI in the Sending account, and track live status updates, response changes, and attachments in real time across both web and mobile platforms (iOS and Android).

• Cross Account Collaboration: Initiate an RFI in a Receiving project, send it upstream, and automatically generate a linked Draft RFI in the Sending project.

  • Cross Account Collaboration automatically detects and requires all standard and custom fields required by the Receiving project. The Send button is blocked until all required fields are filled.

• Same-Tool Bi-Directional Workflows: A single project can act as both a Sender and a Receiver for the exact same tool across separate connections. This allows a project to receive items from a sending partner while simultaneously sending its own locally created items to receiving partners.

• Improved Visibility: Read-only copies of closed RFIs can be searched, exported to PDF, and included in reports.

• Data Ownership & Retention: Read-only copies of closed RFIs are retained permanently in your account, even if the connection is severed.

• Self-Service Management: Easily disable, re-enable, or reset your connections at any time without contacting support.

• Auto-Link RFI Revisions: Revisions auto-link when closed. Changes to draft, open, or manually linked RFIs do not auto-link, but every revision is tracked in the Change History of local and external RFIs

• Behavior & Data: Synced RFIs appear as read-only "External RFIs" in the receiving project. All closed RFIs copy over, the Question, Responses, Status, Key Dates, People/Contractors, Coversheet (PDF), Linked Drawings (PDF), and Attachments.

• Status Updates: If a closed RFI in the sending project is reopened or deleted, the change automatically syncs to the receiving project.

• Access Control: External RFIs live under a dedicated "External Items" tab. Access requires local RFI Admin rights or the "View External Items" granular permission (no access to the sending project is needed). Local RFI permissions govern visibility once synced.

• Sync Criteria for External Connections: For an RFI to sync to a Receving project, the connected user must meet both of the following requirements:

  • Permissions: Must be the RFI Creator, Manager, Assignee, or on the Distribution List.

  • Validation: Must be a validated connection via Connected Vendor.

    • Note: If both the Sending and Receiving projects belong to the same company account, private RFIs sync by default and do not require the specific permission or connection checks listed above.

• Disconnects: Severing a connection leaves all previously copied RFIs intact in the receiving project

Click here to return to Connection Manager Tutorials.