ArcGIS Mission is a geospatial communications and situational awareness tool. It allows you to create, share, and monitor materials for operational use, and it facilitates peer-to-peer mobile communications in real time.

For more information, see What is ArcGIS Mission.

ArcGIS Mission is composed of a web app, a mobile app, and a server component. ArcGIS Mission Manager is the web app that you use to create and organize the mission. ArcGIS Mission Responder is the mobile app that allows mission members in the field to participate in missions. ArcGIS Mission Server is the server role that allows Manager and Responder to communicate.

No. ArcGIS Mission is not available in ArcGIS Online. It is only available in ArcGIS Enterprise 10.8 and later.

ArcGIS Mission Manager users can be separated into three distinct roles: Editor, Owner, and Administrator, which are defined by their privileges. Users who have one of these three roles can be members of a mission that can view, collaborate, and actively participate in a mission. See ArcGIS Mission Manager roles for more information.

ArcGIS Mission supports Built-in, PKI, IWA, and SAML authentication.

Mission owners and leads have greater privileges, such as adding and removing members from a mission and caching and restoring mission activities.

There is no limit to the number of teams any mission member can be on. The mission owner is automatically on all teams they create in the mission.

No. Changing a map view only affects the user making the change. However, if the mission owner makes changes to mission map, those changes are visible to everyone.

By default, a mission owner is automatically added as a member of the mission. A portal user with the role of an administrator can add themselves to a mission. To accomplish this, browse to the Mission Details page of a mission and click Add Me to add yourself to the mission. Once a member of the mission, the administrator can make edits to various parts of the mission. See Work with the Mission Overview tab for more information.

Yes. The mission map can be edited to include or remove additional reference layers through the Map tab on the Mission Details page of the mission. For more information, see Define a mission map.

You can create mission reports in Mission Details starting at ArcGIS Mission Manager 10.9. For more information, see Create a new report.

Yes. You can view the locations of other Responder users on your mission map by clicking the Last Known Location button. However, if the Responder user you are locked on to changes location, the map will shift back to the locked-on user.

No. You cannot edit a report once it is submitted. For more information, see Submit a report.

No. You are not required to assign a task to create it. Location, Name, and Description are the only fields that are required for task creation. However, you can edit a task as necessary. For more information, see Tasks.

No. You cannot use a mission you created in ArcGIS Mission Manager 10.8.1 in ArcGIS Mission Manager 10.9. The mission will remain in your View Missions list, but you cannot open or interact with this mission. All content and data associated with this mission is available in the mission content folder in Portal for ArcGIS.

No. A mission lead cannot delete a mission. Mission leads can only add and remove members from a mission and can cache and restore an activity in the Messages, Tasks, and Reports feeds. For more information, see Set a mission member as a mission lead.

No. There is no limit to the number of fields you can add to a report. For more information, see Create a report.

Only mission owners and administrators have the ability to create and add reports to a mission. For more information, see Create a new report.

Yes. You can still add the report template to your mission because you need to change the report name before adding it to your mission. For more information, see Create a report from a template.

No. You cannot have multiple measurements appear on your mission map. You can only create one measurement at a time. For more information, see Use the Measure Distance tool.

If you use the Find Nearest tool, and no Responder users are nearby, you will get a message stating so. For more information, see Use the Find Nearest tool.

You can view all eight supported coordinate formats at the same time using the Coordinate Conversion tool. For more information, see Coordinate Conversion tool.

Yes. You can edit the Required Report field once you create your task. For more information, see Create a task.

Yes. You can filter your Reports feed and the mission map to display your desired report type. For more information, see Filter reports.

No, you need to sign in as different users. One user is not supported simultaneously on both devices. Attempting to sign in as the same user can cause issues such as incorrect location data inside the mission.

Yes, tasks remain editable throughout the life of the mission.

This is likely because the events list only displays information in your current mission session. When on another mission screen, such as Mission Details, changes are not tracked.

While you can find the latest version of ArcGIS Mission Responder on the app stores, your versions of Responder, ArcGIS Mission, and ArcGIS Enterprise must match. There is no support for backward compatibility. It is recommended that you download older versions of the app from Esri to a workstation that matches your version of ArcGIS Enterprise and copy it onto your device.

The mission status must be set to Active. If the mission status is set to Draft or Complete, it is not visible in the mission list. See Mission status for more information.

Ensure that you are connected within the mission. You can have Responder open and be participating in the mission, even if you are not currently transmitting your location or receiving location data from other Responder users.

Once you have downloaded the app, you must enter your organization’s mission portal URL and sign in with your account information. For more information, see Access ArcGIS Mission Responder.

No. You cannot edit mission configurations or details in Responder. Any changes to this information must be made through the Manager application by the mission owner or an administrator who is a member of the mission.

The Android and iOS mobile platforms have some general differences regarding design and functionality. The two versions of the Responder app include the same functions and are as similar in appearance as possible, while also following the general style of the individual platform.

Once a report has been submitted by anyone, it enters into the mission as a complete item and cannot be edited. Reports are visible on the mission map as a way to provide relevant information to Responder users in the area. For more information, see Reports.

No. A Responder user cannot edit a task as it has been configured by mission analysts. However, if you cannot perform the task or feel it would be better suited to another mission member, you can contact the mission analyst who assigned it to you, and they can edit the task.

Yes, as of the 10.9 release, Responder can be used in secure environments that have been configured to allow it.

No. Responder can access custom report forms created in ArcGIS Mission Manager but cannot create its own.

While working disconnected, any actions that would normally be sent to the mission server are instead saved locally to your device. Once your device reconnects to the mission server, everything that was stored on your device is sent to the mission server and synced.

You can download the latest version of the app on both the iOS and Android app stores.

No. At the 10.9.1 release, the QR code only takes you to the portal login, not inside the portal itself.

This can be achieved via the admin API. Refer to ArcGIS Mission Server administrative operations.

Yes. ArcGIS Mission Server supports this deployment scenario, and it is recommended. Using a reverse proxy with ArcGIS Mission Server gives you more control over the performance of your ArcGIS Mission Server site. The ability to configure an Apache HTTPD reverse proxy through a new endpoint is provided in the Admin API; refer to Configure a reverse proxy for more details.

Context URLs are essential when your ArcGIS Mission Server site is configured with a reverse proxy, or in the cloud. Setting the WebContextURL in the system properties (for example, "WebContextURL": "https://my.reverse.proxy.com/context") allows HTTP requests to be properly routed to your ArcGIS Mission Server site. Setting the WebSocketContextURL in the system properties (for example, "WebSocketContextURL": "wss://my.reverse.proxy.com/context") allows WebSocket requests (your real-time data) to be properly routed to your ArcGIS Mission Server site.

Yes. ArcGIS Mission Server is a separate installation that requires a separate license to use.

Ensure that you entered the command line parameters properly. Parameters are case sensitive and must be entered exactly; otherwise, an error is returned.

The short answer is that if you have a base installation of ArcGIS Enterprise, it is likely that you already meet the hardware and software requirements for Mission. For details, see ArcGIS Mission Server system requirements.

Yes. ArcGIS Mission Server has an emerging developer story. You can generate missions and perform operations on missions in the portal through ArcGIS Mission Server. For more information, visit the REST API site for ArcGIS Mission Server.

Highly available deployments of ArcGIS Mission Server require joining an existing site via the Join Site command line utility or the Admin API. When creating a shared directory and configuration store between all ArcGIS Mission Server machines, it is recommended that you use a network share for the shared directories and configuration store.

To upgrade a highly available deployment of ArcGIS Mission Server, you must upgrade each machine that is joined to the site. It is recommended that you do this procedurally rather than upgrading every machine simultaneously. For more information, see Upgrade ArcGIS Mission Server.

This is on the roadmap. The team recognizes that real-time video is critical to situational awareness and will be working toward bringing it into Mission.

The minimum is 8 GB of RAM. The minimum architecture scales similarly to that of ArcGIS Server. If your ArcGIS Server deployment is scaled to handle a specific number of people with specified hardware, you can expect ArcGIS Mission to be similar.

ArcGIS Mission Server offers high-availability deployment options, including multimachine, AWS, and Azure deployments. Note that ArcGIS Enterprise must scale in parallel with ArcGIS Mission Server for successful deployment. Therefore, for Mission to support 10,000 users, ArcGIS Enterprise must be configured to scale and support this threshold.

This is on the roadmap. The team is working toward enhancing the ArcGIS Mission Server APIs and programmatic access so that you can create your own solutions.

No, ArcGIS Mission Server is not a system of record as of the 10.9.1 release. ArcGIS Mission Server writes data to feature layers and tables inside of the system of record, which is either the relational or spatiotemporal big data store.

No. Although these three features have different functionality and purpose within a mission, they are all stored in hosted feature layers.