Start here: how a Tadabase app fits together
What a Tadabase app is made of (tables, pages, users and roles, workflows) and the order to read the Get started pages in.
- Verified Nov 17, 2026
- Classic builder
On this page
A Tadabase app is a database with screens on top of it. You build it in the classic builder, and the people who use it open it in a browser at the app's own web address.
No-code means you build the app by choosing options and arranging components instead of writing code. You can still add your own CSS and JavaScript when you need to.
The parts of an app #
| Part | What it is | Where you build it |
|---|---|---|
| Data tables | Your data. Each table has fields (its columns) and records (its rows). Tables link to each other through connections. | Data Builder |
| Pages | The screens people use: forms, tables of records, record details, menus. A page is built from components that show or collect data. | Page Builder |
| Users and roles | Who can sign in to the app. Each user has a role, and each page can be limited to certain roles. | The Users table in the Data Builder (its Roles tab), and each page's Security tab |
| Workflows | Steps that run on their own: when a record is created or updated, on a schedule, or when someone clicks a button. | Workflows |
| The live app | What your users see. It runs at the app's address, and every page you save is part of it. | Open it with View App in the builder |
Read the Get started pages in this order #
Start from a prompt instead #
Was this page helpful?
Something wrong or missing on this page? Tell us.