Data and dashboards

Knowledge explains how the business works. Data records the things that change while the work is happening. In Cromo, the Data area contains models, tables, records, and team files. Dashboards turn those records and other Project context into a view people can use for monitoring and decisions.

Data models

A model is a JSON Schema contract that defines the shape of a record. It gives fields stable names and types so chat, tables, dashboards, and workflows can refer to the same structure. A simple renewal model might contain:

{
  "type": "object",
  "properties": {
    "customer_name": { "type": "string" },
    "account_owner": { "type": "string" },
    "renewal_date": { "type": "string", "format": "date" },
    "contract_value": { "type": "number" },
    "risk_level": {
      "type": "string",
      "enum": ["low", "medium", "high"]
    },
    "next_action": { "type": "string" }
  },
  "required": ["customer_name", "renewal_date"]
}

Use field names that describe business meaning. Avoid encoding presentation details such as “red_column” or “card_text” in the model.

Data tables and records

Every table is backed by a model. A table contains the records that follow that model. You can:

create a table from a model;
add records in batches;
edit or delete individual records;
rename or delete a table;
reference the table in chat, Dashboards, and Workflows.

Use a table when records need regular updates, ownership, filtering, or reporting. Keep explanatory policy in Knowledge and link it through the process rather than copying policy prose into every row.

Team files

The Data area also includes files created or uploaded during Project work. These can include chat attachments and generated deliverables. You can preview, download, reuse, or delete a team file. If a file should become long-lived evidence for the Knowledge pipeline, save it to Sources.

Dashboards

A Dashboard is a published operational view. It can combine structured tables, metrics, charts, filters, record details, explanatory Markdown, and actions. Dashboard data can come from Project tables and other supported Project capabilities, including semantic queries, workflow results, connectors, and documents. Use chat to describe the question the Dashboard should answer:

Create a renewal dashboard with the number and value of contracts due in the next 90 days, a breakdown by risk level, a table grouped by account owner, and a filter for renewal month.

Cromo creates and validates a draft before publishing the active version. Published Dashboards appear in the Project’s Dashboard list and can be renamed later without changing their URL slug.

Prompts to try

Create structure from a real need

Create a model and table for customer complaints. Track customer, received date,
category, priority, status, owner, response deadline, and escalation reason.
Make customer, received date, and status required. Show me the proposed schema
before creating the table.

Turn records into an operational view

Create a Dashboard from the Tickets table. Show open tickets by priority,
critical tickets without an owner, tickets approaching their response deadline,
and a review table grouped by owner. Add filters for status and priority.

Review the proposed schema and metric definitions before creating or publishing the asset.

Choose the right representation

Need	Best home
Policy, definition, or process explanation	Knowledge
Original document or evidence	Sources
Frequently changing records	Data table
Reusable generated or uploaded artifact	Team files
Current metrics and operational review	Dashboard
Repeatable transformation or action	Workflow

Example: renewal operations

Keep the renewal policy in Knowledge, with citations to the original contract guidance.
Define a renewal model with date, owner, value, risk, and next action.
Store each customer renewal as a table record.
Publish a Dashboard for upcoming expirations and missing actions.
Run a weekly Workflow that prepares owner follow-ups and writes back the result.

Build a data-backed dashboard

Create a model, add records, ask useful questions, and publish an operational view.

Getting Started

Concepts

Guides

Examples

Reference

Data and dashboards

Data models

Data tables and records

Team files

Dashboards

Prompts to try

Create structure from a real need

Turn records into an operational view

Choose the right representation

Example: renewal operations

Build a data-backed dashboard

​Data models

​Data tables and records

​Team files

​Dashboards

​Prompts to try

​Create structure from a real need

​Turn records into an operational view

​Choose the right representation

​Example: renewal operations

Build a data-backed dashboard

Data models

Data tables and records

Team files

Dashboards

Prompts to try

Create structure from a real need

Turn records into an operational view

Choose the right representation

Example: renewal operations