The admin area
Who can reach /admin, what the six pages control, and what the Overview page's numbers actually count.
/admin is where an installation of Bookbag is run: the AI everyone builds on, the playbooks the builder follows, the design library users pick from, everyone's credits, and where sandboxes run.
It is a separate area with its own sidebar, deliberately not mixed into the workspace.
Who can reach it
Two independent ways in, either of which is enough:
- Your email is on the installation's administrator list. This is set in the server's configuration, or through an
ADMIN_EMAILSenvironment variable holding a comma-separated list. - An administrator at your Bookbag account has marked you as an admin for this product.
If you qualify, a Platform admin item appears in the sidebar and in your account menu. If you do not, it appears nowhere — and typing /admin sends you straight back to the dashboard, with the server answering "Platform admin access required."
One difference worth knowing if you administer an installation. Both routes open the whole
/adminarea. But cross-organization access to projects — the ability to open any project on the installation regardless of who owns it — is granted only to addresses on the installation's own administrator list. Someone designated an admin at the account service gets the admin pages but not that.
The six pages
| Page | What it controls |
|---|---|
| Overview (this page) | Read-only statistics and recent signups. |
| Platform AI | The provider keys and models that every user's builds run on, and what each model costs in credits. |
| Skills | The playbooks injected into the builder's system prompt on every build. |
| Designs | The looks users choose from when they start a project. |
| Credits | Platform defaults, everyone's balances, per-user allowances and adjustments, and each user's ledger. |
| Settings | Where user apps run — local or cloud sandboxes. |
The chrome: a top bar with Back to Bookbag, a shield icon and Platform admin; a sidebar with those six items; and a Back to app link at the bottom.
There is no user management and no email configuration in this build. Accounts, members, roles, devices and transactional email all live at the Bookbag account service and are administered there.
What the Overview page shows
Overview The platform at a glance.
Four cards:
| Card | What it counts | Its second line |
|---|---|---|
| Members | Every account that has ever signed in to this installation. | — |
| Projects | Projects that are not archived. | N archived |
| Build runs | Every run ever started, of any status. | N failed |
| Credits spent | The sum of credits charged across every run ever. | Total tokens in and out, added together. |
Then Recent signups: the five newest accounts, each showing a name — or the email, if no name is set — and email · date. Empty: No accounts yet.
All of these are all-time totals. There is no date range, no chart and no export. The page has no buttons at all.
Reading them usefully
Build runs against the failed count is the number to watch. A failure rate creeping up usually means the platform's active model has changed behaviour, its rate limits are being hit, or sandboxes are struggling. Look at Platform AI and Settings.
Credits spent against tokens tells you the effective rate the installation is running at. If credits spent is far higher than the token count suggests, a model has a high credit_cost set on the Platform AI page.
Archived projects is the only place archived projects are visible anywhere in the product. Users cannot see their own.
Setting up a new installation
In order:
- Platform AI — add a provider key, browse its models, add one that supports tools, and star it as the default. Nothing works until this is done; builds fail with a message that says exactly that.
- Settings — choose local or cloud sandboxes. Cloud needs an API key.
- Credits — set the monthly allowance, if 500 is not what you want.
- Designs — eight designs in five categories are seeded on first start. Review them, and add any of your own.
- Skills — five playbooks are seeded on first start. Read them; they shape every build on the installation.