Members & Teams
An organization is a group of people working on the same data. Members & Teams is where you invite them, decide what each one may do, and organize them into teams.
Two surfaces, one for looking and one for changing
Section titled “Two surfaces, one for looking and one for changing”Members & Teams in the dashboard shows the state of the team: who is in, with which role, and how your licences stand. Every member can open it.
Settings, Organization, Members & Teams is where the changes happen: invitations, roles, spending caps and teams. It is for owners and admins.
Seeing your team belongs to everyone. Changing it belongs to the people responsible for it.
Inviting someone
Section titled “Inviting someone”Invite a teammate takes an email address and a role:
| Role | What it gives |
|---|---|
| Admin | Manages members and content, and works on the organization’s budget. |
| Editor | Creates and edits content, and works on the organization’s budget. |
| Viewer | Views the content shared with them. |
Owner is not in the list, because it is not given by invitation. It moves only through an ownership transfer. See Roles & permissions for the full matrix.
An invitation that has been sent but not yet accepted appears as a row of the members table, where you can send it again.
If your organization has no licence left for the role you picked, the invitation is refused and points you at your plan rather than failing without explanation.
A team is a named subset of your members, useful when different people work on different projects. Admins create them from the Teams tab.
Teams are what the sharing levels call groups: sharing an item with a team means everyone in it can read it, and nothing more. See Sharing for what each level opens.
Licences
Section titled “Licences”On a per-editor plan, your organization holds editor licences and viewer licences. A licence is held by a person: every member with a writing role, Owner, Admin or Editor, holds an editor licence, and every viewer holds a viewer licence.
The counter on the page shows how many of each you hold and how many are used. Inviting someone, accepting an invitation and changing a role are all checked against it.
The counter is read-only on purpose: seeing where you stand is part of seeing your organization, while buying or releasing a licence changes what you pay, so it lives with your plan. See Plans, usage & billing.
Spending caps
Section titled “Spending caps”On a per-editor plan, admins can set how many credits a member may spend, with a default that applies to everyone and a value per person where it makes sense. It keeps one enthusiastic afternoon from consuming the month’s budget.
The AI Assistant for a viewer
Section titled “The AI Assistant for a viewer”A viewer works without the AI assistants by default. An admin can enable the Map Builder AI Assistant for one viewer, from their row. Two things stay true when they do: the assistant’s use is billed to the organization’s credits, and the viewer still cannot save or change anything.
Removing someone
Section titled “Removing someone”Removing a member ends their access to the organization immediately and frees the licence they held. Everything they created there, projects, maps, data and services, is transferred to the organization owner. The same happens when a member leaves or deletes their account. An item can also be reattributed to someone else beforehand, from the item’s page.
Related pages
Section titled “Related pages”- Organizations: what an organization is, and what belongs to it.
- Roles & permissions: the full capability matrix.
- Sharing: what sharing with a team actually opens.
- Plans, usage & billing: licences, credits and invoices.