Managing an App
Every App has an admin panel: one place to see how it's doing and manage everything it owns. Click the App's name in its title bar and choose Manage…, and the panel slides up over the App.
When you're allowed to deploy the App, the panel's header also holds a redeploy button ("Redeploy app (migrations, routes, tools, agents)") that re-runs the App's migrations and re-registers its routes, tools, and agents in place.
The panel is also the best map of what an App can do. Even if you never touch most tabs, a walk through the sidebar tells you what's possible: shared databases, your own API, webhooks, AI agents, notifications. Each tab gets its own page in this section, with what it's for, how it works, and what to do when something's off.
The sidebar
Overview and Usage sit at the top; the rest group by what they manage:
| Group | Tabs | In one line |
|---|---|---|
| Overview | Is the App healthy, who uses it, what changed this week. | |
| Usage | What the App spends in AI credits, and on what. | |
| Documentation | The docs the App's author shipped with it; the tab appears only when the App includes a docs.html or README.md. | |
| Access | Sharing, Dependencies, Environment | Who can open the App, what data it's wired to, and the secrets it runs with. |
| Data | Storage, API Routes, API Docs, Webhooks, Channels, Embeddings | The App's own database, its server endpoints and their generated reference, the doors it opens to outside services, the live updates it pushes to open pages, and the vector indexes it keeps over its own data; the Embeddings tab appears on any server that supports embeddings, and lists nothing until the App declares a use case. |
| Automation | Tools, MCP, Agents, Messages | What the App does on its own, what outside AI clients may ask it, and every notification or email it has sent. |
| Diagnostics | Logs, Snapshots, Files | For when something needs a closer look, or undoing. |
Overview, Sharing, Usage, and Documentation stay available for every App. The other tabs belong to the Apps module and appear locked, with a note pointing to sales@entrinsik.com.
Where do I look when…
| Symptom | Start here |
|---|---|
| "Someone says they can't open the App" | Sharing: is the switch on, are they (or their team) listed, do they have the right role? |
| "The App shows an error about needing setup" | Dependencies: a slot is unbound or its resource was deleted. |
| "A feature that calls an outside service stopped working" | Environment: is the key it reads still set? Then Logs. |
| "Overview says Needs attention" | The facts under the verdict name the culprit (log errors, tool errors, error rate); each maps to a tab. |
| "I need to see or fix the App's data" | Storage: browse tables or run SQL right in the panel. |
| "A webhook stopped receiving events" | Webhooks: was its access key revoked, or were all webhook URLs rotated? |
| "The App's live figures stopped updating" | Channels: are browsers still subscribed, and is anything being rate-limited or refused? |
| "An automated job didn't run / sent nothing" | Agents for the run history, then Messages for delivery. |
| "I want to use this App from Claude or another AI client" | MCP: the address to connect to, and a snippet per client. |
| "How is this App meant to be configured or used?" | Documentation: the author's own docs, when the App ships them. |
| "I want to call the App's API from outside" | API Docs: the generated reference for the App's server routes, filterable to its public surface. |
| "Someone broke the App, undo it" | Snapshots: restore a known-good state. |
| "I want to change the App's icon, name, or description" | Overview: the identity card at the top of the tab. |
The Overview tab's health verdict is computed from the other tabs' data. When it says Needs attention, the facts under it ("2 tool errors", "5 log errors") tell you which tab to open next.