Obvious/Help Center

Workbooks & Sheets Overview

Published February 27, 2026 · Last updated March 7, 2026 · 6 min read

A workbook in Obvious works like a workbook in Excel — it holds one or more sheets, each with its own columns and rows. The difference is that everything connects directly to the views, automations, and AI agent work that happens in the same project.

What a workbook is

A workbook is a container. It groups related sheets together, the same way a file folder groups related documents. You might have one workbook for a customer database, another for a content calendar, another for a project tracker. Each workbook shows up as its own artifact in your project, and you can organize them into folders as your workspace grows.

Inside a workbook, you work with sheets. A sheet is like a tab in a spreadsheet — a single table where columns are fields and rows are records. That structure might sound familiar, but the way Obvious handles it is different in ways that matter.

How sheets differ from spreadsheets

A spreadsheet is a grid. Any cell can hold anything — a number, a formula, a stray note, a date formatted seventeen different ways. That flexibility is useful until it isn't, which is usually around the time you try to analyze the data or hand it to someone else.

Sheets in Obvious are typed. Every field has a defined type — text, number, date, dropdown, email, phone, rating, and more — and Obvious enforces that type consistently across every record. You don't end up with "January 5" in one row and "1/5/26" in another. You end up with a date field, and every row has a date.

That discipline has a few concrete benefits:

  • Validations work reliably. You can flag records where a required field is empty, a number is out of range, or an email doesn't look like an email — and Obvious applies those rules automatically as data comes in.

  • The agent can act on the data directly. Because Obvious knows the shape of your data, the agent can run SQL queries, generate charts, and build analyses without you having to explain what everything means first.

  • Views stay accurate. When you create a Board view from a sheet with a status field, or a Calendar view from a sheet with a date field, those views stay in sync as records change.

The tradeoff: you set up your schema before you fill it in, or you let the agent infer it from data you import. Either way, the structure exists and holds.

Getting data in

Obvious gives you a few ways to populate a sheet, and you don't have to pick just one.

Import from a file. Drag a CSV or Excel file into the chat and Obvious maps the columns to fields, inferring types where it can and letting you correct anything it gets wrong. Your existing data is in the sheet in minutes, and the original file stays in your project as a reference.

Create one from the toolbar. Click the + button in the toolbar and select Sheet. Obvious creates an empty workbook with a blank sheet — add fields and records directly in the UI. On the landing page, you can also click Table from the pill buttons to get started.

Let the agent build it. Describe what you need in the chat — "a sheet to track customer onboarding, with fields for company name, status, owner, and renewal date" — and the agent creates the workbook, configures the fields, and you can start adding records immediately. The agent can also populate records from research, from connected tools, or by transforming data from another sheet.

Paste or type directly. For smaller datasets or quick additions, you can type records into the sheet the same way you'd type into a table. Add a row, fill in the fields, move on.

How views connect to sheets

A sheet holds the data. Views are like different ways to look at the same data — a Kanban board, a calendar, a timeline — without duplicating anything.

Three views are available to all workspaces:

  • Board — Organizes records as cards in columns based on a status or category field. Good for task management, deal tracking, anything with defined stages.

  • Calendar — Places records on a calendar based on a date field. Good for editorial calendars, project deadlines, event scheduling.

  • Timeline — Shows records as horizontal bars between a start date and end date. Good for project plans, roadmaps, sprint planning.

Two additional views are available in some workspaces:

  • Gallery — Displays records as visual cards with image previews in a grid layout. Good for portfolios, image-heavy datasets, or content where visual scanning matters.

  • Checklist — A simplified list view focused on completion. Good for tasks and action items where you want a clean checkbox experience.

Every view you create stays connected to the underlying sheet. Change a record's status in the Board view and the sheet reflects it. Update a date in the Timeline and the Calendar shows the change. You're always looking at the same data, just through a different window.

When to use workbooks vs. documents

The question that comes up most is: should this be a workbook or a document?

Use a workbook when your content is fundamentally records — when you'd naturally organize it in rows. Customer lists, project trackers, product inventories, experiment logs. If you'd reach for a spreadsheet, reach for a workbook instead.

Use a document when your content is fundamentally prose — when you're writing, explaining, or planning. Reports, meeting notes, proposals, strategy briefs. Rows and columns would be the wrong container.

The two aren't mutually exclusive. A workbook and a document often live in the same project and reference each other — a document might explain the strategy, while a workbook tracks the execution. Embedded charts in a document can pull directly from sheet data, so when the numbers change, the document stays current.

Next steps

Was this helpful?