> For the complete documentation index, see [llms.txt](https://intuitem.gitbook.io/ciso-assistant/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://intuitem.gitbook.io/ciso-assistant/features/recording-values.md).

# Record a value

Record a metric's value from its page: the period it answers for, what replaces what, and how values are shown

A metric's page carries a **Record a value** strip. Type the value, press **Enter** or click **Save**, and the metric's current value and timeline update in place. No window opens.

<figure><img src="https://629777851-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCqFeU3oPCgDWkkR386NK%2Fuploads%2Fgit-blob-ee5c087a74873bfc046321de5a114643516e6cf5%2Fmetrics-record-value.png?alt=media" alt="The page of the metric Number of assets in ACME Spain: its details on the left, and on the right the Record a value strip with 1310 typed, For period November 2026, an Observation field, Save, and the line November 2026 holds 1300, recorded 03/11/2026, saving replaces it, above the Current Value 1300 and the Timeline chart"><figcaption><p>The strip sits at the top of the metric's page, above its current value and timeline</p></figcaption></figure>

## The period

A metric with a collection frequency records values **for a period**: the calendar month for a monthly metric, the quarter, the ISO week, the day. The strip proposes the current period; pick any day inside another period to record for that one, for example last month's value entered on the 3rd.

The line under the fields says what the chosen period holds, with the value and the day it was recorded, or that it holds nothing yet. A second value for the same period **replaces** the first. Correcting a value is therefore the same gesture as entering it: pick the period, type the right value and save. Replacing takes the right to change samples; adding only the right to add them.

A metric without a collection frequency records a value for its moment only, as before, one per second.

Values recorded before periods existed keep their timestamp and are read by the period that timestamp falls in.

## Observation and evidence

**Observation** is a free note kept with the value. Evidence is attached from the metric's samples list, as before, through the metric's evidence.

## How values are shown

Everywhere a value is displayed, it is rounded to the definition's **Decimals**: the metric page, the lists, dashboard widgets and chart tooltips. The stored value keeps its precision, and formulas read it unrounded. Leave **Decimals** empty for the unit's default: one decimal for a percentage, none for a count, as entered for other units.

A computed metric has no strip: its values come from its formula. See [Computed metrics](https://intuitem.gitbook.io/ciso-assistant/features/metrics.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://intuitem.gitbook.io/ciso-assistant/features/recording-values.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
