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.

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.

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.

Fields define the type of information stored in each column. Choose a field type that matches the data you want to track.

For example:

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.

Use a Relation field to link a record in one table to records in another table — for example, linking campaign rows to a separate clients table.

Leave Display fields empty to show the target table’s primary field. Display fields can be Text, Number, Select, or Date fields on the linked table. Person (User) fields are not available as display fields.

You can change display fields later from the relation field settings. Target table and cardinality stay fixed after the relation column is created.

Each row represents one record in your table.

To add a record:

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.

Paste a list to add multiple records

If your table’s primary field is Text, you can add several names or titles at once. Copy a list with one item per line, then paste it into the primary field. Hive asks whether to keep the full text in One record or create a separate record for each line. Choose Create [number] records to add one record per non-empty line.

You can paste into the blank Add record row or while editing an existing record’s primary field. Choosing multiple records leaves the existing record unchanged. To bring in a spreadsheet with several columns, use Import Google Sheet or Upload Spreadsheet instead.

You can update a record whenever its information changes.

Common updates include:

Keep important fields current so filters, reports, and team workflows remain reliable.

In a Files field, the cell shows a thumbnail when the first file is an image or video. Hover a video to play it without sound, or click the thumbnail for a larger preview. When there are more files, a count such as +2 appears next to the paperclip. Click it to see and manage all files.

Use Clear all records to empty a table and start fresh without rebuilding its columns or views. Only the table creator or a workspace admin can do this.

Before you confirm: This clears the whole table, including rows hidden from your view. There’s no Undo option in the confirmation window. If your records are linked to other tables, clearing them may also affect those linked records or stop some rows from being removed.

Afterward, Hive shows how many records were cleared and whether any could not be removed. This option isn’t available for campaign tables.

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:

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:

Use an action when someone needs to complete work. Use a table record when you need to store and organize information.

If you've got content in a spreadsheet, you can easily upload that into a Table directly from the app.

Click "Import Google Sheet" or "Upload Spreadsheet" to get your data into Hive with a few clicks.

Some workflows need both. A table can store the details of a request, while a linked action tracks the follow-up work.

Tables are best for structured information and records. Projects are best for managing work, deadlines, ownership, dependencies, and progress. Many teams use them together.

Not necessarily. Add an owner when a record requires follow-up or accountability.

Yes. Consistent fields make it easier to sort, filter, and review information. For broader reporting, combine table data with Hive dashboards where appropriate.

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!