Skip to content
English
  • There are no suggestions because the search field is empty.

How do I save default integration settings for future Procore projects?

Admins can save a project's Procore integration settings as the default configuration template for future projects. This helps standardize setup across projects and reduces the need to manually configure the same settings every time a new project is linked.

What Are Default Settings?

Default Settings allow your company to define a standard Procore configuration that automatically applies to newly linked projects.

When a new project is mapped to Procore, SmartBarrel copies the saved default settings into the new project as its starting configuration.

These settings can include:

  • Daily Log sync preferences
  • Timecard settings
  • Cost code configuration
  • Workforce sync options
  • Approval requirements
  • Billing and quantity export settings
  • Other project-level integration preferences

How To Save Default Settings

  1. Open a project connected to Procore.
  2. Navigate to the project’s Integration Settings page.
  3. Configure the settings exactly how you want future projects to start.
  4. Select Make Default Settings.
  5. Confirm by selecting Save as default in the confirmation modal.

Any future projects linked to Procore automatically inherit those settings.

Important Notes

  1. Admin Only

    1. Only admin users can create or update default settings templates.

    2. Non-admin users do not see the Make Default Settings button.

  2. Existing Projects Are Not Updated

    1. Default settings only apply when a new project is linked.

    2. Updating the template later does not retroactively change settings on existing projects.

  3. Standard Save Still Works

    1. The existing Save button continues to save settings only for the current project.

    2. Make Default Settings is a separate action used to update the company-wide default template.

Why Use Default Settings?

Using default settings helps:

  • Reduce repetitive setup work
  • Keep project configurations consistent
  • Speed up onboarding for new projects
  • Minimize configuration errors across teams