Branding
Set brand colours and logo, plus company-wide rental status, availability, and diary colours from Admin › Setup › Branding.
Overview
Branding controls the visual identity shown in the application chrome — four brand colours and an optional logo — and the Status & schedule colours used on rental statuses, the availability grid, and diary markers and phase seed defaults. A suggested palette derived from your accent colour is offered alongside the brand pickers so a coherent scheme is one click away. Colours are company-wide; there are no per-warehouse overrides.
Where it lives
Route: /admin/settings/branding (admin.settings.branding)
Open Admin → Setup → Branding. Requires admin access. The page is split into Logo, Brand Colours, and Status & schedule colours tabs; each tab has its own save action.
Key fields
| Field | Setting key | Notes |
|---|---|---|
| Primary Colour | branding.primary_colour |
Hex #RRGGBB — navigation and app chrome |
| Accent Colour | branding.accent_colour |
Hex #RRGGBB — buttons, links, focus rings; the palette is derived from this |
| Secondary Colour | branding.secondary_colour |
Hex #RRGGBB — supporting colour for opt-in badges and chips |
| Tertiary Colour | branding.tertiary_colour |
Hex #RRGGBB — quiet tint for surfaces and highlights |
| Company Logo | branding.logo_path |
PNG, JPG, SVG/SVGZ, or WebP up to 2MB |
All four colours are validated against #RRGGBB and stored in the branding settings group (Settings Registry).
SVG and SVGZ logos are safety-checked and rasterised with a transparent background on upload, then pass through the same document-safe normalisation pipeline as raster images. Hosts without Imagick and an SVG delegate return a clear validation message instead of failing the upload unexpectedly.
Suggested palette
The Suggested Palette panel derives three colours from the current accent using the palette colour rules and re-derives them live as you change the accent:
| Suggestion | How it is derived |
|---|---|
| Primary | The accent's own hue, deepened — saturation 0.35–0.60, lightness 0.18–0.30, then darkened in steps until white text on it reaches 4.5:1 (WCAG AA) |
| Secondary | Analogous — the accent hue rotated +30°, saturation clamped 0.35–0.75, lightness 0.38–0.52 |
| Tertiary | Complementary tint — the accent hue rotated +180°, desaturated to 45% of the accent and lightened into a 0.62–0.82 band |
Greys and near-monochrome accents are lifted to a saturation floor first, so an achromatic accent still yields usable brand colours rather than more grey.
Apply copies one suggestion into its editable field; Apply all suggestions copies all three. Nothing is persisted until Save Changes — suggestions are a starting point, not a lock.
Where the colours are used
Every shell that renders app CSS includes resources/views/partials/brand-colours.blade.php, which publishes the palette as custom properties on :root — for guests on the auth pages exactly as for signed-in users:
| Variable | Meaning |
|---|---|
--brand-primary / --brand-accent |
The raw primary and accent colours |
--brand-secondary / --brand-tertiary |
The raw secondary and tertiary colours |
--brand-*-ink |
Contrast-corrected variants for text, headings, and active states on light surfaces |
--brand-on-* |
The foreground colour to use on top of each brand fill |
Secondary and tertiary are deliberately opt-in: nothing painted from --navy* or --blue* reads them, so setting them can never repaint the navigation, sidebar, or primary CTAs. They are consumed only by these helper classes (see the Component Library):
| Class | Use |
|---|---|
.s-badge-secondary |
Solid secondary badge with an accessible foreground |
.s-chip-secondary |
Pale secondary chip with a matching border and ink |
.s-tertiary-surface |
Subtle tertiary background panel with a soft border |
Status & schedule colours
The Status & schedule colours tab configures the three operational colour keys. Each swatch shows a live AA ink preview; contrast warnings are non-blocking (derived text colours still keep labels readable). Collecting matching the On Hire lime (#84cc16) is also a warning only, so the diary key can stay distinct.
Rental statuses
Rows come from the Rental Status list (built-ins plus any custom statuses). Colour and label save through the list-entry write path (list_entries.metadata.colour); identity keys (state, code, derives_from) stay frozen. Reset / Reset all to defaults restore the shipped enum colour without persisting until you save.
The status section requires option_lists.view to appear. Operators with option_lists.manage can also add a custom status (label, owning state, derives_from limited to a same-state built-in, colour), archive a custom row, or delete one that has never been used.
Deletion is stricter than "no rental sits on it now." A custom status that appears anywhere in recorded status history cannot be deleted — the attempt reports "This rental status has been used and cannot be deleted. Archive or rename it instead." Archiving is the intended way to retire a status that has been in service, so the historical trail stays readable. Custom statuses take composite codes from 50 upward, and a deleted status's code stays reserved rather than being handed to the next custom status.
Saving without option_lists.manage still writes availability and diary colours, and shows a notice that status colours were skipped. The same CRUD is available on GET/POST/PATCH/DELETE /api/v1/rental_statuses (option_lists.view / option_lists.manage plus static-data:read / static-data:write).
Availability
Four grid fills — Available, Warning, Shortage, Booked — plus the warning threshold (integer, default 2): cells at or below that quantity and still above zero use the warning colour. Stored in the colour settings group (colour.availability.*). CSS custom properties (--avail-*-bg, --avail-*-ink) are published from resources/views/partials/avail-colours.blade.php next to the brand-colour partial.
Diary & orders
The colour.diary.* phase swatches supply initial defaults when definitions are seeded. The rental diary displays the colours on the Rental phases definitions; changing a swatch does not update those definitions. Flag, marker and now-line swatches remain in colour.diary.*. The Legend preview shows the branding swatches.
| Field | Setting / storage | Default |
|---|---|---|
| Available | colour.availability.available |
#16a34a |
| Warning | colour.availability.warning |
#f59e0b |
| Shortage | colour.availability.shortage |
#dc2626 |
| Booked | colour.availability.booked |
#3f3f46 |
| Warning threshold | colour.availability.warning_threshold |
2 |
| Short threshold | colour.availability.short_threshold |
0 — free stock below this counts as short; 0 flags only real (negative) shortages |
| Delivery | colour.diary.delivery |
#3b82f6 |
| In Use | colour.diary.in_use |
#8b5cf6 |
| Collection | colour.diary.collection |
#06b6d4 |
| Collecting | colour.diary.collecting |
#16a34a |
| Returning | colour.diary.returning |
#0891b2 |
| Prep | colour.diary.prep |
#4f46e5 |
| Load | colour.diary.load |
#1d4ed8 |
| Setup | colour.diary.setup |
#38bdf8 |
| Takedown | colour.diary.takedown |
#a78bfa |
| Unload | colour.diary.unload |
#0e7490 |
| Deprep | colour.diary.deprep |
#c026d3 |
| Repair | colour.diary.repair |
#9333ea |
| Sub-hire | colour.diary.sub_hire |
#0284c7 |
| Transfer | colour.diary.transfer |
#6366f1 |
| Now Line | colour.diary.now_line |
#db2777 |
Workflows
- Save Changes on the Logo tab records the uploaded logo on the resolved public disk under
branding/and detects transparency. - Save Changes on the Brand Colours tab persists all four brand colours.
- Both logo and brand-colour saves reload the page on the same tab so the header picks the change up.
- Apply / Apply all suggestions fill the pickers from the derived palette without saving.
- Remove deletes the stored file and clears logo settings, then reloads so the header updates.
- Save status & schedule colours writes the
coloursettings group and, when the operator can manage lists, updates rental-status colours and labels. The rental-status registry cache is busted on every list-entry save so recolours show immediately.
Documents
Document rendering resolves all four colours from the most specific available source. Primary uses template → warehouse → branding.primary_colour → document default; secondary uses template → warehouse → branding.secondary_colour → document default; accent and tertiary use template → their company-wide branding setting → document default. Logos use template → warehouse → branding.logo_path, so the company logo is the final configured rung before rendering without one. See Documents & Templates for the exact fallback values, embedded data-URI behaviour, and the external document types that display the logo.
At a glance
Customise your company's visual identity with brand colours and a logo, plus company-wide rental status, availability, and diary colours.
| Field | Description | Default |
|---|---|---|
| Primary Colour | Main brand colour (hex) | #1e3a5f |
| Accent Colour | Accent brand colour (hex) | #047857 |
| Secondary Colour | Supporting brand colour (hex) | #188eaa |
| Tertiary Colour | Additional supporting brand colour (hex) | #c07c91 |
| Logo | PNG, JPG, SVG, or WebP up to 2MB | None |
| Logo has transparency | Detected when the logo is normalised and stored as branding.logo_has_transparency |
false |
You can upload a new logo, preview it, or remove the existing one. Removing a logo deletes the file from storage.