Contact our support team for more information.
A reference guide for clients who are familiar with Revit but new to Guardian. Terms are grouped by topic for easy navigation.
Company Administrator — The highest-level Guardian role, with full access to all settings, projects, and users across the entire firm. Company Administrators can create and manage all of Guardian’s Configurations (Project, Workset, Mapping), send company-wide messages, manage all registered models, and view all data in Guardian Backstage™ and Project Central.
Company ID — The unique identifier assigned to a firm's Guardian account. It is used to link Guardian installations across all users within the organization and appears in Company Settings.
Company Settings — The top-level settings area where Company Administrators configure company-level controls and commands, establish model registration rules and settings, enable Guardian Backstage data access, and manage administrators.
Enable Interactions for Administrators — A Guardian feature that allows administrators to temporarily view Guardian's behavior from an end-user's perspective, without needing to log out of their administrator account.
Guardian for Revit — A cloud-connected Revit add-in developed by ICONIC BIM that helps BIM teams automate standards, protect models, and educate end-users in real time. Guardian operates through the Revit ribbon and a cloud back end, enabling firmwide consistency without requiring users to leave Revit.
ICONIC BIM — The company behind Guardian for Revit. Founded in 2018 by AEC industry veterans, ICONIC BIM builds tools designed to bridge the gap between technology and the people using it.
Label Manager — A tool that allows Company Administrators to create and assign metadata labels to registered project models. Labels help organize models into structured data architecture and can be applied automatically or manually from the Registered Projects dialog.
Model Overrides — Model-level customizations that override a model's assigned Project Configuration. When settings are modified here, they apply only to that specific model and do not affect other projects using the same configuration. Changes appear in blue to indicate they have been overridden. Once a model override is applied, all settings are orphaned from the original Project Configuration unless overrides are removed.
Model Registration — The process of enrolling a Revit model with Guardian so it becomes "known" to the system. Once registered, Guardian begins tracking activity, applying protections, and enforcing standards for that file. Registration can be manual or triggered automatically using Registration Rules.
One-Time Password (OTP) — A single-use password generated by a Guardian administrator and shared with an end-user to grant temporary permission to proceed past a Prevent protection mode. Once entered, the password cannot be reused. OTPs allow administrators to grant exceptions on a case-by-case basis without permanently lowering the Protection Mode for a command.
Pausing Guardian — An option that temporarily suspends Guardian's active protections for the current session. Used when an administrator needs to perform work in a model without triggering protections. Pausing Guardian disables automatically after two hours.
Project Administrator — A Guardian role with editing and oversight permissions scoped to specific registered project models. Project Administrators can customize settings and send messages for their assigned projects and access Project Central for those models.
Project Groups — Organizational containers in Registered Projects that group related models together. For Autodesk Forma projects, grouping happens automatically based on the Forma Project ID. Custom groups can also be created manually.
Registered Projects — A dialog inside Revit that gives administrators a comprehensive, searchable view of all registered Revit models across the firm. Administrators can monitor who is working in models, track file size trends, apply labels, manage project groups, and quickly access Project Central or Model Settings for any registered file.
Registration Rules — Conditional rules that automatically register Revit models when they are opened or created, based on criteria such as file name, file location, or other properties. Each rule can assign default Mapping Configurations, Project Configurations, Workset Configurations, and Project Administrators. Manual registration rules can also be established.
Company Default — The Project Configuration that Guardian automatically applies when a new project is registered and no Model Registration Rule matches it. Every firm has at least one configuration, and one is always designated as the default.
Mapping Configurations — Named sets of saved mapping rules that act as Guardian's memory for standards automation. When an administrator maps one property to another (e.g., renaming a line style or redirecting a fill pattern), that rule is saved to the active Mapping Configuration. All projects assigned to that configuration automatically apply those same rules going forward. Multiple configurations can exist for different disciplines, project types, or client standards.
Model Settings — The per-model layer of customization that sits on top of an assigned Project Configuration, allowing project-specific adjustments without creating a separate configuration. These also include selection-based protections that work in conjunction with the rules-based protections.
Project Configurations — Named sets of Guardian settings that act like templates for how protections, Project Commands, Project Controls, and Transactions are applied to a project. A single configuration can govern many projects at once; any change made to the configuration automatically propagates to all models assigned to it. Most firms create multiple configurations for different disciplines or project types.
Rules — A broad term in Guardian referring to the conditional logic used across multiple features: Model Registration Rules (to auto-register files), Workset Rules (to assign elements to worksets), and Rules-based Protections (to control family loading). Rules use AND/OR condition logic and can reference file names, file locations, family categories, family names, and parameter values, etc.
Rules-Based Protections — A set of protections under Project Controls that utilizes conditional logic to protect commands or actions within Revit. These include Families and their Types, Instance Parameters, View Templates, View Filters, Deleting, Mirroring, Copying, Hiding and the Load of Families.
Workset Configurations — Named sets of standard worksets and associated automation rules, managed by Guardian. When worksharing is enabled in a project, users are prompted to select a Workset Configuration to apply. Rules within each configuration can automatically assign modeled elements to the correct workset in real time as they are placed.
Workset Rules — Conditional logic within a Workset Configuration that automatically places elements onto specific worksets based on category, parameter value, family name, family type, or linked file name. Rules run automatically as elements are placed or can be run manually using the "Run All Rules" button.
Company Commands — Guardian's primary protection layer, tied to specific Revit commands (such as Explode CAD, Delete, Mirror, and Load Family). For each command, administrators set up a Protection Mode and apply a custom Command Message to educate users at the moment of action. All native Revit postable commands are available. Company Commands can be configured at the Company Settings level (for commands accessible without a model opened).
Command Frequency — A setting within each User Command that controls how often an end-user sees the same Command Message. Options include: Every Time, Once Per Session, Every 3 Days, or Every 7 Days. Users can optionally be given control to self-select this frequency.
Command Messages — The customizable in-Revit dialogs that appear when a User Command or Custom Interaction is triggered at the Guide or Prevent level. Administrators write the message content in rich text format and can include images, hyperlinks to training resources. Each message communicates the firm's processes, best practices, and standards and explains the "why" behind a restriction.
Copy and Array Protections — A Custom Interaction rules-based protection applied to Revit's Copy and Array commands, used to protect the duplication of elements that should remain single instances.
Delete Protections — A Custom Interaction rules-based protection applied to Revit's Delete command, providing protection when users attempt to delete elements that may be governed by firm standards.
Family Protections — A Custom Interaction rules-based protection that prevents end-users from loading a family of the same name that already exists in the project, protecting the integrity of the existing family.
Family Type Protections — A Custom Interaction rules-based and Model Settings selection-based protection that protects end-users from modifying or deleting specific family types within the model, protecting carefully maintained type libraries.
Group Protections — A Custom Interaction rules-based protection that protects the creation, modification, or deletion of Revit Groups within the model.
Guardian Messages — A broadcast messaging feature that allows administrators to send rich-text messages directly to Revit users — either to all company users, a project group, or a specific project. Messages appear as in-app prompts in Revit and are also viewable in Project Central. Used for critical updates, onboarding, and project announcements.
Hiding in View Protections — A Custom Interaction rules-based protection applied when users attempt to hide elements in a Revit view, helping prevent unintentional or undocumented graphic overrides.
Load Family Protections — A feature that controls where end-users can load Revit families from, and what happens when families come from unapproved locations. Rules are created to define approved file paths or conditions; families loaded from outside those sources trigger a customizable Command Message and can optionally invoke property scanning and mapping.
Mirror Protections — A Custom Interaction rules-based and Model Settings selection-based protection applied to Revit's Mirror command. Mirroring certain families can cause coordination problems.
Parameter Prompts — A feature that prompts end-users to fill in selected instance parameter values immediately after placing an element in the model. This ensures data is captured in real time and prevents information from being entered inconsistently or missed entirely.
Pin Protections — An enhancement to Revit's native pin command that adds Guardian protection to pinned elements. When a user attempts to unpin a protected element, a Command Message is displayed; the Prevent mode requires a password. Any element that supports native pinning (grids, levels, viewports, linked files, etc.) can have a Pin Protection applied.
Project Controls — Workflow-specific protections that go beyond individual Revit commands. Project Controls cover targeted scenarios such as enabling worksharing, loading families from unapproved sources, mirroring elements, and more. They are configured within Project Configurations under the Project Controls tab.
Project Commands — Guardian's primary protection layer, tied to specific Revit commands (such as Explode CAD, Delete, Mirror, and Load Family). For each command, administrators set up a Protection Mode and apply a custom Command Message to educate users at the moment of action. All native Revit postable commands are available. Project Commands can be configured at the Project Configuration level (for commands accessible while a model is open).
Protection Mode — The overarching setting that determines the appropriate Guardian protection level when an end-user performs a protected action. There are three levels:
Revit Warning Tracking Protections — A Custom Interaction that provides Guardian protection modes and categorizes Revit warnings generated by users. Administrators can set priority levels for specific warning types; warning data is visible in Project Central and Backstage for trend analysis.
Rules-Based Protections – A set of protections under Project Controls that utilizes conditional logic to protect commands or actions within Revit. These include Families and their Types, Instance Parameters, View Templates, View Filters, Deleting, Mirroring, Copying, Hiding and the Load of Families.
Selection-Based Protection – A set of protections found under the Model Settings dropdown that provide protections on individual elements within the model. These include Families and their Types, View Templates, View Filters, Mirroring, and Pins.
Sync Traffic Control™ (STC) — A Guardian feature that manages the Synchronize with Central process across teams. Sync Traffic Control monitors who is syncing at any given moment, prevents simultaneous sync conflicts, queues users, and sends customizable sync reminders. Administrators can also trigger reminders manually from Project Central, and Guardian can be configured to sync automatically for users who forget.
User Overrides — An administrator tool used to reset a specific user's command frequency settings back to the default. Useful when a user has dismissed or silenced a Command Message they should still be receiving. Overrides can also be preset by the administrator.
View Filter Protections — A Custom Interaction rules-based and Model Settings selection-based protection that protects end-users from modifying, deleting, or overriding Revit View Filters in the project.
View Template Protections — A Custom Interaction rules-based and Model Settings selection-based protection that protects end-users from making changes to Revit View Templates, preserving standardized view settings across the project.
Content Car Wash — A term used by Guardian to describe its end-to-end workflow for cleaning non-standard content — whether a family file, a template, or a project model — by running Mapping Configuration rules to standardize all properties to the firm's defined standards.
Family Mapping — A specific type of mapping rule that redirects one Revit family to another. If the target family already exists in the project, Guardian converts all instances of the source family to the target. If it does not exist, the source family is simply renamed.
Guardian Sync Properties™ — A cloud-based feature that stores a firm's standard Revit properties (Fill Patterns, Line Patterns, Object Styles, etc.) in the cloud and keeps them synchronized across all projects. Properties uploaded to the cloud can be automatically or manually pushed to any project regardless of Revit version. Guardian tracks sync status so administrators can identify when a project property has drifted from the cloud standard.
Incoming Properties — Guardian’s standards engine and dialog for cleaning and aligning Revit's native properties when content is loaded into a project. The Incoming Properties dialog provides the mapping of the incoming properties similar to Model Properties. Administrators can map, rename, or remove these properties; end-users see a simplified version based on their Transaction settings.
Mapping Rules — Individual instructions stored within a Mapping Configuration that tell Guardian to rename a property, convert one property to another, or remove an unused property. When incoming content is loaded into a project, Guardian silently applies all applicable rules in the background.
Model Properties — Guardian’s standards engine and dialog for cleaning and aligning Revit's native properties (Fill Patterns, Line Patterns, Object Styles, etc.) on the model level, presented through a unified interface that also includes history tracking, Guardian Sync Properties status indicators, and mapping capabilities. Administrators use Model Properties to identify non-standard content and apply Mapping Rules.
Out of Sync Property — A property in a project model that was previously synchronized with a cloud standard in Guardian Sync Properties, but has since diverged — either because the project version was modified locally or the cloud standard was updated. The property is flagged visually, and administrators can choose to pull the cloud version down or push the project version up.
Shared Parameter Mapping — A mapping rule type that maps a shared parameter to the equivalent shared parameter, ensuring data fields align correctly across projects.
Transactions — Guardian's mechanism for identifying and controlling how it processes incoming Revit content (families, files pasted from other models, exploded CAD, etc.) at the moment it enters a project. Transactions define the end-user experience: Silent Mode processes mappings automatically in the background; Show Dialogs options present the user with the Incoming Properties dialog to manually review and map properties.
Activity Feed — A section of Project Central that shows a chronological, real-time log of all Guardian-tracked events in the project: Project Commands triggered, Transactions completed, Revit warnings generated, and Sync Traffic Control events. Each entry is color-coded by severity and Protection Mode level.
File Size Indicator — A visual indicator in Registered Projects that shows whether a model's file size is growing, shrinking, or staying stable, based on a rolling six-week history. Hovering over the indicator shows the exact percentage change.
Guardian Backstage™ — Guardian's data analytics platform, accessed via Microsoft Power BI or other compatible data tools. Backstage connects to an Azure-based database that aggregates activity captured from all registered projects, providing dashboards on user sessions, sync habits, command usage, Revit warnings, family loading activity, model file sizes, and mapping automation. Data is refreshed approximately every three hours.
Project Central — A real-time project dashboard built directly into Revit, accessible from the ribbon and Registered Projects. It gives administrators a live view of activity within a registered model, including user sessions, sync timelines, Revit warnings, command activity, Guardian Messages, and a "Project at a Glance" summary of items like unpinned protected elements, in-place families, mirrored elements, and groups without names.
Project Sessions — A timeline view in Project Central that visualizes how long each user has had the project model open during a session. Vertical dotted lines indicate sync events; lines that end without a marker may indicate a crash or closure without syncing.
Time to Open / Time to Sync — Performance metrics tracked by Guardian for every project open and every sync event. Longer-than-expected times for all users suggest model performance issues; outliers for individual users may point to hardware or network problems.
Standard Revit and BIM concepts that frequently appear in Guardian workflows. Included here for clients who may be newer to Revit terminology.
Autodesk Forma — Autodesk's cloud platform for BIM collaboration and data management, formerly known as Autodesk Construction Cloud (ACC). Guardian integrates with Forma by automatically grouping models based on their Forma Project ID and recognizing Forma-hosted files in Registered Projects.
Central File — The master copy of a workshared Revit model, stored on a shared server or cloud platform (such as Forma). All team members' local copies sync their changes back to the Central File.
Family — A Revit component file (.rfa) that defines a category of building element — such as a door, window, structural column, or light fixture. Families contain type parameters that define variations (e.g., different sizes) and instance parameters that can be set individually per placement.
Fill Patterns — Hatch patterns applied to surfaces in Revit to represent materials or element types in plan, section, or 3D views (e.g., concrete crosshatch, insulation batt). Fill patterns are a type of Model Property managed and standardized by Guardian Sync Properties.
In-Place Family — A family created directly within a project model rather than as a standalone .rfa file. In-place families are generally discouraged because each instance is treated as an individual file, significantly increasing the model file size over an equivalent loadable Revit family. Guardian's Project at a Glance flags in-place families for administrator review.
Line Patterns — Repeating dash-and-gap sequences applied to lines, edges, and curves in Revit to represent different element types graphically (e.g., hidden, centerline, dashed). Line patterns are a type of Model Property managed and standardized by Guardian.
Object Styles — Revit's global settings that control the default appearance (line weight, line color, line pattern, and material) for every category of Revit element. Object Styles and subcategories are a key Model Property that Guardian tracks and can standardize across projects.
Revit Warnings — Notifications generated by Revit when model conditions conflict with its internal rules (e.g., overlapping walls, room not enclosed, elements slightly off-axis). Warnings do not prevent work but can accumulate and affect model performance. Guardian's Revit Warning Tracking Protections monitors and categorizes warnings so administrators can identify problem areas early.
Shared Parameters — Custom parameters defined in an external shared parameter file (.txt) that can be used consistently across multiple Revit families and projects. Shared parameters ensure that data fields carry the same definition, enabling reliable scheduling and data export. Guardian's Shared Parameter Mapping ensures incoming families use the firm's standard shared parameter definitions.
Synchronize with Central (SWC) — The Revit command used to save a user's local changes back to the Central File and pull in changes made by other team members. Regular synchronization is critical for team coordination and model stability. Guardian Sync Traffic Control helps manage this process across large teams.
System Family — A Revit family that is built into the software and cannot be loaded as an external .rfa file. Examples include walls, floors, roofs, ceilings, stairs, and railings. Their types are controlled through Type Properties and exist within the project file itself.
View Filters — Revit rules applied to views that configure the appearance of elements based on parameter values (e.g., highlight all walls with a fire rating). Guardian's View Filter Protections prevent end-users from modifying filters that administrators have defined as standards.
View Templates — Saved sets of view properties (scale, detail level, visibility/graphics overrides, filters) that can be applied consistently across multiple views. Guardian's View Template Protections prevent users from overriding or deleting standard view templates.
Worksets — Subdivisions within a workshared Revit model that control which elements different team members own or can edit. Common worksets include categories like Exterior Shell, Interior, Structure, Linked Files, and Shared Levels and Grids.
Worksharing — A Revit collaboration method that enables multiple users to work simultaneously in the same model file by dividing it into worksets. Enabling worksharing creates a Central File and allows team members to check out and work on specific portions of the model.
Contact our support team for more information.
A reference guide for clients who are familiar with Revit but new to Guardian. Terms are grouped by topic for easy navigation.
Company Administrator — The highest-level Guardian role, with full access to all settings, projects, and users across the entire firm. Company Administrators can create and manage all of Guardian’s Configurations (Project, Workset, Mapping), send company-wide messages, manage all registered models, and view all data in Guardian Backstage™ and Project Central.
Company ID — The unique identifier assigned to a firm's Guardian account. It is used to link Guardian installations across all users within the organization and appears in Company Settings.
Company Settings — The top-level settings area where Company Administrators configure company-level controls and commands, establish model registration rules and settings, enable Guardian Backstage data access, and manage administrators.
Enable Interactions for Administrators — A Guardian feature that allows administrators to temporarily view Guardian's behavior from an end-user's perspective, without needing to log out of their administrator account.
Guardian for Revit — A cloud-connected Revit add-in developed by ICONIC BIM that helps BIM teams automate standards, protect models, and educate end-users in real time. Guardian operates through the Revit ribbon and a cloud back end, enabling firmwide consistency without requiring users to leave Revit.
ICONIC BIM — The company behind Guardian for Revit. Founded in 2018 by AEC industry veterans, ICONIC BIM builds tools designed to bridge the gap between technology and the people using it.
Label Manager — A tool that allows Company Administrators to create and assign metadata labels to registered project models. Labels help organize models into structured data architecture and can be applied automatically or manually from the Registered Projects dialog.
Model Overrides — Model-level customizations that override a model's assigned Project Configuration. When settings are modified here, they apply only to that specific model and do not affect other projects using the same configuration. Changes appear in blue to indicate they have been overridden. Once a model override is applied, all settings are orphaned from the original Project Configuration unless overrides are removed.
Model Registration — The process of enrolling a Revit model with Guardian so it becomes "known" to the system. Once registered, Guardian begins tracking activity, applying protections, and enforcing standards for that file. Registration can be manual or triggered automatically using Registration Rules.
One-Time Password (OTP) — A single-use password generated by a Guardian administrator and shared with an end-user to grant temporary permission to proceed past a Prevent protection mode. Once entered, the password cannot be reused. OTPs allow administrators to grant exceptions on a case-by-case basis without permanently lowering the Protection Mode for a command.
Pausing Guardian — An option that temporarily suspends Guardian's active protections for the current session. Used when an administrator needs to perform work in a model without triggering protections. Pausing Guardian disables automatically after two hours.
Project Administrator — A Guardian role with editing and oversight permissions scoped to specific registered project models. Project Administrators can customize settings and send messages for their assigned projects and access Project Central for those models.
Project Groups — Organizational containers in Registered Projects that group related models together. For Autodesk Forma projects, grouping happens automatically based on the Forma Project ID. Custom groups can also be created manually.
Registered Projects — A dialog inside Revit that gives administrators a comprehensive, searchable view of all registered Revit models across the firm. Administrators can monitor who is working in models, track file size trends, apply labels, manage project groups, and quickly access Project Central or Model Settings for any registered file.
Registration Rules — Conditional rules that automatically register Revit models when they are opened or created, based on criteria such as file name, file location, or other properties. Each rule can assign default Mapping Configurations, Project Configurations, Workset Configurations, and Project Administrators. Manual registration rules can also be established.
Company Default — The Project Configuration that Guardian automatically applies when a new project is registered and no Model Registration Rule matches it. Every firm has at least one configuration, and one is always designated as the default.
Mapping Configurations — Named sets of saved mapping rules that act as Guardian's memory for standards automation. When an administrator maps one property to another (e.g., renaming a line style or redirecting a fill pattern), that rule is saved to the active Mapping Configuration. All projects assigned to that configuration automatically apply those same rules going forward. Multiple configurations can exist for different disciplines, project types, or client standards.
Model Settings — The per-model layer of customization that sits on top of an assigned Project Configuration, allowing project-specific adjustments without creating a separate configuration. These also include selection-based protections that work in conjunction with the rules-based protections.
Project Configurations — Named sets of Guardian settings that act like templates for how protections, Project Commands, Project Controls, and Transactions are applied to a project. A single configuration can govern many projects at once; any change made to the configuration automatically propagates to all models assigned to it. Most firms create multiple configurations for different disciplines or project types.
Rules — A broad term in Guardian referring to the conditional logic used across multiple features: Model Registration Rules (to auto-register files), Workset Rules (to assign elements to worksets), and Rules-based Protections (to control family loading). Rules use AND/OR condition logic and can reference file names, file locations, family categories, family names, and parameter values, etc.
Rules-Based Protections — A set of protections under Project Controls that utilizes conditional logic to protect commands or actions within Revit. These include Families and their Types, Instance Parameters, View Templates, View Filters, Deleting, Mirroring, Copying, Hiding and the Load of Families.
Workset Configurations — Named sets of standard worksets and associated automation rules, managed by Guardian. When worksharing is enabled in a project, users are prompted to select a Workset Configuration to apply. Rules within each configuration can automatically assign modeled elements to the correct workset in real time as they are placed.
Workset Rules — Conditional logic within a Workset Configuration that automatically places elements onto specific worksets based on category, parameter value, family name, family type, or linked file name. Rules run automatically as elements are placed or can be run manually using the "Run All Rules" button.
Company Commands — Guardian's primary protection layer, tied to specific Revit commands (such as Explode CAD, Delete, Mirror, and Load Family). For each command, administrators set up a Protection Mode and apply a custom Command Message to educate users at the moment of action. All native Revit postable commands are available. Company Commands can be configured at the Company Settings level (for commands accessible without a model opened).
Command Frequency — A setting within each User Command that controls how often an end-user sees the same Command Message. Options include: Every Time, Once Per Session, Every 3 Days, or Every 7 Days. Users can optionally be given control to self-select this frequency.
Command Messages — The customizable in-Revit dialogs that appear when a User Command or Custom Interaction is triggered at the Guide or Prevent level. Administrators write the message content in rich text format and can include images, hyperlinks to training resources. Each message communicates the firm's processes, best practices, and standards and explains the "why" behind a restriction.
Copy and Array Protections — A Custom Interaction rules-based protection applied to Revit's Copy and Array commands, used to protect the duplication of elements that should remain single instances.
Delete Protections — A Custom Interaction rules-based protection applied to Revit's Delete command, providing protection when users attempt to delete elements that may be governed by firm standards.
Family Protections — A Custom Interaction rules-based protection that prevents end-users from loading a family of the same name that already exists in the project, protecting the integrity of the existing family.
Family Type Protections — A Custom Interaction rules-based and Model Settings selection-based protection that protects end-users from modifying or deleting specific family types within the model, protecting carefully maintained type libraries.
Group Protections — A Custom Interaction rules-based protection that protects the creation, modification, or deletion of Revit Groups within the model.
Guardian Messages — A broadcast messaging feature that allows administrators to send rich-text messages directly to Revit users — either to all company users, a project group, or a specific project. Messages appear as in-app prompts in Revit and are also viewable in Project Central. Used for critical updates, onboarding, and project announcements.
Hiding in View Protections — A Custom Interaction rules-based protection applied when users attempt to hide elements in a Revit view, helping prevent unintentional or undocumented graphic overrides.
Load Family Protections — A feature that controls where end-users can load Revit families from, and what happens when families come from unapproved locations. Rules are created to define approved file paths or conditions; families loaded from outside those sources trigger a customizable Command Message and can optionally invoke property scanning and mapping.
Mirror Protections — A Custom Interaction rules-based and Model Settings selection-based protection applied to Revit's Mirror command. Mirroring certain families can cause coordination problems.
Parameter Prompts — A feature that prompts end-users to fill in selected instance parameter values immediately after placing an element in the model. This ensures data is captured in real time and prevents information from being entered inconsistently or missed entirely.
Pin Protections — An enhancement to Revit's native pin command that adds Guardian protection to pinned elements. When a user attempts to unpin a protected element, a Command Message is displayed; the Prevent mode requires a password. Any element that supports native pinning (grids, levels, viewports, linked files, etc.) can have a Pin Protection applied.
Project Controls — Workflow-specific protections that go beyond individual Revit commands. Project Controls cover targeted scenarios such as enabling worksharing, loading families from unapproved sources, mirroring elements, and more. They are configured within Project Configurations under the Project Controls tab.
Project Commands — Guardian's primary protection layer, tied to specific Revit commands (such as Explode CAD, Delete, Mirror, and Load Family). For each command, administrators set up a Protection Mode and apply a custom Command Message to educate users at the moment of action. All native Revit postable commands are available. Project Commands can be configured at the Project Configuration level (for commands accessible while a model is open).
Protection Mode — The overarching setting that determines the appropriate Guardian protection level when an end-user performs a protected action. There are three levels:
Revit Warning Tracking Protections — A Custom Interaction that provides Guardian protection modes and categorizes Revit warnings generated by users. Administrators can set priority levels for specific warning types; warning data is visible in Project Central and Backstage for trend analysis.
Rules-Based Protections – A set of protections under Project Controls that utilizes conditional logic to protect commands or actions within Revit. These include Families and their Types, Instance Parameters, View Templates, View Filters, Deleting, Mirroring, Copying, Hiding and the Load of Families.
Selection-Based Protection – A set of protections found under the Model Settings dropdown that provide protections on individual elements within the model. These include Families and their Types, View Templates, View Filters, Mirroring, and Pins.
Sync Traffic Control™ (STC) — A Guardian feature that manages the Synchronize with Central process across teams. Sync Traffic Control monitors who is syncing at any given moment, prevents simultaneous sync conflicts, queues users, and sends customizable sync reminders. Administrators can also trigger reminders manually from Project Central, and Guardian can be configured to sync automatically for users who forget.
User Overrides — An administrator tool used to reset a specific user's command frequency settings back to the default. Useful when a user has dismissed or silenced a Command Message they should still be receiving. Overrides can also be preset by the administrator.
View Filter Protections — A Custom Interaction rules-based and Model Settings selection-based protection that protects end-users from modifying, deleting, or overriding Revit View Filters in the project.
View Template Protections — A Custom Interaction rules-based and Model Settings selection-based protection that protects end-users from making changes to Revit View Templates, preserving standardized view settings across the project.
Content Car Wash — A term used by Guardian to describe its end-to-end workflow for cleaning non-standard content — whether a family file, a template, or a project model — by running Mapping Configuration rules to standardize all properties to the firm's defined standards.
Family Mapping — A specific type of mapping rule that redirects one Revit family to another. If the target family already exists in the project, Guardian converts all instances of the source family to the target. If it does not exist, the source family is simply renamed.
Guardian Sync Properties™ — A cloud-based feature that stores a firm's standard Revit properties (Fill Patterns, Line Patterns, Object Styles, etc.) in the cloud and keeps them synchronized across all projects. Properties uploaded to the cloud can be automatically or manually pushed to any project regardless of Revit version. Guardian tracks sync status so administrators can identify when a project property has drifted from the cloud standard.
Incoming Properties — Guardian’s standards engine and dialog for cleaning and aligning Revit's native properties when content is loaded into a project. The Incoming Properties dialog provides the mapping of the incoming properties similar to Model Properties. Administrators can map, rename, or remove these properties; end-users see a simplified version based on their Transaction settings.
Mapping Rules — Individual instructions stored within a Mapping Configuration that tell Guardian to rename a property, convert one property to another, or remove an unused property. When incoming content is loaded into a project, Guardian silently applies all applicable rules in the background.
Model Properties — Guardian’s standards engine and dialog for cleaning and aligning Revit's native properties (Fill Patterns, Line Patterns, Object Styles, etc.) on the model level, presented through a unified interface that also includes history tracking, Guardian Sync Properties status indicators, and mapping capabilities. Administrators use Model Properties to identify non-standard content and apply Mapping Rules.
Out of Sync Property — A property in a project model that was previously synchronized with a cloud standard in Guardian Sync Properties, but has since diverged — either because the project version was modified locally or the cloud standard was updated. The property is flagged visually, and administrators can choose to pull the cloud version down or push the project version up.
Shared Parameter Mapping — A mapping rule type that maps a shared parameter to the equivalent shared parameter, ensuring data fields align correctly across projects.
Transactions — Guardian's mechanism for identifying and controlling how it processes incoming Revit content (families, files pasted from other models, exploded CAD, etc.) at the moment it enters a project. Transactions define the end-user experience: Silent Mode processes mappings automatically in the background; Show Dialogs options present the user with the Incoming Properties dialog to manually review and map properties.
Activity Feed — A section of Project Central that shows a chronological, real-time log of all Guardian-tracked events in the project: Project Commands triggered, Transactions completed, Revit warnings generated, and Sync Traffic Control events. Each entry is color-coded by severity and Protection Mode level.
File Size Indicator — A visual indicator in Registered Projects that shows whether a model's file size is growing, shrinking, or staying stable, based on a rolling six-week history. Hovering over the indicator shows the exact percentage change.
Guardian Backstage™ — Guardian's data analytics platform, accessed via Microsoft Power BI or other compatible data tools. Backstage connects to an Azure-based database that aggregates activity captured from all registered projects, providing dashboards on user sessions, sync habits, command usage, Revit warnings, family loading activity, model file sizes, and mapping automation. Data is refreshed approximately every three hours.
Project Central — A real-time project dashboard built directly into Revit, accessible from the ribbon and Registered Projects. It gives administrators a live view of activity within a registered model, including user sessions, sync timelines, Revit warnings, command activity, Guardian Messages, and a "Project at a Glance" summary of items like unpinned protected elements, in-place families, mirrored elements, and groups without names.
Project Sessions — A timeline view in Project Central that visualizes how long each user has had the project model open during a session. Vertical dotted lines indicate sync events; lines that end without a marker may indicate a crash or closure without syncing.
Time to Open / Time to Sync — Performance metrics tracked by Guardian for every project open and every sync event. Longer-than-expected times for all users suggest model performance issues; outliers for individual users may point to hardware or network problems.
Standard Revit and BIM concepts that frequently appear in Guardian workflows. Included here for clients who may be newer to Revit terminology.
Autodesk Forma — Autodesk's cloud platform for BIM collaboration and data management, formerly known as Autodesk Construction Cloud (ACC). Guardian integrates with Forma by automatically grouping models based on their Forma Project ID and recognizing Forma-hosted files in Registered Projects.
Central File — The master copy of a workshared Revit model, stored on a shared server or cloud platform (such as Forma). All team members' local copies sync their changes back to the Central File.
Family — A Revit component file (.rfa) that defines a category of building element — such as a door, window, structural column, or light fixture. Families contain type parameters that define variations (e.g., different sizes) and instance parameters that can be set individually per placement.
Fill Patterns — Hatch patterns applied to surfaces in Revit to represent materials or element types in plan, section, or 3D views (e.g., concrete crosshatch, insulation batt). Fill patterns are a type of Model Property managed and standardized by Guardian Sync Properties.
In-Place Family — A family created directly within a project model rather than as a standalone .rfa file. In-place families are generally discouraged because each instance is treated as an individual file, significantly increasing the model file size over an equivalent loadable Revit family. Guardian's Project at a Glance flags in-place families for administrator review.
Line Patterns — Repeating dash-and-gap sequences applied to lines, edges, and curves in Revit to represent different element types graphically (e.g., hidden, centerline, dashed). Line patterns are a type of Model Property managed and standardized by Guardian.
Object Styles — Revit's global settings that control the default appearance (line weight, line color, line pattern, and material) for every category of Revit element. Object Styles and subcategories are a key Model Property that Guardian tracks and can standardize across projects.
Revit Warnings — Notifications generated by Revit when model conditions conflict with its internal rules (e.g., overlapping walls, room not enclosed, elements slightly off-axis). Warnings do not prevent work but can accumulate and affect model performance. Guardian's Revit Warning Tracking Protections monitors and categorizes warnings so administrators can identify problem areas early.
Shared Parameters — Custom parameters defined in an external shared parameter file (.txt) that can be used consistently across multiple Revit families and projects. Shared parameters ensure that data fields carry the same definition, enabling reliable scheduling and data export. Guardian's Shared Parameter Mapping ensures incoming families use the firm's standard shared parameter definitions.
Synchronize with Central (SWC) — The Revit command used to save a user's local changes back to the Central File and pull in changes made by other team members. Regular synchronization is critical for team coordination and model stability. Guardian Sync Traffic Control helps manage this process across large teams.
System Family — A Revit family that is built into the software and cannot be loaded as an external .rfa file. Examples include walls, floors, roofs, ceilings, stairs, and railings. Their types are controlled through Type Properties and exist within the project file itself.
View Filters — Revit rules applied to views that configure the appearance of elements based on parameter values (e.g., highlight all walls with a fire rating). Guardian's View Filter Protections prevent end-users from modifying filters that administrators have defined as standards.
View Templates — Saved sets of view properties (scale, detail level, visibility/graphics overrides, filters) that can be applied consistently across multiple views. Guardian's View Template Protections prevent users from overriding or deleting standard view templates.
Worksets — Subdivisions within a workshared Revit model that control which elements different team members own or can edit. Common worksets include categories like Exterior Shell, Interior, Structure, Linked Files, and Shared Levels and Grids.
Worksharing — A Revit collaboration method that enables multiple users to work simultaneously in the same model file by dividing it into worksets. Enabling worksharing creates a Central File and allows team members to check out and work on specific portions of the model.
Contact our support team to receive personalized assistance.
