Brand the guest portal with skins
A skin is the look of the guest portal around the portal’s own texts and form: colours, logo, background image, CSS, and optional header and footer HTML. Several portals can share one skin. This guide shows how to pick a built-in skin, create your own, and override the skin per portal.
Before you begin
Section titled “Before you begin”- At least one guest portal.
- An administrator role with
guest:write. - Your logo as PNG, JPEG, GIF, WebP or SVG.
Built-in skins
Section titled “Built-in skins”Built-in skins are read-only. To change one, duplicate it.
| Skin | Look |
|---|---|
| Classic | White card on a light background (the default for portals that name no skin). |
| Airowire | Airowire logo on an orange-to-purple gradient with a glass card. |
| Minimal | Flat, neutral and borderless. |
| Hospitality | Warm full-page gradient with a centred welcome card. |
| Dark | Dark background and cards with a bright accent. |
Step 1: Create a skin
Section titled “Step 1: Create a skin”-
Open Guests › Guest portal and select the Skins tab.
-
Either select Duplicate on a built-in skin, or select New skin and pick a skin in Start from (it copies that skin’s colours, images, CSS and HTML into the form).
-
Fill in:
Field Notes Name Required, up to 64 characters. The names of built-in skins are reserved. Description Up to 512 characters. Primary (buttons), Background, Text #rgbor#rrggbb. Empty uses the defaults (#0b5fff,#f4f6fb,#1d2433).Logo Shown above the card (CSS class .logo). Up to 1 MiB encoded.Background image Covers the page behind the card. Up to 1 MiB encoded. CSS Added after the portal’s own styles, so it can restyle everything. Up to 64 KiB. Header HTML Rendered at the top of the page, before main. Up to 32 KiB.Footer HTML Rendered at the bottom of the page, after main. Up to 32 KiB. -
Check the preview on the right and select Create skin.
The CSS can style these elements: main, .logo, .card, h1, h2,
label, input, button, .terms, .creds, footer, .powered. For
example:
.card { border-radius: 16px; box-shadow: 0 12px 30px rgba(0,0,0,.15); }button, .btn { border-radius: 12px; }footer { color: #555; }Step 2: Use the skin on a portal
Section titled “Step 2: Use the skin on a portal”- Open the portal (Guests › Guest portal › the portal) and select Branding.
- Pick the skin in Skin (under Built-in or Custom). Edit skins opens the Skins tab in a new browser tab; the reload button next to the list fetches skins you just created.
- Optional per-portal overrides:
- Browser title, Heading, Message, Button label (empty =
the default for the portal type, such as
RegisterorLog in) and Footer. - Primary (buttons), Background and Text colours. Empty uses the skin’s colours.
- Logo: overrides the skin’s logo. PNG, JPEG, GIF, WebP or SVG, up to 256 KiB encoded.
- Browser title, Heading, Message, Button label (empty =
the default for the portal type, such as
- Select Save changes.
What a skin may contain
Section titled “What a skin may contain”Skin HTML and CSS are administrator content, but the portal page is served with a strict content security policy, so a skin cannot run code in a visitor’s browser:
- No scripts.
<script>elements and event handlers (onclickand so on) in header or footer HTML do not run. - Images only from the portal or as
data:URIs. Logos and background images are embedded in the page; the portal loads no external images, fonts or style sheets. - CSS restrictions. Airgate refuses CSS that contains
</,@import,expression(orjavascript:URLs, with the errorcss must not contain </, @import, expression() or javascript: URLs. - Images must be base64
data:image/...URIs of type PNG, JPEG, GIF, WebP or SVG. The console’s upload buttons create them for you.
Delete a skin
Section titled “Delete a skin”Select Delete on the skin card. A skin that a portal uses cannot be
deleted: the console names the portals (skin is used by portal(s): …).
Switch those portals to another skin first. Built-in skins cannot be
deleted.
Verify
Section titled “Verify”Open the portal with Live preview in the portal editor. The preview renders the saved portal with its skin and a “Preview” banner.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Cause | Fix |
|---|---|---|
Save fails: name … is reserved for a built-in skin |
The name is Classic, Airowire, Minimal, Hospitality or Dark. |
Choose another name. |
Save fails: logo must be a base64 data:image URI of at most 1 MiB |
The image is too large or not an image type the portal accepts. | Compress the image or convert it to PNG or SVG. |
| A web font or external image does not show | The content security policy blocks external resources. | Embed the image with the upload button; use system fonts. |
| The portal shows the old look | The portal still names the previous skin, or the browser cached the page. | Check Branding › Skin and save; reload the portal. |
| “Unknown skin (…)” in the skin list | The portal names a skin that does not exist in this tenant (for example after copying a portal configuration). The portal falls back to Classic. | Pick an existing skin and save. |