The admin area

/admin is where an installation of Vibeforce is run: the AI everyone builds on, the playbooks the builder follows, the design library users pick from, 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:

1. Your email is on the installation's administrator list. This is set in the server's configuration, or through an ADMIN_EMAILS environment variable holding a comma-separated list.
2. An administrator at your Vibeforce 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 /admin area. 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 five pages, and two links out

Page	What it controls
Overview (this page)	Read-only statistics and recent signups.
Skills	The playbooks injected into the builder's system prompt on every build.
Designs	The looks users choose from when they start a project.
Settings	Where user apps run — local or cloud sandboxes.

Three more entries are links out to the Vibeforce account service rather than pages here: Platform AI ↗, Model catalog ↗ and AI tokens ↗. Vibeforce holds no provider key, no model catalog and no token ledger, so there is nothing to administer locally — only somewhere to go. See Platform AI and The token allowance, for administrators.

Billing is shared with Openbook. Use the Vibeforce account service and the selected workspace’s current plan and work-credit display. See billing administration.

The chrome: a top bar with Back to Vibeforce, a shield icon and Platform admin; a sidebar with those seven 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 Vibeforce 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
Tokens in builds	Tokens in and out across every run ever, added together.	The two figures separately.

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 the platform's AI configuration and at Settings. Note that failures in a self-hosted organization are that organization's key to fix, not yours.

Tokens in builds is what this product measured, not what the platform was billed. It counts every run, self-hosted ones included, because it is Vibeforce's own receipt. What the platform actually paid for is at the account service's AI tokens ↗ page, against each account's allowance — and a build in a self-hosted organization costs the platform nothing at all. If this figure is large and the billed figure there is small, organizations have switched themselves to self hosted.

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:

1. Platform AI ↗ — at the Vibeforce account service: add a provider key, browse its models, add one that supports tools, and star it as the default. Do this first. Until it is done, no organization can choose managed mode, so nothing builds unless an organization brings its own key.
2. Settings — choose local or cloud sandboxes. Cloud needs an API key.
3. AI tokens ↗ — at the account service: set the default token allowance, whether it turns over monthly or weekly, and what a generated image costs.
4. Designs — eight designs in five categories are seeded on first start. Review them, and add any of your own.
5. Skills — five playbooks are seeded on first start. Read them; they shape every build on the installation.

Next

• Platform AI.
• The token allowance, for administrators.
• AI configuration — what an organization decides for itself.