Tables Explorer

Think of a table as a spreadsheet. Each table holds one kind of thing — customers, products, tasks — a field is a column (one piece of information), and a record is a row (one item).

• Add a table for each kind of thing you want to keep track of.
• Add a field for each detail, and choose its type so Turbofy knows what kind of value it holds.
• Every table automatically tracks an ID and when each record was created and last changed.

When you add a field, you pick its type from a menu. The type decides what a field can hold and how it's shown and validated. Types are grouped into four families.

Standard types

• Text — a short, single line of text, such as a name, title or label.
• ID — a reference that links a record to another record.
• Count — a whole number with no decimals, for quantities and counts.
• Number — a number that can include decimals, for prices, percentages and measurements.
• Boolean — a simple yes / no (on / off) value.

Complex types

• Email — an email address, checked for the right format.
• URL — a web link.
• JSON — structured data for advanced cases, stored as key-and-value pairs.
• Date — a calendar date, with no time of day.
• Date Time — a date together with a time of day.
• Time — a time of day on its own.
• Timestamp — an exact moment in time, handy for recording when something happened.
• Code — a snippet of code or pre-formatted text.
• Localized Text — text that holds a separate value for each language your app supports.

List types

List types hold several values of the same kind in one field — for example a set of tags.

• Text list — several text values, like tags or keywords.
• Number list — several numbers (with decimals).
• Count list — several whole numbers.
• ID list — several references to other records.
• Boolean list — several yes / no values.

Enum types

An enum is a fixed set of choices you define yourself — for example a Status of Draft or Published. Fields that use an enum show as a dropdown, so every record picks from the same options. Create your own under the Enum types section.

Switch a table between Table, Widget and Document views. Filter and search your records, import or export data, and create, duplicate or delete rows right in place.

Every table carries its own access settings. They decide who may read its records, who may write them, and what the developer API exposes — and they hold everywhere: in your apps, through the API, and in anything an assistant builds on top.

Read permissions

Read access widens outwards from the record itself:

• Owner — always on. Whoever a record belongs to can read it.
• Group — opens the record to the group it belongs to, so teammates see the same records.
• Public — opens the table to everyone, including visitors who never sign in.

Write permissions

Writes are three separate switches, so you can hand out exactly one of them:

• Public create — anyone may add a record.
• Public update — anyone may change a record that already exists.
• Public delete — anyone may remove a record.

Publishing settings

Separately, Publishing settings decide what a table contributes to the developer API: All of its operations, only its Queries, or only its Mutations. A table can be published for reading while its mutations stay unpublished.

Typical combinations

• A contact or signup form on a public page — Public create only. Visitors can submit, and nobody can read back what anyone else submitted.
• A public blog, product list or gallery — Public read only. Everyone can see the records; only your team can change them.
• An internal tool your team uses from the dashboard — nothing public at all; Owner and Group already cover it.
• A page that shows each visitor their own records — owner reads, no public read. Pair it with the matching page access level in Apps & pages.