Manage Data with Tables
Tables give your workspace a structured place to hold business records.
Create a table for a real business purpose
Before creating a table, be able to answer:
- Who owns this data?
- Who updates it?
- Which workflows depend on it?
- What decisions become easier when this data is structured?
What to watch in the table list
The current table list shows useful signals, including:
- table name
- status
- row count
- column count
- usage against plan limits
- last updated time
These are not cosmetic details. They tell you whether a table is healthy and sustainable.
Keep tables understandable
Good tables:
- have clear names
- have stable column meaning
- avoid duplicate records
- stay focused on one business entity or domain
Poor tables become dumping grounds.
When to revise a table
Revisit the structure when:
- users cannot tell where information belongs
- too many columns are unused
- teams create duplicate records because the table is hard to search
- process builders keep bypassing it in favor of freeform entry