---
title: Account roles
description: "See who can do what across MangoMap. Compare the Viewer, Editor, Admin, and Owner roles, and how roles combine with access groups."
---

Use account roles to see what `Viewer`, `Editor`, `Admin`, and `Owner` users can do. Roles set the actions a user may take. Access groups set which maps and datasets those actions apply to. Use this section when you need an account-wide answer.

The role-by-role mechanics for individual surfaces live with those surfaces:

- Per-map sharing and access toggles are in [Map access](/docs/map-access).
- Per-dataset sharing and access toggles are in [Dataset access](/docs/dataset-access).
- Inviting users, changing roles, and access-group management are in [Team management](/docs/managing-team).
- Account-wide branding, localisation, and other owner-only settings are in [Customisation](/docs/customisation).

The invite and update forms can assign `Admin`, `Editor`, or `Viewer`. The `Owner` role is not assignable from those forms.

## Start here

**[How account roles work](/docs/account-roles/concepts-account-roles)**

The four roles, how role and group access combine, the creator and owner overrides, and why some surfaces are owner-only.

**[Account roles reference](/docs/account-roles/account-roles-reference)**

The canonical matrix: every action against every role, with creator and owner overrides marked.