Organizations and members

The short answer

Signing up creates an organization with you as its owner. An organization has three roles: the owner, admins and members. Billing contact is not a role but a setting a member can have. Owners and admins invite people; a seat is used when an invitation is accepted, never when it is sent. People beyond the seat allowance join as free members. An organization can verify its email domain so colleagues can find it and ask to join, or join at once, without an invitation.

Roles

The owner can do everything, including closing the organization, changing roles and handing ownership to someone else. There is one owner.

Admins manage the organization’s people and set-up: invitations, members, counties, area clusters, verified domains and join requests, and which members may use the API. Only the owner may invite or appoint an admin.

Members use the product: they see the data their seat allows, save workspaces, use the organization’s clusters and, where an admin has allowed it, hold API keys.

Billing contact is a setting on a member. Changing the plan, the counties paid for, the seats, the API add-on or the card is for the owner and billing contacts. The app’s own “Who can do what” table on the Members screen sets out each permission.

Seats and invitations

An invitation is sent to one address and only that address can accept it. It expires after fourteen days; resending it issues a fresh link and the earlier one stops working. A seat is consumed on acceptance. If no seat is free, the person joins as a free member: they see nation and state figures at full code depth, in the app only, with no county detail and no file export, and a seat gives them both. Removing a member frees the seat at once, revokes their API keys and ends their sessions; clusters and counties they made stay with the organization.

Verified domains and joining

An owner or admin can claim the organization’s email domain. It is verified at once if an owner already holds a verified address on it, or by publishing a DNS TXT record the app gives you. Public providers such as gmail.com cannot be claimed, and a claim is not exclusive: several organizations may verify the same domain. The join policy is one of Off · invite only, Request · admin approves (the default) or Auto · joins at once. Approving a request seats the person if a seat is free; otherwise they join as a free member.

Leaving, handing over and closing

Any member can leave an organization they joined. Access ends at once and their API keys there are revoked; their own organization and any others are untouched. The last owner cannot leave; they hand the organization to someone else first, from Members → Manage → Transfer ownership. The new owner is seated and the old owner becomes an admin. If every owner has stopped signing in, an admin with a verified address on a verified domain can claim ownership after a seven-day notice, and any sign-in by an owner during that time cancels the claim.

Closing an organization is the owner’s alone. The subscription is cancelled at once with no refund, nobody can reach the organization any more and its API keys are revoked, and everyone stays signed in to their other organizations. Its counties, clusters, workspaces and billing history are kept, and the former owner can reopen it later.

Signing in safely is on account security. Keys are on API keys. What each plan includes is on plans.