Airtable Platform and App Building
What this domain covers
This domain tests your mental model of how an Airtable base is assembled and how its parts interact. Know the hierarchy: workspace → base → table → field → record, and know that a base can hold many tables while a workspace holds many bases with different sharing and permission scopes. Understand table types (a standard table versus an interface, form, or view) and the difference between a view (a saved way of looking at one table: grid, gallery, calendar, kanban, form) and an interface (a separate app-like page that can pull from multiple tables).
Concepts to master
- Field types drive behavior. The field type determines what you can do downstream: lookup, rollup, and formula behavior depend on it.
- Views are not copies. Filtering or sorting a view never deletes or reorders the underlying records.
- Collaboration features: comments, record-level revision history, and the base-level trash are separate mechanisms.
- Permissions are set at workspace and base level (owner, editor, commenter, read-only), and interface users can be granted access without full base access.
Traps in questions
Questions love to imply that editing a view changes data, that deleting a field is instantly permanent (it is recoverable from trash for a limited window), or that a form view can display existing records. Watch for "which is the first step" phrasing and for conflating a base's name with its workspace.
Rule of thumb
If a question asks what changes the data, the answer is almost never a view, sort, filter, or grouping - those change presentation only. Only edits to records or fields change data.