Skip to main content

Using the CoLab integration for Teamcenter Active Workspace

This article is a walk through to the CoLab integration for Teamcenter Active Workspace.

Updated over 2 weeks ago

The CoLab Integration for Teamcenter Active Workspace lets you securely send design files and assemblies from Teamcenter Active Workspace (AWC) directly into a CoLab Workspace for collaborative design reviews, feedback capture, and supplier collaboration — without requiring reviewers to have Teamcenter licenses.


Before You Begin

You must have:

  • A Teamcenter Active Workspace account with permissions to access the files you intend to share.

  • A CoLab user account and access to the destination CoLab Workspace.

  • The CoLab Integration installed and configured by your Teamcenter Administrator.

Note: Installation is typically a one-time activity carried out by your IT or System Admin team. Your CoLab Success Manager can assist with setup.


Signing in to CoLab

The CoLab integration is accessed from a dockable CoLab panel within Teamcenter Active Workspace.

  1. Open Teamcenter Active Workspace.

  2. Open the CoLab panel from the Active Workspace command bar (top or side bar depending on the Teamcenter version).

  3. The CoLab panel opens on the right side of the screen.

  4. Click Sign In.

  5. Complete authentication using your organization’s configured method (for example, SSO).

  6. After signing in, the CoLab panel updates to show sharing options.

You only need to sign in once per browser session. If your session expires, the Sign In button will appear again in the CoLab panel.

Once authenticated, the CoLab panel allows you to:

  • View the currently selected Teamcenter object

  • See whether the file has already been shared to CoLab

  • Select one or more CoLab workspaces

  • Click Share to CoLab to upload the file

A Log Out option is available at the bottom of the panel.


Share an object to CoLab

Within Teamcenter Active Workspace:

  1. Open an object you want to share file(s) from to CoLab.
    You can select either an Item/Item Revision or a specific dataset named reference from the Attachments tab.

  2. Enable the CoLab panel.

  3. Choose the CoLab Workspace where the file(s) should be uploaded.

  4. Confirm and upload.

Once uploaded:

  • Open the CoLab Workspace to view and interact with the files.

  • Invite participants, add comments, pins, markups, and begin your collaborative design review.

Uploading New Revisions

To update an existing file in CoLab with a new version:

  1. Modify or revise the file within Teamcenter Active Workspace.

  2. Re-invoke “Share for Review in CoLab” on the updated file.

  3. CoLab will recognize the file’s identity and create a new revision instead of duplicating it.

This ensures teams review the latest design data and preserves revision history in CoLab


Supported File Types and Structures

The Teamcenter Active Workspace integration supports sharing specific CAD assemblies, parts, and attachments into CoLab.

Supported Assemblies

Assemblies are supported when the top-level file is:

  • CATIA (*.CATProduct)

  • Creo (*.asm)

  • SolidWorks Assembly

Child components must be native part files (*.CATPart / *.prt (Creo) / *.sldprt).

JT and PDF attachments may also be included and will upload as separate files.

Supported Individual Files

The following individual file types can be shared directly:

  • CATIA Part

  • Creo Part

  • SolidWorks Part

  • NX parts (UGMASTER / UGPART)

  • JT

  • PDF

Summary Table

Scenario

Supported

Notes

CATIA / Creo / SolidWorks native assembly

✅ Yes

Full structure uploaded

Native CAD part (*.CATPart, *.prt (Creo), *.sldprt)

✅ Yes

Uploaded as individual part

NX part (UGMASTER / UGPART)

✅ Yes

Parts only (not assemblies)

JT (single file)

✅ Yes

Uploaded as individual file

PDF

✅ Yes

Uploaded as attachment

JT Assembly (non-monolithic)

❌ No

JT structures not supported

NX UGMASTER Assembly

❌ No

Assembly traversal not supported

Drawings (SW, Creo, NX)

❌ No

Not currently supported

DXF / XLSX

❌ No

Not supported

Did this answer your question?