Guest participants can share content with the collaboration, receive content from the collaboration, or do both, depending on the access mode they are given by the collaboration host. When the host creates the collaboration invitation, they will decide how the guest is allowed to participate in the collaboration.
Set up a collaboration
The following are high-level steps for configuring distributed collaboration as a guest:
Note:To see the workflow steps for a collaboration host, see Create a collaboration as a host.
- Accept an invitation to collaborate.
- Join a group to the collaboration workspace.
Accept an invitation to collaborate
- Sign in to your organization as a member with administrative privileges. Go to Organization > Settings > Collaborations.
- Click Accept Invitation.
- On the Accept Collaboration Invitation dialog box, choose the file containing the invitation from the host. Information about the collaboration, including the description and the contact person, will appear once you've chosen the file. If the host requires web-tier authentication, choose the Yes button, enter the credentials for the host's web authentication, and click Accept Invitation.
The Save Invitation Response dialog box appears.
- Click Save Response to generate a file with information about your acceptance. Share this acceptance file with the administrator of the host.
You must share the file outside of ArcGIS Enterprise; this can be by email or another method you have arranged.
Join a group to the collaboration workspace
As the guest organization's administrator, you will receive a notification that you have joined the collaboration. Once you have received the notification, you may join a group to the collaboration workspace.
- Sign in to the guest organization as a member with administrative privileges. Browse to Organization > Settings > Collaborations.
- On the Collaborations page, find and select the table entry for the collaboration with the workspace to which you'll join a group.
- Click the Action button for the selected workspace and click Join Workspace.
- Choose the group that will be associated with the collaboration workspace. This can be an existing group, or you can create a group for this purpose. A group can only be associated with one collaboration workspace.
- If you create a group for the collaboration workspace, it will be a private group where all group members can contribute content to the group. You can change the status and contribution settings after the group has been created if necessary. See Create groups for more information about these settings. When you a create a group for a workspace, you must specify tags for the group to proceed.
- If you choose to link an existing group, the drop-down menu will show a list of all of the groups in the portal, including private groups.
- Choose how feature layers will be sent to the collaboration workspace:
- As references—Collaboration participants will receive live access to feature layers in the designated workspace. Collaboration participants must have access to view feature layers from the originating portal.
- As copies—Collaboration participants will receive feature layer updates at a scheduled interval.
When choosing to send copies of feature layers, do the following:
- A sync interval must be set within the collaboration workspace
- Sync must be enabled on each participating item in the collaboration before sharing.
A copy of participating feature layers will be initially extracted and published as items to each participating portal with Receive access. Once these items have been created, features are updated based on the established sync interval.
- Allow two-way sharing of feature service edits to eligible participants—Introduced at 10.9, the owner and recipient of a feature layer can make and share edits between them. In previous versions, data edits in feature layers could only be shared from the owner to the recipient. By default, this is not enabled. This option is only available if Copies is selected under Feature layers and views in my portal are sent as when establishing the workspace sync settings. Once enabled on a workspace, this option cannot be disabled. To be eligible for the two-way sharing of edits, all ArcGIS Enterprise collaboration participants must be using a version of Enterprise that is 10.9 or later, with the collaboration workspace also having been created using a version of 10.9 or later, and guests must have Send and Receive access to the collaboration workspace. Eligible feature services must be configured to use ArcGIS Pro service runtime and support replica tracking and bidirectional sync.
- If unable to share as copies, share as reference—Introduced at 10.9 for collaboration guests. This option is available if Copies is selected under Feature layers and views in my portal are sent as when establishing the workspace sync settings. If errors occur while sharing feature layers as copies, affected layers will be shared as references instead. By default, this will be enabled. Your selection can be updated by editing your workspace. For more information, see Manage collaborations as guests.
- Click Join Workspace.
The collaboration host's administrator will receive a notification that the guest organization has an active status in the collaboration workspace.
Once you've completed this workflow, sync settings and other details of the collaboration can be further configured. When content is shared with a participant, a folder is created under the participant administrator's folder. This is used to import the content and store the items, which are then shared to the group associated with the collaboration workspace. The folder is named based on the collaboration name.
Note that the sync settings for the collaboration host's workspace are set to sync immediately and can only be changed in the ArcGIS Portal Directory sharing location.
In collaborations in which ArcGIS Online is the host, sync settings will default to At scheduled intervals. The ArcGIS Enterprise participant controls the schedule at which group item content and feature layer edits are synchronized; the host does not control the sync schedule.