---
title: How customisation works in MangoMap
description: "Understand the account-wide settings that control branding, portal copy, custom domains, and analytics. Only the account owner can change them."
sidebar:
  label: "How customisation works"
---

The `Customisation` menu groups account settings that change MangoMap's look and language. Set them once, and the change applies everywhere.
**Account-wide**

A change here affects every map, dataset, and portal page in the account.

**Owner-only**

Only the account owner can open these pages.

## What's in the menu

- Global settings/
  - Customisation/
    - Brand
    - Localisation
    - Domain & whitelabel
    - Portal config
    - Analytics

| Menu item | What it controls |
| --- | --- |
| `Brand` | The company logo, theme colour, primary accent colour, and the colour used to highlight selected map features. |
| `Localisation` | The text labels MangoMap shows on portal pages, map pages, dataset pages, and shared UI elements. |
| `Domain & whitelabel` | The custom domain MangoMap is served on, and the toggle to remove Mango logos and branding from maps, admin pages, page titles, and the sign-in page. |
| `Portal config` | The public portal's name, default layout, default sort order, banner copy, and footer. |
| `Analytics` | A Google Analytics 4 Measurement ID for tracking map and data views. |

## Who can use it

The `Customisation` menu is owner-only. `Admin`, `Editor`, and `Viewer` users cannot open any of these pages, even though they can otherwise create maps, edit data, and use everything else MangoMap offers.

If you need a customisation change and you are not the owner, ask the account owner to make it for you. See [How team management and account roles work in MangoMap](/docs/managing-team/concepts-team-and-roles) for the role hierarchy.

## Account-wide, not per-map

Customisation settings belong to the account, not to maps or datasets. This means:

- A new logo replaces the logo everywhere it appears, on every map and every portal page.
- A new theme colour applies across the product, including in dataset and portal UI.
- Text overrides set in `Localisation` change the words on every map's UI, the portal, and dataset pages.
- Connecting a custom domain makes every account page work on that domain. With `Remove Mango branding` on, it also becomes the domain in every public link the account gives out.

The admin sidebar has no per-map customisation page. Use the map's own `Map settings` for map-specific options.

## Defaults on a fresh account

A new MangoMap account starts with empty customisation. No logo or preset theme is set, so no logo shows in the portal header, the map header, or on the account sign-in page; the primary colour falls back to the MangoMap default; localisation is off; no custom domain is connected; the portal name and copy are empty; analytics is not connected.

You can leave any page untouched. The only page where blank values are user-visible is `Portal config` — an empty portal name shows up in the public portal header.

## Premium gates

Only the `Analytics` page depends on your subscription tier. If your subscription does not include the Google Analytics integration, the page shows an upgrade prompt instead of the form. See [How subscription and billing work in MangoMap](/docs/subscription-and-billing/concepts-subscription-and-billing) for plans and what each includes.

The other four pages — `Brand`, `Localisation`, `Domain & whitelabel`, and `Portal config` — open for any owner. They are owner-only, with no plan gate.

## How customisation interacts with map and dataset access

Customisation does not change map or dataset access:

- Changing a colour does not change who can view or edit anything.
- Connecting a custom domain does not change who can view or edit anything; access still follows the rules in [Map access](/docs/map-access) and [Dataset access](/docs/dataset-access).
- Removing Mango branding hides Mango logos but does not change permissions.

If you want to control who can open a public map or download a dataset, set those rules on the map or dataset itself, not in `Customisation`.

## Saving changes

Most customisation pages save automatically when you change a control:

- `Brand`, `Localisation`, `Domain & whitelabel`, and `Portal config` use auto-save. The page has no `Save` button; changes save as you make them.
- `Analytics` uses an explicit `Save Changes` button. Click `Cancel` to discard pending edits.

## Related

- [Customisation menu reference](/docs/customisation/customisation-menu-reference)
- [How team management and account roles work in MangoMap](/docs/managing-team/concepts-team-and-roles)
- [Account roles reference](/docs/account-roles/account-roles-reference) - the canonical "who can do what" matrix across team, customisation, maps, and datasets.
- [How map access works in MangoMap](/docs/map-access/concepts-map-access)
- [How dataset access works in MangoMap](/docs/dataset-access/concepts-dataset-access)