> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gocromo.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Welcome to Cromo
> Turn business context into trusted knowledge, structured data, dashboards, and repeatable workflows.
Cromo is a chat-first workspace for turning the way your team works into an operational system. You can begin with a question or outcome in plain language, then preserve what matters as shared knowledge, structured data, a dashboard, a reusable skill, or a workflow.
You do not need to model the whole business before you start. Add the context for one real process, use it with your team, and make the system more formal when the work becomes repeatable.
## The Cromo model
Cromo keeps three kinds of information connected:
| Layer | What it contains | Use it when |
| ------------- | -------------------------------------------------------------------- | ---------------------------------------------------------------------- |
| **Sources** | Original files, synced content, and material taught in chat | You need evidence, provenance, or the full source |
| **Knowledge** | Human-readable pages for concepts, policies, entities, and processes | People need an answer they can browse, review, and improve |
| **Data** | Models, tables, records, and team files | Information changes often or needs filtering, reporting, or automation |
Chat works across these layers. Dashboards make the current state visible. Process Skills preserve reusable instructions. Workflows execute repeatable processes and keep a run history.
Sources, Knowledge, and Data are complementary. A policy PDF can remain as evidence, become a concise Knowledge page, and define fields used in a structured compliance table.
## How work moves through Cromo
Upload documents, connect an application, or teach Cromo directly in chat.
Inspect generated Knowledge pages, check their source references, and approve or improve proposed changes.
Ask sourced questions, draft deliverables, or describe the operational outcome you need.
Add a data model and table, publish a dashboard, create a Process Skill, or compile the process into a workflow.
Review dashboard state, workflow runs, failures, and changes to the underlying knowledge.
## Where work lives
Everyday work lives in a **Project**. A Project keeps its conversations, Sources, Knowledge, Data, Dashboards, Skills, Workflows, integrations, and members together.
Projects belong to a **Workspace**, the organization-level home where roles and access are managed.
Build a useful Project from one real business outcome.
Understand how evidence becomes reviewed, usable context.
Track changing records and turn them into an operational view.
Run repeatable work manually, on a schedule, by webhook, or from an event.
## Explore complete examples
Each example starts with a business outcome and follows it through chat, Knowledge, Data, Skills, Workflows, and Dashboards.
Qualify new leads, route them to the right owner, and prepare follow-up drafts.
Apply escalation policy, create consistent tickets, and monitor deadlines.
Check policy requirements and prepare requests for human approval.
Build role-specific checklists, assign owners, and track blockers.
Find incomplete, overdue, unmatched, and possible duplicate invoices.
Cromo helps your team organize and execute work, but important answers and automated actions still need appropriate human review. Check citations, permissions, inputs, and outputs before relying on them for a business-critical decision.