Setup Order of Operations
The right setup order depends on two things: whether your organization uses single sign-on (SSO/SAML), and whether your Custom Web Maps are public or permissioned (secured). Find your scenario below and follow the steps in order - each step depends on the ones before it.
SSO, Esri, and Sensor integrations require an Advanced license.
Choose Your Scenario
Pick the combination that matches your organization, then work top to bottom.
Create the organization account. Do not assign the Observer user type to owners or administrators.
Configure and validate SSO in a test environment (do not enforce yet).
Add all users and operators.
Add the secured Custom Web Maps and share them with the ArcGIS group(s) your federated users belong to, so the maps load for them in AirHub Portal.
Connect Skydio Cloud (operators now exist).
Connect your work order integration and Drone Detection Sensors. For work orders, choose ServiceNow Work Order (FSM), ServiceNow Catalog, or Survey123 Work Requests.
Enforce SSO by disabling native sign-in.
Validate SSO identity matching before binding secured web maps, so a re-mapped identity does not break the service permissions.
Create the organization account. Do not assign the Observer user type to owners or administrators.
Configure and validate SSO in a test environment (do not enforce yet).
Add all users and operators.
Add public Custom Web Maps (these can go in anytime).
Connect Skydio Cloud (after operators).
Connect your work order integration and Drone Detection Sensors. For work orders, choose ServiceNow Work Order (FSM), ServiceNow Catalog, or Survey123 Work Requests.
Enforce SSO by disabling native sign-in.
Create the organization account. Do not assign the Observer user type to owners or administrators.
Add all users and operators to AirHub Portal.
Provision each user's Esri login. Without SSO, users have a dual login- their AirHub Portal sign-in plus a separate ArcGIS Online or Enterprise account used to load secured maps. Create those Esri accounts and use ArcGIS New Member Defaults to auto-add them to the right group.
Add the secured Custom Web Maps and share them with that group, so users can open the maps once signed in to Esri.
Connect Skydio Cloud (after operators).
Connect your work order integration and Drone Detection Sensors. For work orders, choose ServiceNow Work Order (FSM), ServiceNow Catalog, or Survey123 Work Requests.
Without SSO, the AirHub Portal account and the ArcGIS (Esri) account are separate, so users sign in twice — a "dual login" — to reach secured map content.
The fastest path — the only ordering that matters is operators before Skydio.
Create the organization account. Do not assign the Observer user type to owners or administrators.
Add all users and operators. Use New Member Defaults to auto-assign baseline groups.
Add public Custom Web Maps (anytime).
Connect Skydio Cloud (after operators).
Connect your work order integration and Drone Detection Sensors. For work orders, choose ServiceNow Work Order (FSM), ServiceNow Catalog, or Survey123 Work Requests.
Why the Order Matters
A few dependencies drive every scenario above:
Users first. Most integrations assume users already exist in AirHub Portal, so users and operators are added early.
SSO is configured early, enforced last. Configuring before you add users lets them be provisioned once under their SSO identity, avoiding duplicate accounts you'd have to reconcile later. Enforcing (disabling native sign-in) comes last, after validation.
Secured web maps are gated by group membership. A permissioned Custom Web Map is shared with one or more ArcGIS groups, and only users in those groups can load it. Two things have to line up: your users must be in the group, and the web map must be shared with that same group. With SSO, users land in the group automatically through your identity provider's group membership; without SSO, use New Member Defaults to keep them in it. This is why secured maps come after users, add them before users are provisioned and there's no one in the group yet, which creates a poor sign-in experience. Public web maps have no group dependency and can be added anytime.
Skydio needs operators. Skydio Cloud only syncs post-flight logs and telemetry for operators that already exist in AirHub Portal.
Work orders and sensors are independent. Neither depends on users, so they can be set up whenever convenient.
ArcGIS Group Assignments
With SSO, drive AirHub Portal group membership from your identity provider's groups, so users land in the correct groups automatically at sign-in.
Without SSO, use New Member Defaults to automatically add every new member to a baseline set of groups.
Last updated