What you still manage in the builder
Vibe owns the UI. The classic builder still owns everything under it.
Still configured in Tadabase #
Vibe builds screens. The system of record — and most of what governs it — still lives in the classic builder. Change these there, and every interface picks them up:
- Tables, fields, and connections — your data model.
- Roles and row-level security — including the "Allow RLS Permission for API Access" switch.
- Workflows — email, external calls, multi-record updates, scheduled jobs.
- Email and PDF templates — Vibe triggers them; you design them in the builder.
- Users — accounts, roles, and status.
- Your plan and its limits — records, tables, fields, API access.
Limits to check on the builder side #
A Vibe app is still an app on your Tadabase plan. The caps enforced on the builder side apply to what your Vibe front-end can create:
| Limit | Where it bites |
|---|---|
| Records per table | A Vibe form creating records counts against the same cap. |
| Tables / fields per app | Asking the agent to add tables consumes your table/ |
| API access enabled | Required for the Domain API calls Vibe makes. |
| Custom domains | Pointing your own domain at an interface uses a domain slot. |