> ## Documentation Index
> Fetch the complete documentation index at: https://docs.eat-now.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Choose and manage an integration

> Find the right connection and distinguish connecting, configuring and checking it.

Open **Settings → Integrations → General** on the correct restaurant. Search
filters the available service cards.

## Choose a connection

* **Payments**: [Stripe, Payzone or CMI](/integrations/payments).
* **Reputation**: [Google, Facebook and TripAdvisor](/integrations/reputation).
* **Communication**: [WhatsApp Business](/whatsapp/onboarding).
* **Portal measurement**:
  [Google Analytics, Tag Manager and Meta Pixel](/integrations/tracking).
* **POS**: [NowOS](/nowos/connect),
  [Lightspeed K Series](/lightspeed/reservation) or the other POS cards offered.

Connecting a payment provider does not automatically make shifts paid.
Connecting WhatsApp does not configure every message. Continue with the guide
for the relevant setting.

## Other registers through HubRise

On your register’s card, click **Connect**, follow the HubRise authorization in
the opened window and select the correct location. Return to EatNow to check the
connection.

Only one POS path can be connected per restaurant: NowOS, Lightspeed or HubRise.
If a card asks you to disconnect another register, coordinate that change with
EatNow. A connection alone does not validate all table mappings and exchanges.

## Other tabs

* [CSV imports](/integrations/imports) and
  [reservation exports](/reservations/export).
* [Printers](/operations/printers).
* [API keys](/integrations/api) and [webhooks](/integrations/webhooks), visible
  when the API feature is enabled.

## A button or tab is missing

Check integration permissions and the location’s enabled features. Connecting,
editing and disconnecting have separate permissions. Do not disconnect just as a
test; dependent exchanges may stop.