# Galdera Help

> Product guide for Galdera — concepts, workflows, and how the app works.

## Docs

- [Creating Metrics with the Formula Builder](/targets/creating-metrics.md): A **metric** is a derived value — it isn't imported from a data source like a measure is. Instead, you define it with a formula that combines your existing measures and metrics.
- [What Are Targets?](/targets/what-are-targets.md): **Targets** is the area where you manage the things you forecast and track — your measures and metrics. Its purpose, as the page describes it, is to *manage your metrics and measures*.
- [Connecting a CSV Source](/sources/connect-csv.md): To bring data in from a CSV file:
- [Connecting a Databricks Source](/sources/connect-databricks.md): A Databricks connector imports one shared table using OpenSharing. Your Databricks administrator shares the data, and the Galdera team connects that share to your workspace. Creating a connector in Galdera does not create the share.
- [Connecting to Snowflake](/sources/connect-snowflake.md): Getting data from Snowflake into Galdera has two parts:
- [Snowflake Syncs and Troubleshooting](/sources/manage-snowflake.md): A configured Snowflake source has **Status**, **Data**, and **Settings** tabs. Connection tests and data reads use the same stored key, Snowflake service user, and static Galdera egress IP, so a successful test checks the same route used by a sync.
- [Data Formats](/sources/source-data-formats.md): Galdera works with two data layouts and auto-detects which one you're using:
- [Source Status and Troubleshooting](/sources/source-status.md): After you upload or connect a source, it goes through several stages:
- [What is a Source?](/sources/what-is-source.md): A **source** is where Galdera gets its raw data. Before you can forecast anything, you need to connect a data source so the platform knows what numbers to work with.
- [Associating Overlays with a Scenario](/scenarios/apply-overlays.md): An overlay becomes part of a scenario through its **blocks**: each block in the overlay editor references exactly one scenario. The set of blocks (across any overlays) that reference the same scenario together define that scenario's assumptions.
- [Comparing Scenarios](/scenarios/compare-scenarios.md): All overlays share the same baseline forecast — the ML-generated prediction with no adjustments. Each overlay layers its changes on top of that shared baseline, and every block's results are tagged with its scenario name. Differences between scenario-tagged results are therefore attributable entirely to the overlay assumptions carrying that tag.
- [Creating a Scenario](/scenarios/create-scenario.md): A scenario is a named label for a coherent set of planning assumptions. Before creating one, have a clear idea of what business situation it represents.
- [Building a Report](/reports/building-a-report.md): You build a report by choosing which measures and metrics it contains and what order they appear in. Give the report a title (the field starts as "Untitled Report"), then use the two-column selector.
- [Viewing Report Data](/reports/report-data-and-versions.md): A report doesn't just define which measures and metrics to show — it also remembers how to display them. This data-preview configuration is saved with the report and restored the next time you open it:
- [What Is a Report?](/reports/what-is-report.md): A **report** is a saved, named collection of the measures and metrics you want to look at together, arranged in an order you choose. Each report is its own entity with a title, and you manage your reports as a collection.
- [Reusing an Overlay in Another Version](/overlays/copy-to-version.md): Overlays belong to a specific forecast version, but you don't have to rebuild one to use it elsewhere: **copy it into the target version**.
- [Creating an Overlay](/overlays/create-overlay.md): An overlay lets you adjust forecast values without changing the underlying model. Think of it as a "what-if" layer on top of your baseline forecast.
- [Overlay Operations: Scale, Override, Offset](/overlays/overlay-operations.md): Galdera supports three types of overlay adjustments, each suited to different planning scenarios.
- [Overlay Scoping: Date Ranges and Dimensions](/overlays/overlay-scoping.md): Overlays can be scoped precisely to apply only where they are relevant -- both in time and across your business dimensions.
- [Running an Overlay](/overlays/running-overlays.md): Beta: Agent mode
- [Locking an Overlay](/overlays/saving-overlays.md): Beta: Agent mode
- [Finding Entities in Galdera](/navigation/finding-entities.md): Galdera organizes your financial model into distinct entity types — Metrics, Measures, Overlays, Scenarios, Dimensions, and Forecast Versions. Each entity type has its own section of the application where you can browse and manage items.
- [Navigating the Galdera UI](/navigation/navigating-ui.md): The main sections of the Galdera interface correspond to the core entity types:
- [Using Search](/navigation/using-search.md): Galdera's search finds entities across all types by name. You don't need to know the exact name — partial and fuzzy matches work.
- [Quickstart](/getting-started/quickstart.md): This is the shortest path from an empty workspace to a forecast you can reason about. Each step links to a detailed guide.
- [Sharing and permissions](/getting-started/sharing-and-permissions.md): Use **Share** to control access to the version, overlay, or document you are viewing.
- [How the Baseline Forecast Is Generated](/forecasting/baseline-pipeline.md): The **baseline forecast** is the model's prediction with no user overlays applied. It is generated entirely from historical data using statistical and machine-learning models.
- [Configuring a Forecast Version](/forecasting/configuring-a-forecast-version.md): Beta: Agent mode
- [End-to-End Workflow: From Data to Signed-Off Forecast](/forecasting/end-to-end-workflow.md): Here is the complete linear workflow for producing a forecast in Galdera. Each step builds on the previous one.
- [Exporting a Forecast Version](/forecasting/exporting-forecasts.md): **Export** takes a forecast version's numbers out of Galdera: as CSV files you download, as a publication to the consumer-facing tables that downstream integrations read, or both. It is a separate step from locking: [locking](/forecasting/saving-forecasts) designates the official baseline inside Galdera; exporting is how that locked set leaves.
- [Forecast Versions](/forecasting/forecast-versions.md): A **Forecast Version** is a named, time-bounded forecast run. It defines:
- [Running a Forecast Version](/forecasting/running-forecasts.md): Beta: Agent mode
- [Locking a Forecast Version](/forecasting/saving-forecasts.md): Beta: Agent mode
- [Modelling the Three Statements](/forecasting/three-statement-modelling.md): Income-statement lines are flows the ML models can forecast directly. Balance-sheet and cash-flow lines are different: they are connected **across time** — a balance accumulates its flows, and cash-flow lines are the period-to-period change of balances. Forecasting each line independently would give you statements that don't tie. Galdera instead lets you declare those relationships, and derives the connected lines so that **every stock's change equals its flows, every period**.
- [Metric and Measure Dependencies](/data-model/dependencies.md): The dependency structure of your financial model describes which entities feed into which. Understanding dependencies helps you:
- [How Metrics Are Calculated](/data-model/metric-calculations.md): Metrics in Galdera are defined by formulas that combine Measures and other Metrics. A formula **chains any number of operators from one family**, evaluated left to right:
- [The Forecast Graph](/data-model/the-graph.md): Galdera models your financial data as a connected **graph** — every measure, metric, overlay, and scenario is linked to the others it relates to. This is what makes it possible to instantly answer questions like "what does this overlay affect?" or "what feeds into Gross Margin?"
- [Metrics vs. Measures](/concepts/metric-vs-measure.md): In Galdera, your financial data is organized into two distinct types: **Measures** and **Metrics**.
- [What Is a Dimension?](/concepts/what-is-dimension.md): A **dimension** is a categorical attribute used to break down your Measures and Metrics. Common examples include Region (North, South, East, West), Product Line (Enterprise, SMB, Consumer), Sales Channel (Direct, Reseller, Online), or Department.
- [What Is a Forecast Version?](/concepts/what-is-forecast-version.md): A **Forecast Version** defines the execution context for a forecast run. It specifies the time boundaries — when the model starts training on historical data, when the forecast period begins, and when it ends.
- [What Is an Overlay?](/concepts/what-is-overlay.md): An **overlay** is a user-defined adjustment to your forecast. Think of it as a "what-if" layer that sits on top of the model's baseline predictions without changing the underlying historical data.
- [What Is a Scenario?](/concepts/what-is-scenario.md): A **scenario** is a named planning-assumption label — "Base Case," "Upside," "Downside," "New Product Launch" — that overlay blocks reference. Every block inside an overlay carries a scenario, and when the overlay runs, its results are tagged with that scenario's name. This lets you group and compare overlay outcomes by assumption set.
- [Adding Notes to the Canvas](/canvas/adding-notes.md): Beta: Agent mode
- [Documenting Assumptions](/canvas/documenting-assumptions.md): Well-documented assumptions are the foundation of a credible forecast. Each overlay in Galdera represents one assumption — and its canvas is the right place to capture everything a reviewer needs to evaluate that assumption.
- [The Narrative Canvas](/canvas/narrative-canvas.md): Every **Overlay** and **Forecast Version** in Galdera has a narrative canvas — a structured document where you can record the reasoning, assumptions, and context behind your forecast adjustments.
- [What the Assistant Can Change](/assistant/ask-vs-agent-mode.md): Beta: Agent mode
- [Using the Assistant](/assistant/using-the-assistant.md): Beta: Agent mode
- [What You Can Ask the Assistant](/assistant/what-you-can-ask.md): Beta: Agent mode
- [Actuals vs. Forecast](/analytics/actuals-vs-forecast.md): One of the most valuable views in Galdera is comparing your actual results against what was forecast. This comparison shows:
- [Viewing Trends Over Time](/analytics/trends.md): Trend views show how a Measure or Metric changes over the forecast horizon. This is useful for:
- [Viewing Forecast Numbers](/analytics/viewing-numbers.md): Galdera's analytics section gives you access to the actual forecast values produced by the model. You can view numbers for any Measure or Metric, within any Forecast Version, broken down by Scenario.
- [Connect your identity provider](/access-and-sso/connect-sso.md): Use the secure setup link from Galdera to connect your identity provider. Galdera supports SAML and OpenID Connect (OIDC).
- [Add and manage people](/access-and-sso/manage-people.md): Organization administrators can manage workspace membership from **Settings → People**.
- [Understand roles and access](/access-and-sso/roles-and-permissions.md): Galdera controls access at two levels:
- [Troubleshoot sign-in and access](/access-and-sso/troubleshoot-access.md): Start with the message or behavior you see below. After changing an invitation, application assignment, or role, sign out and sign in again.