> ## 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.

# Booking portal settings

> Everything under Settings > Portal — what each tab controls, who can see it, and where to go for a given need.

The booking portal is the page where your customers book online: `https://book.eat-now.io/your-restaurant`, or the same page embedded on your website. Everything that shapes it is under **Settings > Portal**, split into tabs.

Changes apply to the portal **as soon as you save** — there is no publishing step. A customer who reloads the page sees the new version.

## The tabs

| Tab | What it controls | Details |
| - | - | - |
| **General** | Your portal link, website widget and QR code; the rules of the booking form (required contact details, modification, cancellation); the messages shown to customers. | [Share and embed](/portal/share-and-embed), [Booking rules](/portal/booking-rules), [Messages shown to guests](/portal/guest-messages) |
| **Design** | Logo, colours and background image of the portal. | [Design](/portal/design) |
| **Links** | The links in the portal header (menus, activities, your website…). | [Header links](/portal/header-links) |
| **Custom fields** | Extra questions added to the booking form. | [Custom fields](/portal/custom-fields) |
| **Activities** | The activities portal: activation, header message, cross-selling, resource groups. | [Activities portal](/portal/activities) |
| **Privatization** | The privatization request form. | [Privatization](/portal/privatization) |
| **Blacklist** | Customers who can no longer book online. | [Blacklist](/portal/blacklist) |

Looking for one specific setting? The [settings reference](/portal/reference) lists them all on a single page, with their exact label in English and French.

## Why a tab is missing

Tabs only appear when they apply to your restaurant:

* **General**, **Custom fields** and **Privatization** need the **restaurant reservations** feature.
* **Activities** needs the **Activities** feature, and the **Activity settings — Read** permission.
* **Design**, **Links** and **Blacklist** are always there.

To open the tabs you need the **Portal — Read** permission; to save, **Portal — Update** (**Activity settings — Update** for the Activities tab). Without it, the **Save** button stays disabled. Exception: the **Blacklist** tab has no separate update permission — anyone who can open it can add or remove customers. See [Permissions](/collaborators/permissions).

## Common needs

<CardGroup cols={2}>
  <Card title="Put the portal on my website" icon="code" href="/portal/share-and-embed">
    Embedded widget, floating button, tracking script, QR code.
  </Card>

  <Card title="Announce an event to customers" icon="speakerphone" href="/portal/guest-messages">
    Portal banner, service description or closure message: which one to use.
  </Card>

  <Card title="Make the phone number required" icon="phone" href="/portal/booking-rules">
    And the email, guest modifications, cancellation reasons.
  </Card>

  <Card title="Match the portal to my brand" icon="palette" href="/portal/design">
    Logo, colours, background image.
  </Card>

  <Card title="Ask customers an extra question" icon="forms" href="/portal/custom-fields">
    Allergies, occasion, high chair…
  </Card>

  <Card title="Stop a customer from booking online" icon="user-off" href="/portal/blacklist">
    Add them to the blacklist.
  </Card>
</CardGroup>

<Note>
  When and how many tables can be booked is **not** set here: it depends on your services. See [Shifts](/shifts/overview).
</Note>