Supported item types can be shared across participants in a collaboration. These item types include:
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.
As of ArcGIS Enterprise 10.6.1, web apps can be shared to collaboration participants using a version of ArcGIS Enterprise that is equal to or greater than the sender. 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.
If you change the way in which an item is shared, ensure you 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, you should change the settings in any operational layers contained in the web map accordingly.
Share web apps
Web apps may be shared with collaboration participants in the following ways:
Configurable application templates
When you share a configurable application template with collaboration participants, a corresponding web app item is created in the collaboration. Your organization's shareable theme properties will also be shared with the application. You should share any related items of the web app to the collaboration group such as: web maps, images such as logos, layers, and source data. Doing so will ensure collaboration participants receive a copy of the web app and also copies of the items consumed by the application. Feature layers in the web app will be shared based on the workspace setting. Any utility resources included in the application such as geocoding, printing, or geoenrichment services will be updated to use the corresponding utility services on the destination URL.
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 will also be shared with the application. You should share any related items of the web app to the collaboration group such as: web maps, images such as logos, layers, and source data. Doing so will ensure collaboration participants receive a copy of the web app and also copies of the items consumed by the application. Any utility resources included in the application such as geocoding, printing, or geoenrichment services will be updated to use the corresponding utility services on the recipient's portal.
Web AppBuilder for ArcGIS allows you to build custom 2D or 3D web applications using ready-to-use or custom widgets. Recipients of shared Web AppBuilder apps will have the option to download the corresponding code or create an application template to their portal.
Custom widgets cannot be shared through collaboration. This includes all registered widget items with the item type AppBuilder Extension.
Other web apps referenced by URL
You can add an existing application as an item to your portal by providing its URL. The portal will reference the application from its existing URL. You must ensure receiving participants are granted permissions to access the application.
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 to 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.
When you share web scenes, feature layers contained in the web scene will be shared as copies as long as the collaboration group is configured to share as copies.
Share layers and views
Hosted feature layers, hosted feature layer views, and federated feature layers can be shared by reference in a collaboration. This creates a new item for recipient portals that references back to the live layer in the origin portal.
Alternatively, hosted feature layers, hosted feature layer views, and federated feature layers can be shared as copies with other collaboration participants. This copies the data and creates a new hosted feature layer in the recipient portal. Edits to the original layer are synced with the copied layer at specified intervals.
Administrators will need to choose whether layers are shared by reference or as copies when setting up or joining a collaboration workspace. When feature layers are shared, either as a reference or a copy, only designated members of the originating portal will be able to edit the feature layer.
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 new layer item for collaboration recipients and does not copy the data. The layer item in the recipient's portal will reference back to the original feature layer or feature layer view. To access the referenced layer, members must have access to the original portal or the layer needs to be shared with Everyone. If the layer is secured, members will need to authenticate in the original portal as a member (at a minimum, a Viewer user type) who has access to the shared layer via 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 portal and a new item (a hosted feature layer) is published. The copied item will be hosted by the receiving portal, which is indicated by the layer's service URL. The owner of the original feature layer can edit the layer and synchronize changes to all participants via sync intervals. Guests will choose the interval at which edits are synchronized in the collaboration workspace. To share layers as copied, ensure you have sync enabled on the hosted layer or view, or that you have configured your federated layer appropriately.
When you join a workspace where access includes Send content, items you add to the workspace's group are sent to organizations to Receive content form the workspace.
Share ArcGIS Server services
If an ArcGIS Server service item is shared to the portal where it originated, as well as to 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 portal with Everyone as well as with the group associated with the collaboration workspace.
ArcGIS Server services that are shared with collaboration participants create items in the participant portals that refer to the original service; the services and corresponding data are not copied to each participating portal. If a participant shares a feature service, only the owner of that service can edit the original feature service.
Once a feature layer has been shared as a data copy, any subsequent schema changes such as enabling attachments will not be synchronized with other participant portals. Ownership-based access control settings on the original hosted feature layer will not be included in the copied data.
Files such as PDFs shared with collaboration participants create corresponding file items in the collaboration participant portals. Any changes you make to those files as a guest participant will be 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 as long as they are not owned by "esri_nav".
Item comments are not synced with collaboration participants.
Share Insights items
Starting at ArcGIS Enterprise 10.7, Insights for ArcGIS workbooks, pages, models and themes can be shared with collaboration participants.
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, please review how to Configure the portal to support Insights.
- ArcGIS Enterprise recipients are required to have Insights installed in order to open received workbooks, pages, models, and themes.
- Participants must have Insights version 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 equal to or greater than the sender's current version.
Note:You will be able to share Insights items from ArcGIS Enterprise to ArcGIS Online; however, Insights items cannot be shared from ArcGIS Online to ArcGIS Enterprise.
Insights workbooks and pages
Sharing Insights workbooks and pages with collaboration participants will provide them with read-only access to the shared items, allowing recipients to explore your analysis. When you share your workbook with a collaboration, any subsequent edits you make to the original item will be available to recipients after the next collaboration synchronization. Pages you share with recipients will not receive any ongoing edits; if you wish to provide recipients with your most recent edits, you will need to re-share 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 portal as a member who has had the source workbook or page shared with them.
If the workbook contains data added directly from a relational database supported by Insights, recipients must be able to authenticate in the originating portal as a member who has access to the relational database connection item.
Shared Insights models allow for 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'sArcGIS 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 will not be reflected in the recipient's model. Recipients can reconfigure the shared model to run with their own data and parameters.
The user in the receiving organization must be licensed for Insights in order to open and edit a received model.
You can find more information on the best practices for sharing a model by reviewing the Insights for ArcGIS documentation.
Themes can be shared and applied to models to maintain a consistent design standard for collaboration participants.
You can find more information on the best practices for sharing a theme by reviewing the Insights for ArcGIS documentation.