Organizations & teams

How it fits together

• Every account is an organization. Signing up makes a personal one that you own, so a solo account works exactly as before. Rename it and invite people, or create another from the organization switcher in the dashboard.
• Plan, units and limits belong to the organization and are shared by every member and key. Plans keep their limits, applied per organization.
• API keys belong to the organization. A key records who created it and acts with their role (at most admin). It keeps working if they leave, until an admin revokes it; admins see every key on the API keys page.
• Teams group members. Maintainers manage their team; admins manage every team.
• The file library holds boundary exports members saved (save_file). A file is visible to the whole organization or restricted to its creator, admins and the teams and people it is shared with (share_file).

Roles

• viewer: Sees the files shared with the whole organization. Cannot call the API or create anything.
• member: Uses the API and the dashboard, creates files, teams and their own API keys.
• admin: Also invites and removes members, manages every key, team and setting, and billing.
• owner: Everything, including making admins and owners, transferring and deleting the organization.

An organization always keeps at least one owner: the last owner cannot leave or be demoted. Nobody can grant a role above their own.

Who can see a file

Your access to a library file is the highest of:

• your role, on files visible to the organization: viewers read, members write; admins and owners manage every file;
• admin, on files you saved;
• every share to you or to a team you are in (read, write or admin). Viewers never get more than read.

Read lets you list and download it, write lets you rename it, admin lets you change its visibility, share it and remove it from the library. The exported file itself is a permanent public CDN link, as with export_boundary; the library decides who finds it.

Inviting people

Admins invite by email from Organization → Members, with a role and optional teams. The link works once, for that address, for 7 days; the person signs in (or creates a free account) with it and joins. Pending invites can be resent (a new link) or revoked. Inviting, removing members, changing roles, teams, transferring and deleting an organization are always done by a person on the dashboard, never with a key or an agent.

Keys, the CLI and agents

• get_account returns the organization a call acts in and its role. list_orgs, list_members and list_teams read the rest; admins also have list_invites and list_audit_log.
• geocode login asks which organization the new key is for when you are in more than one, and so does connecting an app over MCP.
• With a dashboard or OAuth token you can pick the organization per request with X-Geocode-Org: <slug>; a key always acts in its own.
• A call your role does not allow answers 403 forbidden with required_role; a person-only op answers 403 person_only (see Errors).

Audit log

Membership, role, team, invite, API key, billing and sharing changes are recorded with who made them (a person, an API key, an OAuth app or the system) and kept for at least a year. Admins read it under Organization → Audit log.