Location sharing is an organization-wide extension, allowing you to record where users are and where they have been. Enabling location sharing creates a location sharing layer to which licensed users in your organization can upload their locations using the Field Maps, QuickCapture, Survey123, or Indoors mobile app. Users only see their own tracks, and additional permissions are required to view the tracks of others.
Once location sharing is enabled, administrators can use the Track Viewer web app to share last known location and track data with other users in the organization by creating track views. Track views define which users have tracks included in the view and who can view those tracks. The Field Maps, QuickCapture, Survey123, and Indoors mobile apps are optimized for sharing locations in the background, minimizing the impact on device battery. The mobile apps record tracks whether or not there is a data connection and provide mobile users with control of when they are and are not tracked.
Do the following to enable location sharing for organization members:
- Verify that you are signed in to your organization as a default administrator or custom role with the following privileges:
- General privileges
- Create, update, and delete
- Share with organization
- Publish hosted feature layers
- Administrative privileges
- Manage licenses
- Utility services
For information on roles and privileges, see Member roles and Privileges granted to roles.
- General privileges
- At the top of the site, click Organization and click the Settings tab.
- Click Organization extensions on the side of the page.
- Click Enable location sharing.
To enable location sharing, your organization must first purchase ArcGIS Location Sharing licenses. This license is included in the Mobile Worker user type and is available as an add-on for all other user types. See User types for more information.
A location sharing layer is created. As the administrator who enables location sharing, you own the location sharing layer. The Location sharing folder that is created and that stores all items (layers and track views) needed for location sharing is in your content and owned by you. Administrators in your organization can create track views using the Track Viewer web app, allowing others to view location tracks, but all such views are owned by you. You're the only administrator who can disable location sharing, although all administrators can pause it.
Caution:
If the role of the administrator who enabled location sharing changes to a role that does not have the required privileges for enabling location sharing, other administrators cannot create track views.
If this happens, change the ownership of the location sharing layer (and all of its views) to a different administrator. Once an administrator owns the location sharing layer, other administrators can create track views.
Manage location sharing
Once location sharing is enabled, administrators can manage it as follows:
- Pause location sharing.
While location sharing is paused, the location tracks remain but are read-only. No new tracks are collected, and mobile users can't upload tracks to the location sharing layer.
- Disable location sharing.
When location sharing is disabled, all items associated with location sharing (layers, views, groups, and so on) are deleted. The privilege to view location tracks remains associated with any roles to which it was assigned. Only the administrator who enabled location sharing can disable it.
Note:
Location tracks are stored in your organization for 30 days. The storage of tracks does not consume credits.
View location tracks
While mobile users can see only their tracks, other users who are not administrators—such as supervisors and mobile crew managers—may need to view the tracks of others. A track view contains the last known locations and tracks of a set of mobile users. Anyone with the privilege to view location tracks and access to a track view can view the tracks of the specified mobile users.
The privilege to view location tracks is granted to administrators by default and can be added to custom roles. Administrators create track views in the Track Viewer web app, defining the mobile users whose tracks are included in it. The administrator also adds the track viewers who can see the last known locations and tracks of the included mobile users. When a track view is created, an associated group that controls access to the track view is also created. Adding track viewers to the track view adds them to the group.
Once track viewers have access to location tracks, they can view them in the Track Viewer web app or another map or app. Track Viewer provides an overview of the last known locations and the tracks of mobile users and allows the track viewer to do simple filtering and analysis. Add the hosted feature layer view of the tracks to your own map or app for a more complete picture of the locations of your mobile users and where they've been in relation to other assets and information important to you. You can also use the tracks for advanced analysis in ArcGIS. See View tracks and Track layers for details.
Location track security
Location tracks are stored in your organization. With ownership-based access control enabled for the location tracks history, users can only see their own tracks. Users who need to see additional tracks must have the privilege to view location tracks and be assigned to a group that contains the track view they need to access. Administrators (including the one who creates the location sharing layer) can access all tracks in the layer.
While tracks are collected using the Field Maps, QuickCapture, Survey123, or Indoors mobile app, they are stored in an SQLite database on the mobile device. Each shared location is created by the user signed in to the app, and editor tracking stores this information with the shared location. When a user signs out of Field Maps, QuickCapture, Survey123, or Indoors, the tracks are removed from the device. Other users who use the app on the device don't have access to the tracks of previous users.
Note:
To learn more about deploying cloud and enterprise GIS in a manner that helps comply with privacy regulations, such as GDPR, for location sharing services, see ArcGIS Location Sharing Privacy Best Practices.