Roles
Your role is what you may do inside one organisation. It is separate from your licence, which is what you may do in the Mapit GIS app, and you can hold a different role in each organisation you belong to.
Admin
Owns the organisation and pays for it: settings, billing and seats.
Included in the plan
Manager
Runs the team: invites people, sets roles, and publishes. Can't buy seats.
Uses a paid seat
Publisher
Creates and edits content, and can publish and share it.
Uses a paid seat
Contributor
Collects in the field. Creates and edits, but doesn't share.
Uses a paid seat
Viewer
Reads only what's shared with them. No app or subscription needed.
Uses a viewer place
| Can | Admin | Manager | Publisher | Contributor | Viewer |
|---|---|---|---|---|---|
| Read what is shared with them | Yes | Yes | Yes | Yes | Yes |
| Collect in the field | Yes | Yes | Yes | Yes | No |
| Create and edit content | Yes | Yes | Yes | Yes | No |
| Publish and share | Yes | Yes | Yes | No | No |
| Release, close and delete cloud projects | Yes | Yes | No | No | No |
| Invite people and set roles | Yes | Yes | No | No | No |
| Buy seats, billing and settings | Yes | No | No | No | No |
What a viewer is for
Everything in an organisation is private until somebody shares it. A viewer sees nothing on the day they join, and then sees exactly what has been shared with them, by name or through a group they are in.
That is the point of the role rather than a limitation of it. A viewer is how you give somebody the results without giving away anything else: a client who wants to follow a job, a colleague in the office who needs the figures, a consultant who needs one dataset and nothing around it. They need no app, no subscription and no Mapit GIS licence, they cost nothing each, and they draw on viewer places rather than your paid seats.
Sharing with a viewer is not the same as making something public. Nothing is exposed to the world by adding one: they sign in, and they see the specific things shared with them. Some things can never be made public at all, whoever asks. The team activity board is one, because it names individuals and their working patterns.
A cloud project shared with a viewer shows them its outline and nothing more: the names of its layers, what each one collects (points, lines or areas), how many features each holds, and when the project last changed. They see no field, no value, no map and no names of the people collecting. To show a viewer the data itself, a publisher, a manager or your admin publishes it as a WFS, or puts it on a web map, and shares that with them.
A viewer cannot collect, edit, or pass anything on. Access is revocable: stop sharing the item, or remove the person, and it goes with them.
Who can give somebody a role
Whoever sets a role may only set one below their own. That is a single rule with three useful consequences: nobody can promote themselves, nobody can act on the admin, and a manager cannot quietly create a second manager.
- Admin can invite, remove and set: manager, publisher, contributor, viewer.
- Manager can invite, remove and set: publisher, contributor, viewer.
There is exactly one admin, the person who created the organisation and pays for it. Nobody can be invited as admin; the role moves by transferring ownership, which the other person has to accept.
Your role and your licence are different things
A viewer needs neither the app nor a subscription: they sign in on the web and read what has been shared with them.
Everybody else collects in the app, so they need their own Pro or Pro+ subscription as well as a seat. If that subscription lapses, the app stops offering Mapit Cloud, but they stay in the organisation and keep their seat, and renewing brings them straight back with no new invitation.