Review and connect an authorised integration

Console: Settings → Integrations. For the authorised owner or integration manager. The list groups Payments, Delivery, Accounting, Communications, and AI Assistants. Provider availability and completed setup vary by account/release; a listed category is not proof every connection flow is implemented.

Check before connecting

Use Add integration or Finish setup where offered. Verify provider, intended restaurant business/company, account, permissions, and Production / Test environment through the supported provider flow. Never paste payment keys, copied bearer tokens or another company's credentials into support notes.

A cancelled or rejected connection does not establish a connected account. Inspect the saved record and explicit setup/capability state before retrying. Connected, Setup required, Charges, and Payouts are different signals; Test mode is not live payment readiness. Review the location's assignment and a supported safe end-to-end test separately.

Use	Related guide
Local payment methods/readers	Payment setup
Direct delivery area vs delivery apps	Address and delivery
External assistant access	AI assistants
Accounting periods and journal outcomes	Month end

A third-party service manages its own access and responsibilities. Work on this TablePort business does not authorise modifying that provider account, another company, shared billing credentials, contracts, or deployment. Follow its company-specific authorised process where a separate action is required.

Pause, disconnect, and recovery

An integration can have an operational active switch distinct from deletion or provider disconnection. Read the actual confirmation: removing a connection can stop sending/receiving immediately, and payment capability can stop even while earlier payouts remain in transit. Review active work, alternative approved service, queued data, and intended scope before a consequential change.

If settings are marked coming soon or creation unavailable, use support for the supported setup rather than guessing private endpoints. After an uncertain save, OAuth result, sync or disconnect, inspect the same record and provider state before repeating it. Escalate with provider/business/location references, environment, capability status, last intended action and error through an authorised channel, keeping credentials and personal records private.

Browse more guides