Forget the scattered Notes app lists, half written email pitch lists, or solo Excel spreadsheet. The Table app gives your team a flexible way to manage structured information in rows and columns.
Use it to track requests, inventory, content calendars, campaign details, research, budgets, or any other data that does not fit neatly into a traditional project plan.
What can I use the Table app for?
Think of Tables as the one-stop-shop for all other data that might not be its own task or project. Anything you have in a Google Doc, Google Sheet, Spreadsheet, etc.
Tables are useful when you need to:
Store information in a structured format
Track records across multiple fields
Sort, filter, and review data quickly
Connect structured information to related Hive work
Common examples include:
Marketing campaign calendars
Content and editorial planning
Customer or partner trackers
Event planning
Create a table
Open the Table app from the Hive navigation menu.
Select Create table.
Enter a name for your table.
Add the fields your team needs.
Add records manually or import existing information, if available.
Start with only the fields you need. You can add more fields later as your process develops.
Pro tip: Don't know where to start? Ask Buzz to create the Table for you with your exact specifications.
Add and manage fields
Fields define the type of information stored in each column. Choose a field type that matches the data you want to track.
For example:
Information | Suggested field |
Campaign name | Text |
Launch date | Date |
Owner | Person |
Status | Select |
Budget | Number |
Website or document | Link |
Additional context | Long text |
Use clear field names that make sense to anyone viewing the table. For example, use Launch date instead of Date, and Campaign owner instead of Person.
Add records
Each row represents one record in your table.
To add a record:
Open the table.
Select Add record or the next available row.
Enter the relevant information in each field.
Add any supporting context or links.
Keep each row focused on one item. For example, in a content calendar, each row should represent one content asset rather than an entire campaign.
Edit records
You can update a record whenever its information changes.
Common updates include:
Changing the owner
Updating a status
Adjusting a due date
Adding notes or links
Correcting a value
Recording a decision or outcome
Keep important fields current so filters, reports, and team workflows remain reliable.
Collaborate with your team
Tables work best when the team agrees on how they should be maintained - you don't want a dozen people all making mismatched edits to the Table.
Some best practices include:
Assign an owner to each record when follow-up is required.
Use comments or linked Hive actions for detailed discussions.
Add links to relevant documents, meetings, or projects.
Review and clean up outdated records regularly.
Avoid storing sensitive information unless the table has the appropriate access controls.
Connect table data to project work
One of the best parts about Tables is that they can act as the central source of structured information, while Hive actions track the work required to move each record forward.
For example:
A campaign table stores campaign details.
A project contains the campaign execution plan.
Actions track deliverables, approvals, and deadlines.
The table records the campaign’s owner, audience, budget, and launch status.
Use an action when someone needs to complete work. Use a table record when you need to store and organize information.
Table records versus Hive actions
Use a table record when you need to... | Use a Hive action when you need to... |
Store structured information | Assign work to someone |
Track attributes across fields | Set a deadline |
Compare or filter records | Track progress toward completion |
Maintain a list or database | Add dependencies or subactions |
Capture reference information | Manage a deliverable or responsibility |
Some workflows need both. A table can store the details of a request, while a linked action tracks the follow-up work.
Frequently asked questions
Can I use a table instead of a project?
Tables are best for structured information and records. Projects are best for managing work, deadlines, ownership, dependencies, and progress. Many teams use them together.
Should every table row have an owner?
Not necessarily. Add an owner when a record requires follow-up or accountability.
Can I use tables for reporting?
Yes. Consistent fields make it easier to sort, filter, and review information. For broader reporting, combine table data with Hive dashboards where appropriate.
How should I organize a large dataset?
Start with a clear table purpose, use consistent field types, and separate unrelated processes into different tables. Archive or remove outdated records according to your team’s retention practices.
If there is something you're struggling with, ask Buzz to help!