In Beta
Guardian Link lets one company keep its Guardian standards and protections in force on a Revit model, even when other companies do much of the work in it and even when that company isn’t actively working in the model.
The company that enables the Link becomes the model’s Primary Project Team, and its standards travel with the model. Every other company working in that model is a Linked Collaborator. Each Collaborator keeps its own Guardian license and its own setup on its other projects, but on the Linked model it works within the Primary’s standards.
Common uses include:
Note: A model can be part of only one active Link at a time. Over its lifetime, it may be part of different Links, but never two at once.
Note: Guardian Link doesn’t add any new role or permission. It changes only where your existing Company Administrator, Project Administrator, and end-user roles can act on a Linked model. See Roles and Permissions.
Clients have told us Guardian protects their own Revit users well, then asked the next question: what about partners from other companies working in the same models?
Over the past four to five years, most companies have adopted Autodesk Forma (formerly Autodesk Construction Cloud) as the common data environment for their projects. That put partner companies directly inside each other’s models. Where companies once worked in separate models, they now share them, and each company’s Guardian applies its own standards to the same file.
Guardian Link gives every project member one set of standards, processes, and best practices to follow, and gives the project team the insight to confirm the project is progressing as planned. Shared models need shared guardrails.
Members aren’t picked from a list. Guardian adds companies to the Link automatically based on how each company registered the model:
Learn more about how models are registered in Model Registration.
While a Link is active, each area of Guardian behaves as follows for a Linked Collaborator:
Pro Tip: Because Collaborator users can add rules to the Primary’s Mapping Configuration under Show Dialogs (full mappings), consider setting Linked models’ Transactions to Silent Mode or Show Dialogs (one time mappings), and checking for Model Overrides on the model, which take precedence, until partners are familiar with your standards. Learn more about Transactions.
A Link moves through four actions: the Primary enables it, Collaborators accept or review it, a Collaborator can leave it, and the Primary can end it.

A Primary Company Administrator, or a Project Administrator assigned to the model, enables the Link from the Link icon in the Project panel of the Guardian ribbon, or from the model’s kebab menu in Registered Projects.

Enabling a Link takes two decisions:
The setting chosen is the starting setting for every Collaborator. The Primary can later change an individual Collaborator’s setting from Link Details, but its own setting can’t be changed after the Link is enabled. If the Link is enabled as Private, the Primary doesn’t receive any other company’s activity, regardless of the setting it gives individual Collaborators.
Last saved by, last saved date, and file size are always shared with every active company in the Link, even when the setting is Private.
Note: Enabling, accepting, leaving, and ending a Link take effect for each user the next time they open the model. Right after a Link is enabled or ended, users who still have the model open may be in a separate Sync Traffic Control queue until they reopen it.
Learn more about Enabling a Guardian Link.
Under Require acceptance, Collaborator users can’t work in the model until one of their administrators accepts the Link. Other users see their company’s administrator contacts instead.
Under No acceptance required, users work right away, and an administrator reviews and acknowledges the Link afterward.
Note: A Link can’t be declined. A Collaborator can accept it and leave it later.
Learn more about Accepting, Reviewing and Leaving a Guardian Link.
A Collaborator’s Company Administrator or Project Administrator can leave a Link from Link Details once their company has accepted or reviewed it. Leaving affects only that company’s membership; the Link continues for everyone else. Leaving resets the company’s membership rather than removing it from the Link.
Under No acceptance required, the company stays active and returns to Review Link: its users keep working, and activity sharing, the shared sync queue, and the Primary’s configurations all continue.
Under Require acceptance, the company’s membership becomes pending, activity sharing stops in both directions, and its users are blocked the next time they open the model until an administrator accepts again.
Only the Primary can end a Link. Ending it applies to every member at once, whatever their acceptance status, and each company’s model goes back to the Project Configuration and Mapping Configuration it had when it joined the Link.
An ended Link can’t be reactivated, but any former member can start a new one. Learn more about Ending a Guardian Link.

Each Linked model shows one of four statuses in Registered Projects, depending on whether you are the Primary or a Collaborator:
Learn more about the Link Actions banner and Link filters in Registered Projects.
In Beta
Guardian Link lets one company keep its Guardian standards and protections in force on a Revit model, even when other companies do much of the work in it and even when that company isn’t actively working in the model.
The company that enables the Link becomes the model’s Primary Project Team, and its standards travel with the model. Every other company working in that model is a Linked Collaborator. Each Collaborator keeps its own Guardian license and its own setup on its other projects, but on the Linked model it works within the Primary’s standards.
Common uses include:
Note: A model can be part of only one active Link at a time. Over its lifetime, it may be part of different Links, but never two at once.
Note: Guardian Link doesn’t add any new role or permission. It changes only where your existing Company Administrator, Project Administrator, and end-user roles can act on a Linked model. See Roles and Permissions.
Clients have told us Guardian protects their own Revit users well, then asked the next question: what about partners from other companies working in the same models?
Over the past four to five years, most companies have adopted Autodesk Forma (formerly Autodesk Construction Cloud) as the common data environment for their projects. That put partner companies directly inside each other’s models. Where companies once worked in separate models, they now share them, and each company’s Guardian applies its own standards to the same file.
Guardian Link gives every project member one set of standards, processes, and best practices to follow, and gives the project team the insight to confirm the project is progressing as planned. Shared models need shared guardrails.
Members aren’t picked from a list. Guardian adds companies to the Link automatically based on how each company registered the model:
Learn more about how models are registered in Model Registration.
While a Link is active, each area of Guardian behaves as follows for a Linked Collaborator:
Pro Tip: Because Collaborator users can add rules to the Primary’s Mapping Configuration under Show Dialogs (full mappings), consider setting Linked models’ Transactions to Silent Mode or Show Dialogs (one time mappings), and checking for Model Overrides on the model, which take precedence, until partners are familiar with your standards. Learn more about Transactions.
A Link moves through four actions: the Primary enables it, Collaborators accept or review it, a Collaborator can leave it, and the Primary can end it.

A Primary Company Administrator, or a Project Administrator assigned to the model, enables the Link from the Link icon in the Project panel of the Guardian ribbon, or from the model’s kebab menu in Registered Projects.

Enabling a Link takes two decisions:
The setting chosen is the starting setting for every Collaborator. The Primary can later change an individual Collaborator’s setting from Link Details, but its own setting can’t be changed after the Link is enabled. If the Link is enabled as Private, the Primary doesn’t receive any other company’s activity, regardless of the setting it gives individual Collaborators.
Last saved by, last saved date, and file size are always shared with every active company in the Link, even when the setting is Private.
Note: Enabling, accepting, leaving, and ending a Link take effect for each user the next time they open the model. Right after a Link is enabled or ended, users who still have the model open may be in a separate Sync Traffic Control queue until they reopen it.
Learn more about Enabling a Guardian Link.
Under Require acceptance, Collaborator users can’t work in the model until one of their administrators accepts the Link. Other users see their company’s administrator contacts instead.
Under No acceptance required, users work right away, and an administrator reviews and acknowledges the Link afterward.
Note: A Link can’t be declined. A Collaborator can accept it and leave it later.
Learn more about Accepting, Reviewing and Leaving a Guardian Link.
A Collaborator’s Company Administrator or Project Administrator can leave a Link from Link Details once their company has accepted or reviewed it. Leaving affects only that company’s membership; the Link continues for everyone else. Leaving resets the company’s membership rather than removing it from the Link.
Under No acceptance required, the company stays active and returns to Review Link: its users keep working, and activity sharing, the shared sync queue, and the Primary’s configurations all continue.
Under Require acceptance, the company’s membership becomes pending, activity sharing stops in both directions, and its users are blocked the next time they open the model until an administrator accepts again.
Only the Primary can end a Link. Ending it applies to every member at once, whatever their acceptance status, and each company’s model goes back to the Project Configuration and Mapping Configuration it had when it joined the Link.
An ended Link can’t be reactivated, but any former member can start a new one. Learn more about Ending a Guardian Link.

Each Linked model shows one of four statuses in Registered Projects, depending on whether you are the Primary or a Collaborator:
Learn more about the Link Actions banner and Link filters in Registered Projects.
Contact our support team to receive personalized assistance.