Seats, viewer places and storage
Your organisation has three separate pools of capacity, and they behave differently. Keeping them apart is what makes an invoice predictable.
Three pools
Paid seats hold the people who collect and publish: managers, publishers and contributors. A seat is typeless, so it holds any of those roles equally and changing somebody between them moves nothing.
Viewer places hold people who only read what you share with them. They need no app and no subscription, they cost nothing each, and they are sold in blocks of 50.
Storage holds what your crews collect. It is sold in packs of 10 GB and belongs to the organisation, not to any person: adding somebody brings no space with them, and removing somebody takes none away.
The admin’s own place is included in the plan and is drawn from no pool.
When storage is full
From nine tenths of your storage, admins and managers see how much is left. Once it is full, nothing new can be added: no new cloud project, from the app or the portal, and no new WFS. The admin is offered more storage; anybody else is asked to tell the admin.
Nothing else stops. Crews keep syncing, because field work is never refused, and releases, exports and downloads carry on. Closing, deleting and unpublishing always work, and deleting a project or a WFS you no longer need is the other way back under. A storage pack cannot be released while your organisation stores more than it would have without it.
Removing a person is not releasing a seat
This is the one that surprises people, so it is worth stating plainly.
- Adding a seat charges immediately, pro rated for the rest of the term.
- Removing a person frees their seat for somebody else and keeps paying for it.
- Releasing a seat takes it away there and then, and refunds nothing, because the term is already paid. What changes is your next renewal, which is lower. We ask you to confirm before doing it.
- Storage and viewer packs follow the same two rules: a new pack is charged at once, and releasing one takes the capacity away at once without a refund.
So “I removed three people and the bill did not change” is expected. They are two different buttons because they are two different decisions: one is about who is in the team, the other is about what you are paying for.
Who can buy
Only the admin buys and releases capacity, because only the admin pays. A manager can fill the seats that exist and will be told to ask when there are none left. What each role can do.
A member whose own subscription lapses keeps their seat, so their place is still held when they renew.