Orgs & seats

An Org plan gives everyone in your GitHub organisation access to the same private ontologies, billed per seat. Seats keep themselves in step with your organisation — there’s no separate list to maintain.

Your organisation is your GitHub organisation#

There is no separate Ontoshire organisation to create, and no invitations to send. Ontoshire reads your GitHub organisation memberships when you sign in, so whoever is in the organisation on GitHub is who has access here.

If you belong to several organisations, each one is its own context with its own plan and its own invoice. Switch between them on your billing page.

Who can manage the subscription#

Anyone with the Owner role in the GitHub organisation can start, change, or cancel the Org subscription. Every other member can see which plan the organisation is on, but not change it — the same split GitHub itself uses.

What counts as a seat#

A seat is an organisation member who has signed in to Ontoshire at least once. Your GitHub organisation might have fifty people in it; if six of them use Ontoshire, you pay for six. Nobody is billed for a colleague who has never opened the product.

An Org subscription always includes at least one seat, so an organisation on the Org plan is never billed for zero.

When the seat count changes#

You never adjust the number by hand. Ontoshire re-derives it from your organisation at each of these moments:

Because the count is always derived from membership, it can’t drift out of step with who actually has access. There is no separate seat limit to run out of.

How changes are billed#

Seat changes are prorated onto your next invoice, in both directions. Add a colleague mid-month and you’re charged for the part of the month they had access; the card is never charged the moment they sign in. Remove someone and the unused part of their seat is credited back the same way.

This is the model GitHub uses for its own per-seat plans, and it means an ordinary member’s first sign-in can never produce a surprise charge.

When someone leaves#

Removing someone from the GitHub organisation is what removes their Ontoshire access — including access through an API token they had already created. There is nothing to revoke separately.

That takes effect the next time the organisation’s membership is checked. If you want it applied immediately, an owner can open the billing page, which re-reads the roster from GitHub on the spot. Otherwise it applies the next time that person signs in.

Their own ontologies, published under their personal account, are unaffected — leaving an organisation only ends access to that organisation’s shared private ontologies.

Cancelling#

An owner can cancel from the billing page. Before you confirm, Ontoshire shows how many private ontologies the organisation has and the date they would lock. Nothing is deleted and nothing is published: the ontologies stay private and simply stop resolving for validation and imports at the end of the period you’ve already paid for. Members can still view and export them, and resubscribing restores everything.

An Org subscription runs until it is cancelled. It doesn’t stop on its own when people leave or when the organisation stops using Ontoshire — an organisation with no remaining members still bills for a single seat until someone cancels it.

If your GitHub organisation is deleted#

You can still cancel it. Whoever most recently set up or managed the organisation’s billing keeps the ability to cancel from their own billing page, even after the organisation itself is gone from GitHub. Sign in as that person and cancel as normal.

If that isn’t possible — the person has left, or nobody can reach the subscription — email support@ontoshire.com and we’ll cancel it for you. Don’t leave it running.