Sheets
Individual data tables within Workbooks that organize and structure imported data
What are Sheets?
Sheets are individual data tables within Workbooks that organize and structure imported data. Each Sheet represents a distinct data type or entity, similar to tables in a database or tabs in a spreadsheet.
Sheets serve as containers for Records and are defined by Blueprints that specify their structure, validation rules, and data types. They provide the fundamental building blocks for organizing data within the Flatfile platform.
Basic Blueprint Structure
- A Space has one Blueprint
- A Blueprint may contain the configuration for many Workbooks and many Documents
- A Workbook may contain many Sheets and many Workbook-level Actions
- A Sheet may contain many Fields and many Sheet-level Actions
Basic Sheet Definition
The following examples demonstrate the configuration of isolated Sheets, which are intended to be used in the context of a Workbook configuration.
Single-Sheet Sheet Configuration
This example configures a single Sheet containing three Fields and one Action and defining
Sheet level access
With access
you can control Sheet-level access for users.
Access Level | Description |
---|---|
"*" (default) | A user can use all access actions to this Sheet |
"add" | A user can add a record(s) to the Sheet |
"delete" | A user can delete record(s) from the Sheet |
"edit" | A user can edit records (field values) in the Sheet |
"import" | A user can import CSVs to this Sheet |
<empty> | If no parameters are specified in the access array, sheet-level readOnly access will be applied |
If you use "*"
access control, users will gain new functionalities as we expand
access controls. Use an exhaustive list today to block future functionality from
being added automatically.
Sheet Options
Configurable properties for a Sheet that control its behavior and appearance:
Option | Type | Required | Description |
---|---|---|---|
name | string | ✓ | The name of your Sheet as it will appear to your end users |
description | string | A sentence or two describing the purpose of your Sheet | |
slug | string | A unique identifier for your Sheet. Used to reference your Sheet in code, for example in a Record Hook | |
readonly | boolean | A boolean specifying whether or not this sheet is read only. Read only sheets are not editable by end users | |
allowAdditionalFields | boolean | When set to true , your Sheet will accept additional fields beyond what you specify in its configuration. These additional fields can be added via API, or by end users during the file import process | |
access | array | An array specifying the access controls for this Sheet. Read more about access controls | |
fields | array | ✓ | This is where you define your Sheet’s data schema. The collection of fields in your Sheet determines the shape of data you wish to accept |
actions | array | An array of actions that end users can perform on this Sheet. Read more about actions | |
metadata | object | Use metadata to store any extra contextual information about your Sheet. Must be valid JSON | |
mappingConfidenceThreshold | number | Configure the minimum required confidence for mapping jobs targeting that sheet (default: 0.5). Must be greater than 0 and less than or equal to 1 |
Related Concepts
- Workbooks - Containers that hold multiple sheets
- Blueprints - Define the structure and validation rules for sheets
- Records - Individual rows of data within sheets
- Fields - Individual columns that define data structure
- Actions - Custom operations that can be performed on sheet data