Configurable app templates

When you share a configurable app template with collaboration participants, a corresponding web app item is created in the collaboration. Your organization's shareable theme properties are also shared with the app. Any related items of the web app to the collaboration group, such as web maps, images, logos, layers, and source data. Doing so ensures that collaboration participants receive a copy of the web app and copies of the items consumed by the app. Feature layers in the web app are shared based on the workspace setting. Any utility resources included in the app—such as geocoding, printing, or geoenrichment services—are updated to use the corresponding utility services on the destination URL.

As of ArcGIS Enterprise 10.8, group-based apps, as well as apps created using the ArcGIS Indoors template, can be shared between ArcGIS Enterprise 10.8 and up participants or from ArcGIS Enterprise 10.8 and up to an ArcGIS Online organization. The recipient of an ArcGIS Indoors application must be configured to use ArcGIS Indoors.

Web AppBuilder apps

When you share Web AppBuilder apps with collaboration participants, a corresponding web app item is created in the collaboration. Your organization's shareable theme properties are also shared with the app. You should share any related items of the web app to the collaboration group, such as web maps, images, logos, layers, and source data. Doing so ensures that collaboration participants receive a copy of the web app and copies of the items consumed by the app. Any utility resources included in the app—such as geocoding, printing, or geoenrichment services—are updated to use the corresponding utility services on the recipient's portal.

Web AppBuilder allows you to build custom 2D or 3D web apps. Recipients of shared Web AppBuilder apps have the option to download the corresponding code or create an app template in their organization.

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.

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.

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 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 ArcGIS Enterprise portal 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 hosted feature layers, hosted feature layer views, and federated feature layers as references

Sharing hosted feature layers, hosted feature layer views, and federated feature layers by reference creates a layer item for collaboration recipients and does not copy the data. The layer item in the recipient's organization references back to the original feature layer or feature layer view. To access the referenced layer, members must have access to the original organization or the layer must be shared with Everyone, or have save credentials. If the layer is secured, members must authenticate in the original organization as a member (at a minimum, a Viewer user type) who has access to the shared layer through the sharing settings.

Share hosted feature layers, hosted feature layer views, and federated feature layers as copies

Hosted feature layers, hosted feature layer views, and federated feature layers can be shared as copies. When layers are shared as copies, the data is copied to the recipient's organization and a new item (a hosted feature layer) is published. The copied item is hosted by the receiving organization, which is indicated by the item's service URL.

When you join a workspace as a guest who can send content, items you add to the workspace's group are sent to organizations that can receive or send and receive content from the workspace by using the Receive or Send and Receive options.

See About sharing feature layer and view data as copies and View synchronization status for more details.

Shared feature layer editing

Shared feature layers can be edited either by the owner of the layer (one-way) or by both the owner and receiver of the layer (two-way).

Edits made by owner and receiver (two-way)

Support for sharing edits two-way was introduced at ArcGIS Enterprise 10.9. When sharing edits two-way, the owner of the feature layer can allow shared feature layers to be edited by both the owner and the receiving collaboration participants. The types of edits supported include adding new features, editing features, or deleting existing features.

Services that support sharing edits two-way include the following:

• Hosted feature services
• Hosted feature service views
• Feature services running on branch versioned data
• Feature services running on nonversioned with archiving data
• Feature services published by reference from a user manager data store

The following are prerequisites for allowing edits to be shared two-way:

• For ArcGIS Enterprise, the collaboration workspace must be created at version 10.9 or later to enable this capability. Workspaces created prior to 10.9 will not support this option.
• To enable the option of two-way sharing of edits to eligible participants, the collaboration workspace must be configured to share feature layers as Copies when setting up the workspace sync settings.
• The participant configuring the collaboration workspace must have Send and Receive access.
• The participant receiving the feature layer must have Send and Receive access to the collaboration workspace.
• Collaboration participants must be using ArcGIS Enterprise 10.9 or later. The shared feature layer must meet the following requirements:
  • Has sync enabled—The feature service property capabilities should appear as follows:
    "capabilities": "Query,Create,Update,Delete,Editing,Sync"

  • Is configured to use the ArcGIS Pro service runtime
  • Supports replica tracking—The feature service layer property isDataReplicaTracked should be true:
    "isDataReplicaTracked": true

  • Supports bidirectional sync—The feature service property syncCapability should have the child property supportsBiDirectionalSyncForServer set as true:
    
    {
      "syncCapabilities": {
        "supportsBiDirectionalSyncForServer": true
      }
    }

If the feature service does not meet all the above requirements, but has sync enabled, the service will be shared as copies supporting one-way editing. Additionally, if the above requirements are not met, and the service does not have sync enabled, the service will be shared as a reference.

A collaboration workspace configuration (introduced at ArcGIS Enterprise 10.8.1 for collaboration hosts, and at 10.9 for collaboration guests) allows the organization to either send feature service items as a reference if they are unable to be sent as copies, or allow for feature service items to not be shared at all if they cannot be sent as copies if the feature isn't enabled. This feature, If unable to share as copies share as reference, is available to both collaboration host and guests when creating or managing the collaboration workspace. To learn more about how to manage a collaboration workspace and how to modify this feature as a collaboration host, see Manage collaborations as host. To learn more about how to manage the collaboration workspace and modify this feature as a collaboration participant, see Manage collaborations as guest.

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.

Prerequisites

The following must all be true before any Insights items can be shared to a collaboration:

• Insights must be properly licensed for ArcGIS Enterprise and ArcGIS Online. For further licensing details, see Configure ArcGIS Enterprise to support Insights.
• ArcGIS Enterprise recipients are required to have Insights installed to open received workbooks, pages, models, and themes.
• Participants must have Insights 3.2.1 or later installed to share and receive Insights content. Items can only be shared with recipients who are using a version of Insights that is the same as or later than the sender's current version.

ArcGIS Insights workbooks and pages

Sharing Insights workbooks and pages with collaboration participants provides them with read-only access to the shared items, allowing recipients to explore your analysis. When you share your workbook in a collaboration, any subsequent edits you make to the original item are available to recipients after the next collaboration synchronization. Pages you share with recipients do not receive any ongoing edits. To provide recipients with your most recent edits, you must reshare the page with the collaboration.

Participants may not require an Insights license to view shared workbooks or pages; however, if your Insights item or its content is secured, collaboration participants must be able to authenticate in the originating ArcGIS Enterprise environment as a member who has had the source workbook or page shared with them.

For more information about the best practices for sharing a workbook or sharing a page, review the ArcGIS Insights documentation.

ArcGIS Insights models

Sharing Insights models allows participants to work within the model to explore and analyze their own data. When a model is shared with collaboration participants, the item is copied and added to each participant's ArcGIS Enterprise or ArcGIS Online organization. These new items act as snapshots of your Insights item, meaning that any subsequent edits made to the workbook or page are not reflected in the recipient's model. Recipients can reconfigure the shared model to run with their own data and parameters.

For more information about the best practices for sharing a model, review the ArcGIS Insights documentation.

Insights themes

Themes can be shared and applied to models to maintain a consistent design standard for collaboration participants.

For more information about the best practices for sharing a theme, review the ArcGIS Insights documentation.