Cross-workspace record type overview

The highlighted information on this page refers to functionality not yet generally available. It is available only in the Preview environment for all customers. After the monthly releases to Production, the same features are also available in the Production environment for customers who enabled fast releases.

For information about fast releases, see Enable or disable fast releases for your organization.

IMPORTANT
The information in this article refers to Adobe Workfront Planning, an additional capability from Adobe Workfront.
For a list of requirements to access Workfront Planning, see Adobe Workfront Planning access overview.
For general information about Workfront Planning, see Get started with Adobe Workfront Planning.

You can enable cross-workspace capabilities for a record type in Adobe Workfront Planning. A cross-workspace record type can be referenced or accessible from more than one workspace.

IMPORTANT
Your organization must purchase the following packages to be able to enable cross-workspace capabilities for record types:
To configure connectable record types:
  • Any Workfront package and any Planning package
Or
  • Any Workflow and a Planning Prime or Ultimate package
To configure global record types:
  • Any Workfront package and a Planning Plus package
Or
  • Any Workflow and a Planning Prime or Ultimate package
For more information about what is included in each Workfront Planning package, contact your Workfront account representative.
For information, see Adobe Workfront Planning access overview.

The following are cross-workspace capabilities of record types:

  • Global record types: Users can add global record types to other workspaces they manage.

  • Connectable record types: Users can connect to this record type from other workspaces.

This article gives you an overview of cross-workspace record types. For information about defining a record type’s cross-workspace capabilities, see Configure cross-workspace capabilities for record types.

Overview of global record types

Global record types can be added to multiple workspaces from a central or primary workspace in Workfront Planning.

When implementing Workfront Planning for a multi-team organization with common workflows, you might need to define a cohesive structure and metadata for key record types (like Campaigns or Deliverables) that can be added to each team’s workspaces to capture and manage their work.

You might also need each team’s work to roll up to a central level.

In such a workflow, you can ensure that teams capture their work consistently while unlocking cross-team visibility, without the need to add everything to one workspace, or everyone in the organization to every workspace. You can use global record types to achieve this.

To use global record types, do the following:

  1. From a workspace you manage, configure a record type to be global.

    A workspace manager can give permissions to users with a Standard license, or teams, groups, roles, and companies to add a chosen record type to a workspaces they manage.

    The original record type will exist in its original workspace but will be made visible in other workspaces.

    For information, see Configure cross-workspace capabilities for record types.

  2. Add a record type to a secondary workspace from an existing one that has been configured as a global record type.

    The record type will exist in the following workspaces:

    • Its original workspace where it was designated as a global record type.
    • A secondary workspace.

    For information, see Add existing record types from another workspace.

    The following sections describe considerations about global record types and how they function in either their original or secondary workspaces.

Considerations about the global record types in their original Primary workspace

The record type configured to be global has the following properties:

  • All its information (appearance, original fields) can only be edited in the original workspace.

  • You can perform the following actions on the global record type from its original workspace:

    • Edit it

      Editing a global record type includes editing its appearance, cross-workspace capabilities, and all the fields created in the original workspace.

    • Share it

      Sharing a record type adds users to the workspace and also shares the records with those users.

    • Delete it

      You can delete a global record type from its original workspace only after you delete all the instances of if from all the secondary workspaces where it was added.

      For more information, see Delete record types.

    • Make it connectable from other workspaces

    • Create and manage request forms

    • Create and manage automations

  • The following records display in the Primary workspace of a global record type:

    • Records added from the global record type in the Primary workspace

    • Records added from global record types in the secondary workspaces where they were added

      The records that you add from a secondary workspace roll up and display in the primary workspace. All members of the original primary workspace gain View permissions to them and the records are visible to them only from the Primary workspace, even when they do not have permissions to the secondary workspace.

  • The following scenarios exist for what kind of permissions you have to the records displayed in the primary workspace, depending on where they were added from:

    • You have the same permissions to the records created in the Primary workspace as you have to the workspace and to the original global record type.
    • You have the same permissions to the records created in a secondary workspace as you have to the secondary workspace and to the global record type in that space.
  • The record types connected to a global record type will become available for connection from the workspaces where this record type is added.

    For example, if you have a Campaign global record type that has a connection with a Regions record type, and you add the Campaign record type to a secondary workspace, Regions will become cross-workspace connectable from the secondary workspace. The secondary workspace members can now create campaigns and link them to regions.

  • Fields created for a global record type from the original workspace are visible from all workspaces where the record type is added.

    You can edit field settings only from the original workspace.

    The settings of the fields created in the original workspace are read-only in the secondary workspaces for all members, regardless of their permissions on the secondary workspace.

    Secondary workspace managers cannot modify the field settings for fields configured in the original workspace. Only yhe workspace managers of the original workspace can modify field settings in the original workspace.

Considerations about global record types in a secondary workspace

  • Secondary workspace contributors gain Contribute permission to the global record type in their team’s workspace. They can add and manage records in it from the secondary workspace.

  • Secondary workspace viewers gain View permission to the global record type in their team’s workspace. They cannot add and manage records in it.

  • Secondary workspace managers can perform the following additional actions on the record type added from a global record type in a secondary workspace:

    • Delete it.

      Deleting the record type from a secondary workspace only removes it from the secondary workspace. The records and fields added to it from the secondary workspace are also deleted from the secondary space. The records added in the secondary space remain in the primary workspace. This does not delete the record type from its original workspace or from any other secondary workspaces where it has been added.

      For more information, see Delete record types.

    • Share it

      By sharing a global record type in a secondary workspace, the following also occur:

      • Users are added to the workspace with View permissions.
      • Users receive the same permissions to all the records of the global record type in the secondary workspace.
    • Share the record types’s views.

      You cannot share a view publicly from a global record type in a secondary workspace. You can only share views internally from a secondary workspace. You can share a view internally and publicly for a global record type in its original workspace.

      For information, see Share views.

  • No user can perform the following actions on a global record type in a secondary workspace:

    • Edit it

      You cannot edit its appearance, cross-workspace capabilities, or the fields added from the original workspace.

    • Create and manage request forms

    • Create and manage automations

  • Records added in a secondary workspace are visible from the following workspaces, when you have View or higher permissions to these workspaces:

    • The secondary place where they were added
    • The global record type’s original primary workspace
  • The following scenarios exist for accessing records that were created in secondary workspaces:

    • If you have Manage permissions on the original workspace, and no permissions on a secondary workspaces, you can view records added from the secondary workspaces in the original workspace, but you cannot manage them from the original workspace.
    • If you have Manage permissions on the original and the secondary workspaces, you can manage the records from both the global record type’s original workspace and from the secondary workspace where they were added.
  • You cannot publicly share views from a global record type in a secondary workspace.

Access to the connections of a global record type

Record types connected to the global record type in the original workspace become visible from other workspaces where the global record type is added and they are available for connections from the secondary workspaces where the global record type is added.

API access of a global record type

When adding records to a global record type from a secondary workspace using the Workfront Planning API, the system checks if the user has access to create records in the original workspace of the global record type.

The following cases exist:

  • If the user has access, the record is created in the global record types’s original workspace.

  • If the user doesn’t have access, the user gets an error that they don’t have access to the global record type’s original workspace and they need to provide the workspace ID where they have access to create records.

Overview of connectable record types

You can connect to a record type that has been defined as connectable from any workspace that you manage.

Your teams might need their records linked to record types from other workspaces or view information captured on records that belong to records in other workspaces. You can achieve this configuration by designating a record type as connectable.

To use connectable record types, do the following:

  1. Configure a record type to be connectable in a specific workspace.

    A workspace manager can select what workspaces a designated record type is available to connect to.

    The original record type will exist in its original workspace and it can be accessible to connect to from another workspace.

    note tip
    TIP
    Only System Administrators can designate a record type to be connectable from all workspaces in the system. All other workspace managers can designate specific workspaces from which to connect to the record type.
    For information, see Configure cross-workspace capabilities for record types.

    1. Connect to a record type designated as connectable from another workspace you manage.

    For information, see Connect record types.

recommendation-more-help
5f00cc6b-2202-40d6-bcd0-3ee0c2316b43