Skip to main content

Share content with collaboration groups

In a distributed collaboration, the collaboration group you belong to is configured by the host administrator to send, receive, or send and receive content. If you have permission to send content, you can send your content as either a reference or a copy, depending on the content type and how your administrator has set up the collaboration.

The following table lists the supported item types that can be shared in a distributed collaboration and the ways in which they can be shared:

Web apps

Maps

Scenes

Feature layers

Other layers

Files

ArcGIS Enterprise sharing direction

Send

Supported

Supported

Supported

Supported

Supported

Supported

Receive

Supported

Supported

Supported

Supported

Supported

Supported

ArcGIS Online sharing direction

Send

Not supported

Supported

Supported

Supported

Supported

Supported

Receive

Supported

Supported

Supported

Supported

Supported

Supported

Sharing type

References

Not supported

Not supported

Not supported

Supported

Supported

Not supported

One-way copies

Supported

Supported

Supported

Supported

Not supported

Supported

Two-way copies

Not supported

Not supported

Not supported

Supported

Not supported

Not supported

Share web apps

Web apps can be shared with collaboration participants in the following ways:

ArcGIS Experience Builder

Experience Builder apps and templates can be shared with collaboration participants, creating a corresponding app or template item in the collaboration. Application theme items, as well as any related items, are shared with participants. Organization utility resources included with an app, such as printing, are updated to use the corresponding utility services on the recipient's portal. Only the sending organization can make edits to the app or template, which are then shared with collaboration participants. URLs that are added directly to the app will reference the source item. Only published content can be shared with collaboration participants.

Note:

The following widgets are not supported in Experience Builder apps shared through distributed collaboration:

  • Branch Version Management widget

  • Oriented Imagery Catalog widget

  • Survey widget

  • Utility Network Trace widget

ArcGIS Instant Apps

When an instant app is shared with collaboration participants, a corresponding web app item is created in the collaboration. The web app's related items (such as web maps, images, logos, layers, and source data) are shared to the collaboration group, which ensures that collaboration participants receive a copy of the web app and copies of the items consumed by the app. If the web app includes any feature layers, the layers are shared based on the collaboration's workspace setting. Any of the app's included utility resources—such as geocoding, printing, or geoenrichment services—are updated to use the corresponding utility services on the destination URL. The organization's shareable theme properties are also shared with the app.

ArcGIS StoryMaps

When a story is shared with collaboration participants, the Story Maps theme items and related items are also shared. Only the sending organization can make edits to the story. Edits made to the story are shared with collaboration participants. Only published stories can be shared in collaborations.

Other web apps referenced by URL

You can provide the URL of an existing app to add it as an item to your portal. The portal references the app from its existing URL. You must ensure that receiving participants are granted permissions to access the application.

Share maps and scenes

You can send and receive maps and scenes that contain layers in a distributed collaboration. Maps and scenes are always shared as one-way copies; therefore, editing is limited to the sending organization. Item and metadata edits are synchronized from the sending organization to the receiving organization. When you share a map or scene, layers contained in the map or scene are also shared. Feature layers are either shared as references or copies depending on the layer properties and how your administrator has configured the distributed collaboration group. All other layers are shared as references. It is recommended that you share any related items for the layers, such as the source data that created the layers. For example, if you share a map that contains a hosted feature layer published from a shapefile, share the shapefile with the distributed collaboration group. That way, collaboration participants receive a copy of the map, hosted feature layer, and the original shapefile.

Share feature layers

In a distributed collaboration, you can send and receive hosted feature layers, hosted feature layer views, and federated feature layers as references, one-way copies, or two-way copies depending on how your administrator has set up the collaboration. To view the collaboration details of a group you belong to, visit the group page.

Share other layers and services

You can send and receive the following layers in a distributed collaboration; however, these layers and services can only be shared by reference, unlike feature layers:

  • Elevation layers

  • Geodata Services

  • GeoEnrichment Service

  • Geometry Services

  • Geoprocessing Service layers

  • Globe Services

  • Imagery layers

  • Locators

  • Map image layers

  • Network Analysis Services

  • Scene layers

  • Stream layers

  • Tiled imagery layers

  • Tile layers

Sharing by reference creates an item in the recipient organization that references the live layer in your organization. The receiving organization members are prompted for credentials when they add your layer to a map. To avoid a prompt for credentials, you must share your layer with Everyone or save credentials.

Note:

If you share a map or scene containing a layer with stored credentials, the layer will be referenced directly from the source.

Share files

You can send and receive files, such as PDFs, shared with distributed collaboration participants as one-way copies. When you share a file, a corresponding file item is created in the receiving organization. Members of the receiving organization can't make changes to the file or the metadata associated with the item. Item and metadata updates are synchronized from the sending to the receiving organization.

Mobile map packages (.mmpk) can be shared with collaboration participants if they are not owned by esri_nav.

Note:

Item comments are not synced with collaboration participants.