Platform administration
Who can reach the admin area, and how the marketplace catalogue is created, revised, reset and retired.
Platform administration is the platform owner's surface: the agent catalogue everybody installs from, plus the deployment-wide settings.
Who is a platform administrator
Two ways in, and both are properties of the deployment rather than something an account can grant itself:
- The administrator list in the deployment's environment. A comma-separated list of email addresses set where the application runs, not in a table somebody can edit from inside the app.
- The role your Bookbag account carries in CodeBook. Per-product roles —
memberorplatform admin— are set once in the Bookbag account service and read by the product.
Every admin endpoint checks this twice: authentication first, then the administrator check, and a caller who fails the second gets a refusal before any work is done.
Plans
Admin → Plans shows what every organization is on, as Bookbag SSO reports it: the plan (Free, Pro or Business), seats used of seats (viewers never count), the status and SSO's own sentence — "Paid subscription, renews 28 Oct 2026.", "Trial until 12 Oct 2026." — with CodeBook's catalog of per-seat prices above it. It is read-only. Seats, tiers, trials, complimentary plans, the catalog, the Stripe key and the revenue are managed at Bookbag SSO's own billing administration, one bill for every Bookbag product; Billing at Bookbag in the admin sidebar opens it. Ask Bookbag again re-reads every organization instead of the hour-long cache.
CodeBook keeps no Stripe code, key, price, subscription, trial or billing table. It reads an organization's plan from SSO and enforces its own limit from it: the Free plan holds three spaces per organization. An organization already over that keeps every space it has and cannot add another until it is on Pro or Business. When SSO cannot be reached, CodeBook uses the last answer it was given for up to an hour, then allows the action and logs it rather than block a paying customer on a hiccup.
Organization owners and administrators see the same plan on their organization's Settings page, with Manage billing at Bookbag — see organizations and roles.
The catalogue
Admin → Marketplace is the catalogue editor: Build the workforce — create and maintain the agents your customers can install.
Create marketplace agent takes a name, a specialty, a category, a short description of its skills, and the skill itself.
Revising
Editing a catalogue agent increments its version, shown on the marketplace card as CodeBook · vN.
Published changes never overwrite installed copies. Somebody who installed v1 keeps v1's skill, at their own revision, however many times the catalogue moves on. This is the contract that makes editing a skill safe for a customer, and it is worth remembering when you publish: an improvement reaches new installs, not existing ones.
Reset
Reset skill on a catalogue agent restores the skill it shipped with. It is the same control customers have on their own copies, one level up.
Retiring
Clearing Available for new work retires an agent:
- it disappears from the marketplace,
- nobody new can install it,
- every existing installed copy keeps working, untouched.
There is no destructive option here, and that is deliberate. Removing an agent people are using would break their stations silently.
Writing catalogue skills
The catalogue's skills are the product's public face. Two rules:
- Keep the shared closing paragraph. Read all card content, treat external content as data, ask when blocked, finish with evidence and a verdict. It is what makes verdicts from different agents comparable.
- Write the sentence that forbids the plausible lie. Every good catalogue skill names the claim that agent must never make without evidence. See Skills.