📌 Summary

<aside> 💡 Databases unify multiple Data Sources into a single, standardized view (e.g. combine Finance and Sales data). They’re the curated layer Models reference for calculations.

</aside>

🎯 Purpose

• Joining multiple sources (ERP actuals + CRM pipeline, etc.)
• Standardizing names/structures (schema) across entities
• Applying mappings so rollups and drill-downs behave consistently

🔑 Key Concepts

• Sources vs. Database: a source is raw input; a database is your curated, joined view.
• Schema (Database level): define column types (measure, dimension, date, relationships) to normalize disparate inputs.
• Cross-entity setups: each company/workspace can have its own mapping; Databases align them for portfolio views.

➡️ Typical tasks

• Add multiple sources into one Database
• Define/adjust the Database schema (measures, dimensions, dates, relationships)
• Use mappings to align account structures
• Export filtered tables for audits or spot checks

⚡️ Quick start

1. Open Databases → create or select a database.
2. Add Source rows to include your chosen Data Sources.
3. In Settings, define schema columns and relationships (joins/mappings).
4. Validate in Overview with filters; save and reprocess if needed.