Knowledge Base Tables

When you need a table

The table is suitable for structured data:

• price lists;
• inventory balances;
• catalogues;
• schedules;
• lists of branches;
• rules with columns and values.

If data is better read in rows and columns, use a table rather than a long text file.

In a table, each row can describe a product, service, or schedule entry, while columns hold its properties. See the table editor for working with cells.

Tables are stored in the project's knowledge base. To open it, click the Settings gear button next to the project name, then choose Knowledge base on the project settings page.

If the table fails to open because the service is temporarily unavailable, use the retry button in the error message. It loads the same table again.

• Creating a table: create an empty table or import data from CSV or XLSX.
• Table editor: edit cells and sheets, freeze headers, and ask AI questions with the selected data as context.
• Version history: view earlier table states and restore the version you need.
• Range protection: restrict editing or viewing selected cells.
• Filling tables through the API: fill a table from an external integration and update its structure.

Agent connection

For the table to be used in agent answers, connect it to the agent in the Knowledge Base block. The minimum read permission is Read tables.

To change tables you need separate agent permissions:

• Edit tables;
• Add table rows;
• Import CSV and XLSX;
• Delete rows;
• Create sheets;
• Delete sheets;
• Create tables;
• Delete tables.

Don't give the agent the right to modify tables if all they need to do is respond to the data.

What table permissions allow changing

Read tables allows reading the table structure, selected ranges, and rows by headers.

Edit tables is needed to write values and formulas into cells, fill a rectangular block from the selected cell, insert and delete columns, move rows, columns, and ranges, resize, hide rows and columns, clear, copy, merge, unmerge, format, and set borders.

Add table rows is needed to append rows to the end and insert empty rows into a specified place. Delete rows is needed to delete rows. Creating and deleting sheets, tables, and CSV/XLSX import are enabled by separate permissions.

If the change did not work

Check:

• the table is selected in the agent's knowledge base sources;
• the agent has Read tables and the required change permission;
• the user is in the current table version, not in history preview;
• the correct cell or range is selected;
• the request clearly says whether to change the selection, start from the selected cell, or add rows to the end;
• if the change is risky, the user confirmed that they understand the consequences.

If AI changed the wrong area, undo the action through history or a manual edit, select the correct range, and repeat the request more specifically: "change only the selected range" or "start from cell B4".

If the editor loses its connection to the current version, use refresh data first. Use discard local changes only when the unsaved draft is no longer needed.