Overwriting Setting on Projects

In this article

• Why you need Project Settings
• Customize Project Settings

Project Settings are controlled by the Project Settings button in the Guardian ribbon. This will look very similar to the Project Configurations with the exclusion of a few tabs. These tabs enable the Company/Project Administrator to customize the settings on a project level. Once a setting is changed, it will turn blue, indicating that company settings have been overridden.

Why you need Project Settings

We understand that you can’t predict the needs of each project. Whether it’s an advanced team that requires less direction or a schematic project phase with reduced stringency, Project Settings allows the Company Administrator to delegate customization to the individual project model level.  

Customize Project Settings

By default, projects will adopt when registered. The settings for each individual project can be overwritten through the Project Settings. It is important to note that once the settings for a project are overwritten, the settings for that project will no longer be affected by changes made to the applied Project Configuration.

Pro Tip: Project Settings automatically adopt the Project Configuration settings when the project model is registered. Setup the Project Configurations to the desired level of Guardian protections to be applied to all project models from the start.  

Project Settings can be accessed by Company or Project Administrators through the button shown in the ribbon.

When you open the dialog, you will see five familiar tabs:  

• Custom Interactions
• User Commands
• Command Frequency
• Transactions
• Guardian Sync

In each of these tabs, any settings that differs from the applied Project Configuration will show as blue (A). These can be settings that have been overwritten or ones where the Project Configuration had been changed after the project settings have been disconnected.

The Project Settings can be restored/reconnected back to the applied Project Configuration by using the Restore Defaults (B) button. When using this option, administrators will get two options:

• Reconnect to <Project Configuration>: This will reconnect the project to the applied Project Configuration. Any further changes to the Project Configuration will be reflected in this file.
• Copy from <Project Configuration>: This will copy the same settings over from the applied Project Configuration but will remain disconnected. Any further changes to the applied Project Configuration will not be adopted by this file.

The password for Prevent commands can be made unique for each project by selecting the Edit Password button (C). Changing this password will also cause the Project Settings to be overwritten and become disconnected from the applied Project Configuration.

Project Settings can also be accessed from the Projects dialog by selecting the Project Configuration button.

Additionally, the Project Settings of files that aren't open can be accessed by selecting a project in the list and clicking the applied Project Configuration.

Pro Tip: From the Projects dialog, multi-select models to edit the Project Settings of multiple models simultaneously. Many projects are made up of multiple models and this will allow the settings to be established congruently across all project models.