2: Database admin

The Dashboard can browse and edit the databases behind your apps without a separate tool.

2.1: MySQL and SQLite

Both drivers the platform ships are supported: the shared MySQL database that backs most production apps, and the SQLite files individual apps use (the CMS demo's cms.db is one). You can inspect tables, read and edit rows, and run queries from inside the Dashboard.

2.2: Why it is built in

Because every Phlo model is schema-driven, the Dashboard renders database tables with the same machinery the CMS uses for content. Database admin is therefore not a bolted-on phpMyAdmin; it is the same list/record UI pointed at raw tables, with the same look and permissions.

2.3: Safety

Database access is an admin capability. Scope it with the permission system (next chapters) so only trusted users reach it, and prefer per-app SQLite files for things that do not need the shared database, which keeps blast radius small.