GuritaGurita

Appearance

Request access

Settings: Access & Rules, Appearance ​

Where: Settings → Guest Portal (/config/portal)

Who can access this: requires admin, or the Settings permission with the ability to update settings. Visible when the Guest Portal module is active (see Settings & Administration → Active Modules).

GuritaDashboardBookingTrip DatesCalendarOPERATIONSOccupancyPOSDiveCRMMANAGEMENTFinance ▾Master Data ▾Report ▾Settings ▴CompanyConfigurationAge BandsTranslationsAudit LogActive ModulesAI Assistant (MCP)BookingTemplatesGuest PortalSYSTEM OK←Guest PortalSearch bookings, guests, trips, agencies…⌘K▾+ Create🌐 ENGuest portalONLINEGlobal settings · apply to every property unless a property overrides them🌐Global · all properties▾⧉OPEN PORTALSAVEAccess & rulesWho gets into the portal and what guests may do there themselvesPortal activeLOGIN METHODSat least oneBooking no. + surnameNo account needed — ideal forone-time guestsMagic linkOne-time link by e-mail, nopassword neededAccountE-mail + password — all of aguest's bookings in one placeMAGIC-LINK EMAIL TEMPLATEBuilt-in text (no template)▾PORTAL ADDRESSiSlug and custom domain belong to the property. Choose aproperty to edit them.SELF-SERVICEGuests may cancelThe rate's cancellation terms still applyAppearanceApplies to the guest portalBRANDLogoSVG/PNG · darkChoose fileLogo lightSVG/PNG · on imageFaviconPNG · 512×512Cover imageJPG · 2400×900Live previewOverviewLoginOverviewExtrasPaymentsCheck-inDocumentsMessa…Hello AnnaYour welcome text appears here.Your tripStart online check-inCancel booking★Club ·Guest portal settings page

Global settings vs. per-property overrides ​

A Scope selector at the top switches between Global — the defaults every property uses unless it overrides them — and one specific property. Any field a property leaves untouched simply inherits the global value; a field it does override shows a small Custom for this asset marker, with a Reset to global action next to it that clears the override.

The header also shows:

  • An Online / Inactive status chip for whichever scope you're viewing.
  • Unsaved changes / Saved feedback.
  • Open portal, which opens the live portal for that scope in a new tab.
  • Save, which is blocked — with an explanation — if no login method is turned on, the brand colour or reception e-mail is invalid, or a slug is still a duplicate. Switching scope with unsaved changes asks you to confirm before discarding them.

Note: A handful of settings only make sense per property and are never part of the global defaults: the Portal address (slug/domain) below, and the team notification e-mail template further down — that one stays global-only even when you're editing a property.

This chapter, plus Settings: Modules, Texts, Live Preview, walks through every card in order.

Access & Rules ​

The first card controls who gets in and what they may do once they're there.

  • Portal active — the master switch for this scope. Turned off, guests only see a notice page with the property's contact details, and booking confirmation e-mails carry no portal link at all.
  • Login methods — three tiles, one per method described in Signing in: Booking no. + surname, Magic link, and Account. At least one must stay on, or saving is blocked. Turning Account on also reveals a short note that loyalty points are easier to follow with an account login — a hint, not a requirement, since loyalty never needs an account.
  • Magic-link email template — which mail template the one-time sign-in link uses (or the built-in text, if you haven't written one). Only shown while Magic link is on. Write or edit templates under Settings → Mail.
  • Portal address — see below.
  • Self-service — Guests may cancel, a single switch. When on, a cancellation is only offered to guests inside the rate's free-cancellation window (see Cancelling online) — there is no separate "always allow, rate's fee applies" option; a guest past the free period is simply told to contact the property.

Portal address ​

Each property (not the global scope) can have its own address:

  • Slug — a short, URL-safe identifier unique across your properties, used as …/portal/login?asset=<slug>.
  • Custom domain (optional) — for example portal.your-hotel.com. The domain needs a DNS entry pointing to Gurita before it will resolve; the settings page only accepts the domain text itself; see Known limitations for what it doesn't check.

In the global scope, this section instead lists one button per property to jump straight to that property's own address settings.

Appearance ​

Applies to the guest portal. Brand the portal with your own visuals, colour, type, and shape.

SettingWhat it does
Logo / Logo lightYour logo for light and dark/photo backgrounds.
FaviconThe browser-tab icon (PNG, 512×512 recommended).
Cover imageThe banner behind the Overview header (JPG, roughly 2400×900).
Hero imageThe image behind the sign-in page (JPG, roughly 1600×1200); falls back to the cover image if not set.
Brand colourPick a preset or enter a hex value; used for buttons, links, and active tabs. A contrast indicator warns when a colour is too light for buttons or only safe for large text. Status colours (open, paid, error) never change.
Headings / Body textA font per role, chosen from Montserrat, Roboto, DM Sans, Lora, or Source Serif 4.
CornersRound, Soft, or Sharp — the corner radius used across the portal's cards and buttons.
Page headerCover image, Brand colour, or Plain — see below.

Page header styles ​

The header style controls how the portal's main pages open:

  • Cover image — your cover photo behind the page title (falling back to the hero image, or a plain background, if neither is set). This is what the Overview tab uses. Login page uses the hero image instead.
  • Brand colour — a solid band in your brand colour, with the light-background logo placed on it.
  • Plain — a white header with a thin hairline border underneath — the quietest option, with no image or colour band.

Use each upload's Replace file / Remove actions to swap or clear an image at any time.