Organisation portal
Pro, Team and Enterprise organisations get a portal at app.spendctl.dev. It shows what your sidecars report in their daily check-ins, who in your team can sign in, and your licence keys. It is never on the payment path: payments, policy, approvals and the ledger stay in the sidecar you run, and the portal sees only the five numbers a check-in sends (Privacy).
Signing in
Section titled “Signing in”There are no passwords.
- The first time, enter the e-mail address you paid with (or the one you were invited with) and open the link we mail you. It works once, for 15 minutes; an invitation link works for 7 days.
- Add a passkey on the Account page. From then on, sign-in is your device’s lock: Touch ID, Windows Hello, your phone or a security key. Add one per device.
Lost every device? Ask for a new link with your address and add a new passkey. Sign out everywhere ends every session of your address on every device.
| Page | What it shows |
|---|---|
| Overview | Plan, paid-through date, seats, licence status, this month’s governed payments against the plan limit |
| Sidecars | Each sidecar that checked in: its random id, version, agents, this month’s count, last check-in; flags a version too old to verify renewed keys and a sidecar that went quiet |
| Usage | The last 13 months: governed payments, share of the limit, sidecars, the largest policy file |
| Members | Who can sign in, with role and status; owners invite and remove people |
| Keys | Your licence keys by id, never the key itself; owners can issue a new one |
| Billing | Plan and the Stripe billing portal for card, invoices and cancellation (owners) |
| Account | Your passkeys and sessions |
Seats and roles
Section titled “Seats and roles”A seat is a person who can sign in. Pro includes 3 seats, Team 25, Enterprise as agreed. A pending invitation holds a seat. If a plan change leaves more people than seats, the newest members are suspended (never an owner); nothing is deleted, and an owner can reinstate someone once a seat is free.
- Owners invite and remove people, change roles, issue licence keys and manage billing. An organisation always keeps at least one owner.
- Admins will manage policies and approvals when those move to the portal; until then they see what members see.
- Members can see every page.
Replacing a licence key
Section titled “Replacing a licence key”A key renews itself at every daily check-in, so you only need a new one if a key leaked or someone who had it left. On the Keys page an owner chooses Issue a new key:
- the new key is mailed to that owner, never shown in the page;
- every previous key keeps working for 24 hours and is not renewed in the meantime; then it stops, and a sidecar still using it falls back to the Free limits at its next check-in;
- set the new key on each sidecar before then:
npx spendctl@latest license set <key>.
An organisation can issue three keys a day.