Initial Setup: Project Customization

This article will explain the difference between the Company Settings and Project Settings. This will also discuss different scenarios in which using the Project Settings is more beneficial.

Company vs. Project

Project Configurations are adopted by project models when registered with Guardian. All changes made to the Project Configurations will affect any registered files with those applied configurations.  

Project Settings are customized overrides to the Project Configurations. Once changes are made to the Project Settings, they will become disconnected from the Project Configurations. Any further changes to the Project Configurations will no longer affect project models that have had their Project Settings modified.  

Pro Tip: Any differences between the Project Settings and the applied Project Configuration will appear as blue in the Project Settings.

Projects with customized settings can be reverted back to the applied Project Configuration by clicking Restore Defaults in the Project Settings window. When selected, you can choose to either reconnect to the Project Configuration or to copy the existing settings. When choosing to copy the settings, the Project Settings will remain disconnected from the Project Configuration.

When to Use Project Settings

Whether it’s an advanced team that requires less direction, junior teams requiring increased oversight, or a schematic project phase with reduced stringency, Project Settings allows the Company Administrator to delegate customization to the individual project model level. There are many reasons specific projects may require different settings to be applied and, thus, Guardian allows for this level of customization on a model-by-model basis.

Pro Tip: Testing new features and protections is best done through Project Settings so that it does not affect other registered files.