Admin
A working admin console from day one, with every tab behind its own permission.
The problem
Without an admin, every support request becomes a SQL query. Building one is weeks of tables, forms, and permission checks nobody asked for.
What Bones does
/admin in the web app has eight tabs. Each one is gated by its own page.admin.* feature, so a role can see some tabs and not others.
| Tab | What you do there |
|---|---|
| Users | Search, sort, and page through every account. Change roles and deactivate users |
| Organizations | Manage every organization and its members |
| Feature Flags | Turn features on and off for everyone |
| Permissions | Grant features to roles |
| Roles | Create, delete, and reorder roles |
| Site Settings | Turn sign-in methods on and off |
| Terms & Conditions | Post a new version of the terms. Old versions are kept |
| Blog | Write, publish, and upload media for the blog |
Search, sort, and pagination on Users run on the server, so they work on the whole table, not just the page you loaded.
How it compares
Retool or a database GUI gets you a table fast, but it sits outside your permission model. The Bones admin uses the same session, features, and server checks as the rest of the app.