Organizations

Everyone gets a personal organization on signup and administers it. A
department, lab or class is a second organization with more than one seat.

Its page carries a three-step list until the organization is set up: invite
your members, set your email domain, choose a plan. Each step ticks itself off
from the organization’s own state (a second member or a pending invitation, a
domain on record, an active plan); there is nothing to dismiss.

From your organization page you can:

  • Invite by email. Someone with an account joins immediately; someone
    without joins when they sign up.
  • Make someone an admin, or a member again, and remove people. An
    organization always keeps an admin: the last one can be neither demoted nor
    removed until someone else is promoted.
  • Set an email domain. Anyone signing up with a matching address joins
    automatically, once you have proven the domain with a DNS record
    (verified domains). Ask
    staff to set the domain itself. It’s a super-user setting, because it hands
    out seats without a human deciding.
  • Require two-factor authentication of every member, with a week to
    enrol (two-factor authentication).
  • Connect your identity provider, so members sign in at your institution
    (single sign-on).
  • Mint API keys. Keys belong to the organization, not to you, so they
    survive people leaving. Rotate a key to replace it with a new one that has
    the same scopes and allow list (the old one stops working at once), and
    revoke one you no longer need. Every mint, rotation and revocation, and
    every webhook endpoint added, re-enabled, removed or given a new signing
    secret, is in the organization’s audit log, with who did it; the log names
    the key by its label and prefix, never the key itself.

Seats and plans

The plan sets the seat limit; staff can override it per organization for a site
licence. Adding a member past the limit is refused rather than silently billed.

Access is the best plan across a member’s organizations. A student on a free
personal plan who is also in your covered department has the department’s
access. Removing them from the department removes it again.

Billing

Self-serve billing is Stripe Checkout plus the billing portal, operating on your
billing organization, or on any organization you administer when you open
billing from its page. Team and Institution plans are bought per seat and the
seat count can be changed any time. An institution that pays by invoice and
purchase order enters its billing contact, PO number, tax id and terms under
Invoicing on the organization page; staff then start a subscription that
Stripe bills by invoice, with the PO on it, and the organization is entitled
at once. A failed card renewal opens a fourteen-day grace period before the
paid data surfaces close; a late invoice only brings reminders. See
Billing and payments.