Skip to content
Manybases
esc

Search pages and sections. Try a tool name, an error code, a route.

↑↓ navigate↵ openesc close
  1. Dashboard
  2. Screens
  3. Project settings
Docs

Dashboard · Screens

Project settings

General configuration, data location and lifecycle.

General#

  • Project name — displayed in the dashboard and to your agent. Saving a name needs no confirmation.
  • App URL — the public address of your app, https://…/. Invitation links are built from it, and the first site deployment fills it in when it is empty. Saving a new one opens a confirmation — "This changes what every user of this app opens" — single-use, covering this exact URL only, expiring in 5 minutes.
  • Project ID — the reference used in API routes and by your agent.
  • Region — where this project's data lives. Fixed at creation.

Export#

Your data leaves whenever you want — that is the point. You get a zip: a dump.sql you can restore anywhere, your files, and a manifest of your access presets. Outgrown the 10-user cap? Export, then import into Postgres — the export keeps your table names and access presets, so the mapping is mechanical. What the zip holds exactly, and its current bound on the number of files: Export.

Danger zone#

Delete this project removes its tables, rows, users, spaces, files and keys, and takes down its edge functions and its site. Export first — this cannot be undone. Type the project's name to confirm, then confirm again: "This destroys the whole project" — the confirmation covers this project only, and expires in 5 minutes.