Create and Configure a Spreadsheet
Build an organization table with a clear purpose, suitable columns, and controlled structure.
Before you begin
Define the spreadsheet’s purpose, owners, intended users, and whether any information may later be shared. List the required columns and identify which values are plain text, numbers, dates, selections, formulas, or links to CapitalOS records. Search existing spreadsheets before creating a duplicate.
How it works
CapitalOS Spreadsheets provides organization-scoped custom tables. A spreadsheet has a name, optional description, configurable columns, rows, saved views, templates, and supported links to CapitalOS data. The builder changes structure, while the detail grid supports everyday data work.
Step-by-step
- Open Spreadsheets in the correct organization.
- Search the list and confirm that an equivalent table does not already exist.
- Create a spreadsheet with a specific name and purpose.
- Open the builder and add the smallest useful set of columns.
- Choose the correct type for each column and give it a clear label.
- Configure selection options, number behavior, dates, or linked-record settings as needed.
- Reorder columns into the sequence users will follow.
- Return to the grid and enter a small set of representative rows.
- Verify editing, display, and validation for each column type.
- Expand the table only after the sample structure works.
Check your result
The spreadsheet appears in the organization list, its purpose is clear, and every column accepts and displays the intended data type. Sample rows can be edited without workarounds, and users do not need duplicate columns for the same concept.
Common problems
The wrong column type was chosen: correct the structure before loading substantial data and review existing values carefully.
A column cannot be edited: it may be calculated, linked, protected by configuration, or unavailable to your role.
The spreadsheet is hard to scan: reduce unnecessary columns and move essential fields earlier.
A similar spreadsheet exists: agree on ownership and purpose instead of creating competing sources.
Permissions and data notes
Creating and configuring structure can require broader access than editing rows. Column changes can affect formulas, views, imports, and sharing. Avoid storing credentials or unnecessary customer data, and treat any future external sharing as a design constraint from the beginning.