.png)
Guardian’s Project Configurations is a powerful feature to configure and apply Guardian’s proactive protections to all of your project models. Project Configurations perform like templates, automatically applying Guardian’s protections when a new project model is registered. In addition, any change to the settings within a Project Configuration will automatically propagate to all models that have that Project Configuration applied. This provides live control of your project models.
Project Configurations can be found under the Settings button on the Revit ribbon. This is only available for Project and Company Administrators.
On the left side of the Project Configurations dialog is the list of Project Configurations created by your firm. For firms first starting to set up Guardian, only Company Default will be available. By utilizing the Add New, Rename, Delete, and Copy buttons along the bottom, new configurations can be created.
The star icon is used to set the default Project Configuration that is automatically applied when a new project is registered with Guardian that does not meet any of the existing Registration Rules.
While some firms establish a single Project Configuration for the entire firm, most will establish multiple Project Configurations that provide custom proactive protections for different disciplines, project typologies, regions, client standards, or even Project Configurations for Revit families.
Some firms use Project Configurations as the primary means for managing Guardian’s settings at the project level, while others utilize the Project Settings capabilities for project-level customizations.
Within each Project Configuration, a custom password can be created to provide Revit end-users with the ability to execute Custom Interactions and User Commands that have been set to the Prevent Protection Mode under that Project Configuration.
Allow Screenshots turns on the ability for Guardian to capture before and after screenshots for many of the Custom Interactions. These screenshots are available in Guardian’s Project Central and Guardian Backstage.
Each Project Configuration provides Last Modified information to keep track of who has edited the Project Configuration.
Custom Interactions are proactive protections based on specific workflows. As additional Custom Interactions are regularly being added, we have made it easy to filter all the various Custom Interactions.
User Commands are the proactive protections based on specific Revit commands. As there are over 100 User Commands, a search field is provided too quickly locate specific User Commands.
The Transactions tab provides customization on where and how Guardian keeps an eye on content that is loaded into your project model, ensuring non-compliant standards do not find their way into the project model.
Sync Properties allows you to sync all of the Project Properties with the company standards stored in Guardian Sync’s cloud repository.
Company Administrators can add Project Administrators, providing them with editing permissions to the Project Configuration. There are multiple strategies for applying and managing project model level customizations, and this allows the Project Administrator to customize this Project Configuration as they see fit for their project.
To note once again, a change in the Project Configuration will propagate to all projects registered under that Project Configuration, regardless of which project the Project Administrator is assigned to.
Once a Project Configuration is applied to a registered project, the settings can be customized on a model-by-model basis. All project model-specific customizations are made by selecting the Project Settings button.
Project Settings are available to all Company Administrators and only to the Project Administrator assigned to the project model. For a project model that has not been registered, the Project Settings button will be replaced with a Register Project button.
The Project Settings dialog looks similar to the Project Configurations dialog. A Project Administrator assigned to the project, or any Company Administrator, can customize any of these settings, and those settings will only be applied to the active project model. The active Project Configuration name will be displayed at the top (A).
As a Project Setting is customized, the text color changes to blue (B), indicating it has been changed specifically for the active project model. At the same time, text appears in the upper right-hand corner stating, “Indicates settings have been overridden.” This provides quick identification that settings have changed from the assigned Project Configuration.
Selecting Remove Overrides (C) will clear all project model-level changes and reconnect the Project Settings to the original Project Configuration. Guardian will prompt the Administrator to Reconnect to Project Configuration or Copy from Project Configuration to create a new Project Configuration based on the customized Project Settings.
The password for Prevent commands can be made unique for each project by selecting the Edit Password (D) button. Changing this password will also cause the Project Settings to be overwritten and disconnected from the applied Project Configuration.
Reach out to learn more, ask any questions, or meet the team! We'd love to learn more about your challenges and explore the more proactive solution.
