Procore Integration: Overview
What the Procore integration does and how connected records move between Procore and LiveArch.
Overview
LiveArch helps architecture firms coordinate RFI and Submittal reviews with their consultant teams — without disrupting how the CM/GC already works in Procore. The integration syncs assigned RFIs, Submittals, prior replies, and attachments from Procore into LiveArch, where architects distribute items for review, collect consultant input, and prepare a well-coordinated final response. The result: a streamlined review process that sends Procore back exactly what it needs — a clear, actionable answer.
Setup and ongoing management are simpler for everyone involved: the integration app is transparent about exactly which permissions and capabilities it's requesting, so a Procore administrator always knows what they're approving — see Requested permissions on Installation for the full breakdown.
Start with Installation to connect a project, then see Linked RFIs and Linked Submittals for the day-to-day workflow rules.
Security-First Design
LiveArch's Procore connector uses OAuth together with a Procore Developer Managed Service Account (DMSA) — Procore's own recommended pattern for representing an integration. This removes the need to set up a shared Procore user account and distribute its email and password among team members. The DMSA creates a single project user, referred to throughout these docs as the LiveArch Integration user — assigning a Procore RFI or Submittal to this user is what routes it into LiveArch.
LiveArch connects to Procore only through Procore's own API, as an authorized application — every request LiveArch makes is checked by Procore against the permissions your company administrator approved, and Procore rejects anything outside that scope. In practice, this means LiveArch has no access to Procore's scheduling, budget, financial, daily-log, timesheet, or bidding tools, and cannot gain that access even if LiveArch itself were compromised or malfunctioning. See Requested permissions on Installation for the full list of what is granted.
This is defense in depth: LiveArch takes security seriously, but minimizes the permissions it requests regardless, and Procore ensures permissions are clear and pre-arranged, then enforces those restrictions at an API level.
Lifecycle of a Procore-Linked Record
Once a project is connected, we use Procore's built-in webhook architecture to notify LiveArch whenever an RFI or Submittal is issued or updated — no polling, no need to hit a manual trigger. Review can start immediately, instead of on the next sync cycle. And with API based communications, there's no manual re-entry on either side — the data arrives exactly as issued in Procore, with nothing retyped and no risk of transcribing incorrectly.
Everything in LiveArch is tracked, with intuitive predictive tools to help design teams stay ahead of issues and delays. Once a project is connected, the sync simply works in the background, with minimal administration. For the CM/GC, that also means an RFI or Submittal is never left waiting on a separate system for someone to notice it.
Keeping Everything in Sync
Real-time data syncing is only half the story; maintaining a clear source of truth between two systems is where LiveArch shines. Every externally linked record lands in read-only mirror tables first. What happens next depends on whether the record is new or a change to something already in-flight. New records cross into LiveArch's native tables right away. Everything else is flagged for reconciliation, keeping the user informed and in control before anything changes.
That separation protects the integrity of the design team's official record: external edits in Procore cannot silently overwrite LiveArch's content. It also removes a manual chore — nobody has to remember to periodically check Procore for changes, since anything that changes is surfaced automatically. This follows LiveArch's ethos of automating the busywork where it's safe, and requesting human judgment only where it is truly needed.
Support
Questions or issues? We're happy to help — , or use the contact form if you're signed out.