When your website utilizes Collections, Blog, Store Products, Contacts, and Digital Products & Online Courses, all structured data is aggregated in the dashboard under "Data & Records › Data Workbench" (https://app.kanorio.com/data).
Whether your site is managed manually in the dashboard, automatically built by an AI assistant via MCP, or powered by an external headless frontend calling our API, you can view the data, field structures, and API endpoints for every table in this unified workbench.
Upon entering the "Data & Records › Data Workbench", the sidebar categorizes all site data into three blocks:
| Group | Included Tables | Editable in Dashboard | Description |
|---|---|---|---|
| Collections | Custom collections created by you and AI (e.g., teachers, stores) | Editable (Double-click cells, add, delete, CSV import) | Custom structured database for your website, counts toward your plan's collection entry limit (see ) |
| Blog | blog、blog_categories、blog_tags、blog_authors | Read-only (Synced from "Content › Blog") | Automatically projects blog posts and categories into a standard collection structure, accessible via the same API for external frontends without consuming custom collection limits |
| System Tables (Customers / Products & Promotions / Orders & Forms / Deliverables) | Grouped by business domain: contacts、segments、entitlements、products、product_variants、product_categories、、、、、、 |
Automatic Permission Filtering: System tables are automatically displayed based on your role permissions. For example, members with "View Store" permissions can see
productsanddeliverables, while tables containing sensitive customer data likecontacts,entitlements, andprogressare only visible to members with "View Contacts" permissions.
After selecting a table from the sidebar, the top toolbar allows you to switch between three tabs: "Data," "Structure," and "API."
contactId and deliverableId in entitlements, or productId in product_variants), the table and record panel automatically resolve and display the referenced names, eliminating the need to manually cross-reference IDs.id), data type, and constraints for every field in the table.fetch examples, and Management API tool names available for AI assistants and backends, with direct links to the Developer Reference.Tables under the "Blog" and business domain groups are marked with a "Read-only" lock icon. This is because actions like order refunds, product spec synchronization, customer access provisioning, and blog post publishing involve complex logic—including financial transactions, inventory, notifications, and permission checks—that cannot be handled by simply modifying a single cell.
When you need to perform an action on a record in a system table, you have two options:
orders to order details, from contacts to contact profile, or from deliverables to the delivery management page to manually grant access).products.*, deliverables.*, entitlements.*, posts.*) to perform batch creation or updates.Not at all. Only "Custom Collections" created by you or the AI in the first group count toward your plan's record quota (Free: 50, Pro: 1,000, Business: 10,000). Blog and all system tables are excluded from this limit.
No. To avoid conflicts with system table routes (/data/:key), system table names like contacts, products, orders, and deliverables are reserved. If you attempt to use a reserved word when creating a custom collection, the system will return a KEY_TAKEN error, prompting you to choose a different name.
promotionsordersform_submissionsdeliverablesdeliverable_unitsprogress| Read-only (Displayed based on member domain access permissions) |
| Directly displays the underlying records of core website systems, does not consume custom collection limits |