Share content with collaboration groups
Supported item types can be shared across participants in a collaboration. These item types include the following:
When content is shared with a participant, a new folder is created under the participating administrator's folder. This folder is used to import the content and store the items, which are then shared with the group associated with the collaboration workspace. The folder is named based on the collaboration name.
Members of groups linked to a collaboration workspace can view collaboration details on the Overview tab of the group page, which helps them understand how their group content is shared with other collaboration participants.
Note:
As of ArcGIS Enterprise 10.6.1, web apps can be shared to collaboration participants using a version of ArcGIS Enterprise that is the same as or later than the sender's version. Web apps can be shared from ArcGIS Enterprise to ArcGIS Online; however, it is not possible to share web apps from ArcGIS Online to ArcGIS Enterprise.
When you share content with collaboration participants, the item and sublayer metadata are also shared. Only the sending organization can make edits to the metadata. Edits made to the metadata are shared with collaboration participants.
If you change the way an item is shared, you must modify the sharing settings for related items as well. For example, if a web map was previously shared with Everyone but you altered it to be shared with your organization, change the settings in any operational layers contained in the web map accordingly.
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
When you share web maps that contain hosted layers with collaboration participants, corresponding web map items are created in the collaboration. You should also share any related items for the hosted layers in the web map and source data that created those layers with the collaboration group. For example, if you share a web map with a hosted feature layer published from a shapefile, share the hosted feature layer and shapefile with the group associated with the collaboration workspace. That way, collaboration participants receive a copy of the web map, a copy of the hosted feature layer, and a copy of the original shapefile.
Share scenes
When you share web scenes, feature layers contained in the web scene are shared as copies if the collaboration group is configured to share as copies.
Share layers and views
Hosted and referenced services, such as tile, map, and imagery layers, can only be shared by reference in a collaboration. This creates an item for recipient portals that references the live layer in the origin portal.
Alternately, hosted feature layers, hosted feature layer views, and referenced feature layers with sync enabled can be shared as copies with other distributed collaboration participants. Starting at 10.9, you can allow two-way edits of copied layers, meaning both the sending and receiving organizations can edit the layer and synchronize updates back and forth. Types of edits supported include adding new features, editing features, or deleting existing features. Schema updates are not synchronized.
Caution:
When editing feature layers that support two-way sharing of edits, it's important to note that no checks occur to detect and prevent concurrent edits. When edits are submitted, the last change submitted takes precedent, overwriting preexisting edits to the feature layer. To avoid data conflicts, the archived version of the feature service should be consulted before making additional edits.
Note:
An ArcGIS Server service added as an item with stored credentials will not be copied to the destination organization when shared in a distributed collaboration. When web maps or apps containing such an item are shared in a distributed collaboration, they will reference it directly from the source organization.
For more information, see Share feature layers with collaboration groups.
Share imagery layers
You can share imagery layers from ArcGIS Image Server as reference in a collaboration. Imagery layers that are shared as reference cannot be edited or copied to another organization. If groups are used in the sharing workflow, the group gains access to imagery without it being shared to the rest of the organization. When sharing the image layer with a group, the imagery layer can be used in web maps and in ArcGIS Pro. For raster analysis, the member must part of an organization that has the ArcGIS Image Server license. For image services from ArcGIS Enterprise, the creator of the image service defines the capabilities of the recipient with the shared image service.
Share ArcGIS Server services
If an ArcGIS Server service (for example, a map service or image service) is shared to the organization where it originated, as well as with a group associated with a collaboration workspace, members of other participants are still prompted for credentials when adding the service to a map. To avoid a prompt for credentials, you must share the service in the originating organization with Everyone as well as with the group associated with the collaboration workspace, or save credentials.
ArcGIS Server services that are shared with collaboration participants create items in the participant organizations that refer to the original service; the services and corresponding data are not copied to each participating organization. If a participant shares a feature service by reference, only the designated members in the originating environment can edit the original feature service.
Share files
Files, such as PDFs, shared with collaboration participants create corresponding file items in the participating organizations. Any changes you make to these files as a guest participant are overwritten when the content is synced from the item's source. The same is true of metadata associated with an item.
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.