Skip to main content
Teams is billed per seat, monthly, from a minimum of three seats, in the currency your billing country resolves to.

​
The price

One catalogue resolves every price, from the billing country stored on the workspace. You cannot pick a cheaper zone by changing a setting, and the same catalogue is what the public pricing page reads. Your workspace’s zone and currency are shown on its billing screen, alongside the note that the billing service resolved them.

​
Seats, and what holds one

A seat is held by an active member or a pending invitation. Revoking an invitation releases its seat immediately. That is why an invitation can be refused: five invitations against three seats will not all succeed, and Iris Code tells you which ones did.

​
Adding seats

Adding seats is a two-step flow, on purpose.
1

You are quoted

Iris Code works out the prorated amount for the days left in the period you have already paid for, and shows it before anything is charged. The figure separates what is charged now from what your renewal becomes.
2

You confirm

The approved figure is sent back with the request. If proration has moved since the quote was shown, the change is refused and you are asked to review a fresh one, so a card is never charged an amount nobody saw.
If your workspace has a card on file the difference is charged to it in place, and your renewal date does not move. If it does not, you are sent to a hosted checkout instead.
You owe the difference for the remainder of the current period, not a fresh full month. Charging the whole new amount would bill you twice for days you already own.

​
Removing seats

Reductions are scheduled for the next renewal rather than applied now. Access stays at the current seat count until then, and the next renewal bills the lower amount. Nothing is refunded, because the period was already paid for, and nobody loses access mid-period as a side effect of a billing change. The billing screen shows the pending reduction and its effective date. You cannot reduce below the members and pending invitations you actually have, or below the three-seat minimum.

​
Renewals

Iris Code charges the card on file on its own schedule, for the exact seat total. You will see one charge per period covering every seat, and the workspace’s own billing history is on the billing screen, so a finance team does not need a payment-provider login to read it.

​
If a payment fails

1

A 7-day grace window opens

Every member keeps Pro. Nothing changes for anyone using the product, and the workspace owner is emailed.
2

Retries happen inside the window

A declined card is retried. A payment whose outcome could not be confirmed is not retried until it has been verified with the provider, so a card is never charged twice for the same period.
3

After the window, access becomes read-only

The entitlement stops granting Pro. Members drop to Free in their editors, cloud audits stop, and existing reports remain readable. Paying restores everything immediately.

​
Cancelling

Cancelling stops the next charge and leaves access running to the end of the period you have paid for. The billing screen shows the date access ends. You can reactivate before then and nothing is lost. A workspace cannot be deleted while a subscription is still running - cancel first.

​
Members who pay for Pro themselves

If a member also has their own Pro subscription, their editor is covered twice. Iris Code says so on their billing screen rather than letting them discover it on a statement. It is not always waste: a personal subscription is the only thing that cloud-audits their own repositories, while the seat covers the team’s. See Team entitlement.