Update File Versions in a Project Model

Procore Model Manager - Beta Access & Feedback

The Model Manager (Beta) tool is exclusively available to registered beta participants. It is not available through Procore Explore. To learn more, see Beta Participant Guide.

  • To access the beta and provide feedback Show/Hide Details

    • To register: Participating companies must sign the Procore Beta Agreement. Once signed, your Procore Administrator coordinates with your Procore point of contact to enable Model Manager (Beta) on specific Procore projects.

    • To Provide Feedback During Beta: Contact your dedicated Beta program lead.

    • To report issues: Report breaking changes to Procore Customer Support. For general feedback or non-critical issues, contact your Beta program lead or Procore point of contact.

  • Notice: Procore Beta Services & Documentation Show/Hide Details

    For information about Beta Services, see the Procore Subscription Services Agreement. This documentation supports a product currently in Beta; content is actively being developed for General Availability (GA) and may be incomplete.

    • As-Is Basis: Provided solely for evaluation purposes on an "as is" basis.

    • No Warranties: Standard contractual commitments do not apply. This information carries no formal product commitments, and Procore assumes no liability for harm arising from its use.

    • Subject to Change: Procore may change, discontinue, or choose not to generally release these Beta Services at any time without notice.

Procore is finalizing functionality and documentation for general availability in the UK and Ireland (UKI). Please check back here for updates.

When design teams upload new revisions of discipline-specific files to your project's document repository (Document Management or Documents), Admins can update the project model to ensure all project stakeholders are coordinating against the latest 3D geometry.

There are two ways to update file versions:

  • Manual Update: Review available updates on the landing page and trigger re-federation on an as-needed basis.

  • Auto-Update: Mark the Auto-Update checkbox for specific model files to automatically re-federate the project model whenever a new eligible version is uploaded.

Things to Consider

  • Required User Permissions

  • Additional Information:

    • Manual Update. Displays an Update button on the landing page when a new version is detected in your project's document repository.

    • Auto-Update. Automatically triggers re-federation as soon as a new file version in an eligible status is uploaded.

Prerequisites

Steps

Manually Update File Versions

  1. Navigate to the Model Manager (Beta) tool.

  2. Go to the Appended Files card.

  3. Locate the file to update and review the Version Update column.

    • Update available: Click Update Project Model to start re-federation.

    • Latest Version: No button appears until a new file version is available in the document repository.

    • Failed: Check the status of your internet connection and try again.

Note

If you click Update on multiple files while a re-federation is running, the files enter a queue and process sequentially. You will be unable to add new files to the project model or view the previously model until the re-federation is complete.

You can add an entire folder of files to a project model at once. If your Documents tool has a folder structure, select the folder to add all its files in a single action. Any file already part of the project model is skipped automatically, only the new files are added.

Auto-Update File Versions

  1. Navigate to the Model Manager (Beta) tool.

  2. Go to the Appended Files card.

  3. Mark the Auto-Update check box next to any file you want to automatically re-federate.

Note

Once enabled, whenever a new version of the selected file is uploaded to Document Management or Documents in an eligible status, the system automatically triggers re-federation. For files in Document Management, Auto-Update still respects the configured federation status: if the new version's status isn't eligible, the federated model won't update until the file reaches an eligible status, even with Auto-Update turned on.

Tip

If an update fails, an error message appears and the original scene remains. Check your internet connection to ensure your connection isn't interrupted by a weak signal and try again.


Windows is a registered trademark of Microsoft Corporation in the United States and other countries. Google Chrome, Android, and Google Play are trademarks of Google LLC. iPhone, iPad, and App Store are trademarks or service marks of Apple Inc., registered in the U.S. and other countries and regions. iOS is a trademark or registered trademark of Cisco in the U.S. and other countries and is used under license by Apple Inc. Autodesk, AutoCAD, Civil 3D, Navisworks, and Revit are registered trademarks or trademarks of Autodesk, Inc., and/or its subsidiaries and/or affiliates in the USA and other countries. All other trademarks are the property of their respective owners.