RotorLab logo RotorLabDocs

Seats, add-ons, and org purchases

All purchasing for an organization runs through its administrator. Your plan, user cap, billing details, and order history live on My account under Billing & plan; add-ons and bundles are bought under Add-ons; credit packs under API & credits. Members of your organization see none of this: their Billing and Add-ons sections show a note that purchases are handled by their organization administrator.

The central rule: entitlements belong to the organization, not to the person who bought them. One add-on purchase unlocks the capability for every user in your organization, and API credits go into one shared balance that everyone draws on.

Your plan and usage#

The Subscription card on Billing & plan shows your current plan: its name, price and billing period, and your organization's status. A trial plan shows a banner with the days left, or "Trial ended" once it expires. If the plan bundles add-ons, an Included add-ons line lists them; per-aircraft add-ons show the number of aircraft covered, or "(per aircraft)" when the plan includes the capability without granting slots.

Below the plan line, usage tiles show:

  • users: how many accounts your organization holds against the plan's cap, for example "7 / 10". Every account counts, active or not. When the cap is reached, adding a user fails until you remove someone or move to a larger plan.
  • groups: groups created against the plan's group limit.
  • API req / day: the daily API request quota per key holder.
  • included credits: API credits the plan grants, when it grants any.

Changing plans#

When other plans are on sale, a Request change control appears with a plan dropdown. Picking a paid plan takes you to checkout, and the new plan activates when payment completes. A plan with no charge is recorded as a request instead and the page confirms "Your plan change request has been submitted for approval"; the plan changes once the request is approved.

Subscription status#

On a subscription-billed plan with an active subscription, the card shows the state: "Active subscription, renews" with the date, "Payment past due. Update your card to keep access.", or the scheduled end date after a cancellation. Two buttons manage it:

  • Cancel at period end: schedules the cancellation. Access continues until the paid period runs out.
  • Resume subscription: undoes a scheduled cancellation before the period ends.

Billing details#

The Billing details card holds your billing contact, billing email, phone, tax or VAT ID, and address. These are used for invoicing and shared with the payment processor at checkout. Press Save billing details to store them.

The address fields follow the country you pick. Choose the country first: the field below it is then labelled the way that country labels it — State in the United States, Province in Canada, Prefecture in Japan, County in Ireland and the United Kingdom — and becomes a picker where a standard list exists. Countries that do not use an administrative area in a postal address, which is most of Europe, do not show the field at all, and countries with no postal system, such as Hong Kong and the United Arab Emirates, are not asked for a postal code. The tax field is labelled for the country too, as VAT number, ABN, GSTIN or EIN.

The postal code is checked against the country's format before it is saved. If it does not match, the save is refused and the field that needs attention is highlighted. This is deliberate: the address you store here is the address sent to the payment processor and printed on your invoice, so a code that cannot be right is caught now rather than at checkout.

If your organization is somewhere the payment processor cannot serve, the sign-up form says so at the time rather than letting you discover it during payment.

Orders and invoices#

The Orders & invoices table lists your organization's orders: date, item, amount, and status. Statuses are paid, pending, rejected, and canceled. A pending order is one waiting for payment or approval.

Buying add-ons and bundles#

Open My account and choose Add-ons. Bundle cards come first: each names what it includes, its price per period, and the saving against buying the parts separately. If your organization already holds everything in a bundle, the card says so instead of selling it again.

Below the bundles, one card per capability shows its current state:

  • included: the capability comes with your plan, and there is nothing to buy.
  • active: bought as an add-on, either one-time with no expiry or active until a renewal date.
  • not active: available to buy.

Only an organization admin sees buy buttons; members see "Only your organization administrator can purchase add-ons." Each button states the full price it will charge. For per-aircraft add-ons, an Aircraft quantity box sits beside the button and the button's total updates as you change the count.

Pressing a buy button takes you to checkout when the item has a price, or submits the order for approval when it does not. Once the order is paid or approved, the capability switches on for the entire organization at once.

Per-aircraft slots#

Some capabilities are sold by the aircraft rather than as an on/off switch: your organization holds a pool of slots and spends one per aircraft the feature is enabled for. The add-on card shows the pool, for example "3 of 5 aircraft slots in use, 2 free", or "Covers every aircraft on this account" for an unlimited grant.

Registering an aircraft in the Fleet manager consumes one aircraft registry slot. When every slot is in use, registering another aircraft fails with a message telling you how many slots you hold and how to proceed: add more slots under My account, or free one by removing an aircraft from the fleet. For other per-aircraft features, a slot is freed by switching the feature off for one of your aircraft instead.

Only an organization admin can add slots. When your organization already pays by subscription, adding a slot happens in place: the seat count on the subscription is raised, the payment provider prorates the part-period, and the slot is usable immediately. Without a subscription, the purchase goes through checkout, which creates the subscription with the slots on it.

Credit packs#

API credits are bought under API & credits, next to the balance and usage they feed. The Buy credits card lists the packs on sale; credits are spent only after the daily API quota is used up, at one credit per API call.

Credits are pooled per organization. Whoever buys a pack, the credits land in one shared balance that every key holder in the organization draws on, and the balance is labeled "shared credits". The balance does not depend on any one account staying around.

Orders with no charge#

When an order has no price, the purchase becomes a request: the page confirms it "has been submitted for approval" and the order appears as pending under Orders & invoices. The entitlement activates the moment the order is approved.