Bridge in Design Collaboration FAQ
- General FAQ
- Configuration
- Do I have to make sure that the location of the shared folder is the same in every bridged project?
- Does renaming or moving the shared folder in the source or bridged project cause issues?
- What happens in the background during the process of setting up Bridge team automations?
- Which folders will be bridged/synchronized in a Bridge for Design Collaboration environment?
- Can I set up Bridge team automations for existing teams in a later phase of a project?
- Can I create more Bridge team automations on teams that already have automations enabled?
- Can I configure a Bridge team automation in any project?
- Is it possible to pause and resume Bridge team automations?
- As a member of a bridged project, can I choose not to receive packages from teams in other projects?
- What happens when a team folder already exists in the shared folder of a project I want to bridge with?
- What happens when a team folder with active team automations is deleted from the shared folder in a bridged project?
- Can I update my team settings (such as name and color) when it has Bridge team automations enabled?
- Package Workflow
- Can I share a package with a single or limited selection of bridged projects, even if my project is bridged with multiple projects?
- Can I consume a package shared from a bridged project?
- When working with Bridge in Design Collaboration, is it possible to use direct linking to contents in the shared folder instead of the package workflow?
- How I can make sure that packages are transferred successfully into the bridged projects?
- Why is there a spinning wheel on the models that have been shared with me in a bridged package?
- Can I use Bridge team automations and the Design Collaboration folder structure to transfer data to Docs?
- Can I forward or share packages that have been shared with me to other bridged projects?
- Which file types can I share in bridged packages?
- Issue Management
- Bridge and Revit Workflows
General FAQ
Is there a limit to the number of projects that I can bridge with?
No.
Is there a limit to the number of Bridge team automations that I can configure?
No.
Configuration
Do I have to make sure that the location of the shared folder is the same in every bridged project?
No. Each project and Design Collaboration configuration can use a different shared folder.
Does renaming or moving the shared folder in the source or bridged project cause issues?
No, but moving the shared folder into a team folder will break Design Collaboration package workflows for all projects.
What happens in the background during the process of setting up Bridge team automations?
Design Collaboration will create an equivalent team folder in the shared folder of the bridged project, establishing a one-way synchronization from your team's shared folder to the newly created folder.
Which folders will be bridged/synchronized in a Bridge for Design Collaboration environment?
The folder synchronization will be established between the equivalent team folders in the shared folder on each project.
Can I set up Bridge team automations for existing teams in a later phase of a project?
Yes, you can enable Bridge team automations at any time in the project lifecycle.
Can I create more Bridge team automations on teams that already have automations enabled?
Yes, you can enable Bridge team automations at any time in the project lifecycle, and there is no limit on the number of automations that can be created per team.
Can I configure a Bridge team automation in any project?
Yes, you can enable Bridge team automations for any project which has Design Collaboration initialized. You don't need to be a member of the project you want to bridge with. Design Collaboration initialization involves the creation of a shared folder, which is required for Bridge workflows. Team folder configuration is not required in the target project.
Is it possible to pause and resume Bridge team automations?
Yes, you can pause Bridge team automations in the Bridge tool. This will temporarily stop the synchronization from the source to the bridged project. Any packages that are shared while team automations are paused are not synchronized to the bridged project. You can resume team automations at any time in the project lifecycle.
As a member of a bridged project, can I choose not to receive packages from teams in other projects?
Yes, you can pause a team automation to stop receiving packages and data. Pausing a team automation is available for both the source and bridged projects through the Bridge tool, and this will stop the synchronization of packages from that project.
What happens when a team folder already exists in the shared folder of a project I want to bridge with?
Design Collaboration will create a folder with the same name and an incremental number in brackets. For example if the team folder is called Arch, subsequent folders would be called Arch(1), Arch(2).
What happens when a team folder with active team automations is deleted from the shared folder in a bridged project?
Deleting a team folder with active team automations will delete those automations and prevent any further synchronization from happening. The team is still visible in the bridged project, but is shown in a ghosted state on the Project timeline.
Can I update my team settings (such as name and color) when it has Bridge team automations enabled?
Yes, updating the name or color of a team will have no impact on team automations, and will not show up in the bridged project.
Package Workflow
Can I share a package with a single or limited selection of bridged projects, even if my project is bridged with multiple projects?
No, packages are shared with all bridged projects, as specified by the Bridge team automations you have set up.
Can I consume a package shared from a bridged project?
Yes, consuming a bridged package will copy its contents into the Consumed folder in your team space (in the Home tool).
When working with Bridge in Design Collaboration, is it possible to use direct linking to contents in the shared folder instead of the package workflow?
As well as consuming packages, it is also possible to link directly to content in the shared folder in the source project. Whenever a new version of the content is shared, this is automatically reflected in your desktop authoring application without the need to consume a package. For more control over model versions, use the regular package workflow to allow review of contents before consuming.
How I can make sure that packages are transferred successfully into the bridged projects?
You will see notifications in Design Collaboration when packages have been shared and received, or if there were any problems sharing the package.
Why is there a spinning wheel on the models that have been shared with me in a bridged package?
Models shared as part of a bridged package are handled as an upload into the project, and so require extraction and translation of the 2D sheets and 3D views. The spinning wheel indicates that this is in progress, and the models will be available shortly.
Can I use Bridge team automations and the Design Collaboration folder structure to transfer data to Docs?
Uploading or copying models into a team folder in the shared folder of a bridged project will cause those models to be automatically synchronized to all bridged projects that team has automations set up for. Models shared in this way won't show up on the Project timeline in Design Collaboration.
Can I forward or share packages that have been shared with me to other bridged projects?
No, only the owner of the original shared package will be able to share it with other projects.
Which file types can I share in bridged packages?
All Design Collaboration supported file formats can be shared between projects. This includes the various types of Revit models (standard Revit models, Cloud models, and Cloud Workshared models).
Issue Management
Can I create issues on models shared with me by a bridged package?
o, Bridge does not currently support this. You can create issues on models from bridged packages, but these issues remain local to the project in which they are created.
Bridge and Revit Workflows
Are Revit Cloud Workshared (RCW) models supported when using Bridge in Design Collaboration?
Yes, in addition to all other types of Revit models.
Which Revit versions support RCW bridged models?
- Share models with Bridge: You can use any version of Revit.
- Receive models with Bridge: You need to use Revit 2023.1.2 or later version.
Can I reference bridged models from an earlier version of Revit?
No, all referenced files need to be created or upgraded to the same version of Revit.
Can I link an RCW model into Revit from another project using Bridge?
No, RCW and Revit do not support live-linking across projects. To copy or synchronize an RCW model between projects, either use direct linking to the shared folder (see question 3 in the Package Workflow section), or use the standard Design Collaboration package workflow.