Latest news
Tips & GuidesRevitAutodesk FormaAutodesk

BIM Sharing Guide with Autodesk Forma Design Collaboration Packages

Autodesk Forma Design Collaboration lets teams share Revit models, views and sheet sets, and supporting documents through packages. This guide explains how to prepare, share, and consume packages.

Studio scene showing teams reviewing a shared architectural project model and drawings togetherAI image
Representative image, generated with AI.Image: 3dsınıfı / FCA AI

In brief

  1. Packages can include models, views or sheet sets, and supporting documents.
  2. You need at least Create permission in the team folder to create a package, and at least Edit permission to share it.
  3. After reviewing packages from other teams, you can bring them into your team space with the Consume step.
  4. The source documents do not specify a particular software version number.

Autodesk Forma Design Collaboration helps different teams organize and share BIM deliverables through packages. The workflow described in Autodesk’s official help documents covers grouping models published from Revit, views and sheet sets, and supporting documents; checking the contents before sharing; and, when appropriate, consuming deliverables from other teams. The steps below follow the Design Collaboration workflow described in those documents. Since the sources do not specify a required software version number, no additional assumptions about version compatibility should be made.

1. Understand what package sharing is for

A package brings together the models, views, sheet sets, and supporting documents selected by a team as a single deliverable. This lets teams decide what to share, rather than having every update automatically flow into other parties’ working environments. The receiving team can review a package first, then decide whether to bring it into its own workspace.

The Design Collaboration timeline visualizes deliverable exchanges between teams and the status of packages. The platform’s features for viewing the current project model and comparing it with previous versions can also help team members who do not work in Revit keep track of changes. This approach makes it easier for different disciplines or firms to track which deliverable is under review and which has been brought into a team space.

2. Create a package and select its contents

  1. Check that Revit content has been published. Autodesk recommends that Revit authors publish their latest models and sets to Design Collaboration before preparing a package. The documents also describe using Publish latest to update content in the team space.

  2. Start creating a package from the timeline. Users with at least Create permission in the team folder can use Create package at the top of the timeline. Alternatively, expand the timeline and click the plus button at the far right of the team’s row.

  3. Select what to share in the Content Browser. The Sets menu contains views or sheet sets created in Revit. You can select an entire set or add specific views and sheets from it to the package. Select RVT models from the Models menu; models in a set may be selected by default when the set is selected.

  4. Add supporting documents. Open the Documents menu and select Add documents to choose relevant files from the team folder. To check which file types are supported, consult Autodesk’s help for supporting documents; the source text here does not list the file types individually.

  5. Save the content and review the draft. Select Add to add your selections, then Save to save the package. The new package remains in draft status and is visible only to your team. Before sharing, verify that the models, sets, and documents represent the intended deliverable.

3. Share, update, or reuse a package

Open the draft package from the timeline node in the team’s row and review its contents again. Sharing a package requires at least Edit permission in the team folder. In the window that opens with Share, you can edit the package name and add a description. When you select Share, the package appears in the shared row of other teams’ timelines.

For a recurring deliverable, you can start a new package with Reuse from a previously shared node. The content selections in the previous package become the starting point for the new one; the latest published content is selected for the relevant models, sets, views, sheets, and supporting documents. Before sharing, review the selections against the scope of the new deliverable and make any necessary changes.

A draft package can be edited later. Open the package, change its name and description, then select Edit to return to the Content Browser, update the content to be shared, and save with Save. If new content is published by the team while you are working on a package, you may see a version-change notification for selected files. The team can then decide whether to keep the previously reviewed file version or switch to the latest published version.

4. Review and consume another team’s package

  1. Find the shared package in the timeline. Packages that have not yet been consumed appear as empty circles in the other team’s row. If a node represents multiple packages, you may need to click it several times to select the right one.

  2. Review the contents before consuming. Autodesk notes that it can be useful to explore a package first and understand how new information might affect ongoing work. Reviewing it lets you assess whether the deliverable is suitable for your team’s work.

  3. If appropriate, bring it into your team space with Consume. The Consume step adds the package contents to the consuming team’s workspace and project view; the source team remains the package owner and is responsible for it. After consumption, the other team’s latest model appears in Project Model. If the other team’s consumed online model is linked in Revit, those links are updated automatically in the authoring environment.

What does this mean for architecture and visualization workflows?

Architecture and interior design teams can use this package-based approach to share project models and sheet deliverables with other disciplines in a more controlled way. For archviz teams, tracking which package contains the current model and when changes are brought into the team space can help manage the data used for visualization. However, the source documents do not describe integration with any particular render software or hardware requirements.

Before getting started, check access permissions in the project account, the publication status of Revit content, and the available subscription. Autodesk’s help document discusses access to Design Collaboration in relation to subscriptions and products on the platform; it does not provide a detailed version or hardware list. Teams should therefore verify their own account and project conditions before making purchasing or technical setup decisions.

Common mistakes

  • Assuming unpublished content is included in the package: If the latest Revit models and sets have not been published to Design Collaboration, the content in the team space may not be current. Check the publication status before creating a package.

  • Confusing a draft with a shared package: A newly saved package is a draft and is visible only to your team. It must also be shared before other teams can access it.

  • Not verifying the contents before sharing: You can edit the package name and description, but the key check is whether the correct models, sets, and documents have been selected.

  • Overlooking a changed file version: A notification may appear if a new version is published while a draft is open. Make a deliberate decision about whether to keep the previously reviewed version or switch to the latest one.

  • Consuming a package without reviewing it: Consume brings the deliverable into the team space. Review the package first and assess whether the changes are suitable for ongoing work.

Sources

2 sources
H
help.autodesk.comhelp.autodesk.com/view/COLLAB/ENG
Summary
H
help.autodesk.comhelp.autodesk.com/view/COLLAB/ENU
Summary

Source texts are not republished; short quotes are marked, everything else is our own summary and commentary.

3dsınıfı’s take
3dEditor’s assessment

For multidisciplinary project teams in Turkey, one of the most practical benefits is being able to control what gets shared and when it is consumed, rather than automatically accepting every update. Handling sets and supporting documents in the same package as Revit models can make deliverable reviews more organized.

It is important for offices to clarify permissions and subscription access before getting started; creating and sharing packages require different permission levels. Since the documents do not specify particular hardware or version requirements, this guide should not be used as the basis for installation or purchasing decisions. One detail that is easy to miss is a change to the selected file version while a draft is waiting to be shared.

Frequently asked questions

What content can be added to a Forma Design Collaboration package?

Packages can include models, views and sheet sets created in Revit or selected items from them, as well as supporting documents.

What permissions are required to create and share a package in Design Collaboration?

You need at least Create permission in the team folder to create and edit a package, and at least Edit permission to share it.

What happens when a Design Collaboration package is consumed?

The package brings another team’s deliverable into the consuming team’s environment, and that team’s latest model appears in Project Model. Revit links to consumed online models are updated automatically.

Comments and the forum are in Turkish.Join the discussion
+

Related news