Integration marketplace and connection reference

What this does

Browse provider capabilities at any permitted scope; connect, select assets, reconnect, or disconnect only with Integrations Editor access.

Steps

1. Open Integrations and select a provider.
2. Review requirements, availability, and current/inherited status.
3. Choose Manage when enabled.
4. Complete provider authorization and select only authorized assets.
5. Save and verify synchronization at each affected location.

Browse and requirements

The marketplace describes released capabilities and whether the selected scope is eligible.

Connect, assets, and disconnect

Manage starts provider authorization, asset selection, save, reconnect, and disconnect workflows. Canceling before Save preserves the prior state.

Parent and location behavior

Parent connections can expose eligible assets to child locations. Effective status and mapping remain location-specific.

Permissions and scope

• No Access hides or blocks the module. Read Only permits viewing but disables changes. Editor permits the documented create, edit, publish, or administrative actions within the user's assigned scope.

Mobile

• On narrow screens, open the sidebar or overflow menu to reach the same actions; labels and save behavior are unchanged unless this article says otherwise.

Customer-visible states

• connected
• disconnected
• inherited
• needs attention
• provider error
• syncing

Browse and search integrations

This control is covered by the Integration marketplace and connection reference workflow.

Applies to /admin/integrations

Availability and connection status

This control is covered by the Integration marketplace and connection reference workflow.

Applies to /admin/integrations

Parent versus location scope

This control is covered by the Integration marketplace and connection reference workflow.

Applies to /admin/integrations

Needs-attention and disconnected states

This control is covered by the Integration marketplace and connection reference workflow.

Applies to /admin/integrations

Requirements and capabilities

This control is covered by the Integration marketplace and connection reference workflow.

Applies to /admin/integrations/:integrationSlug

Connection and inherited status

This control is covered by the Integration marketplace and connection reference workflow.

Applies to /admin/integrations/:integrationSlug

Manage action availability

This control is covered by the Integration marketplace and connection reference workflow.

Applies to /admin/integrations/:integrationSlug

Connect and provider authorization

This control is covered by the Integration marketplace and connection reference workflow.

Applies to /admin/integrations/:integrationSlug/manage

Asset selection and save

This control is covered by the Integration marketplace and connection reference workflow.

Applies to /admin/integrations/:integrationSlug/manage

Disconnect and reconnect consequences

This control is covered by the Integration marketplace and connection reference workflow.

Applies to /admin/integrations/:integrationSlug/manage

Provider, permission, and sync errors

This control is covered by the Integration marketplace and connection reference workflow.

Applies to /admin/integrations/:integrationSlug/manage

What happens next

Your change is available within the scope you selected.

Warnings

• Disconnecting can stop dependent reviews, publishing, POS, or data synchronization.
• Never paste provider tokens or credentials into Support.

Troubleshooting

• Needs attention means authorization, asset selection, or a provider response requires action.
• A child location may inherit an eligible parent connection but still require a mapped provider asset.
• For needs-attention and disconnected states, verify the selected scope, access level, required connection, and displayed validation or freshness status; retry once after correcting the cause, then create a context-rich Support case if it continues.
• For provider, permission, and sync errors, verify the selected scope, access level, required connection, and displayed validation or freshness status; retry once after correcting the cause, then create a context-rich Support case if it continues.