> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usecustory.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Item details and fields

> Manage item fields, descriptions, links, files, comments, relationships, status, history, and permissions in one practical reference.

Use this page as a reference for fields and controls inside an item record.

For item-type definitions and examples, read [Items](/items).

## What lives inside item details

Item details can hold:

* description
* shared and type-specific fields
* files and attachments
* image gallery
* external links with context
* comments
* linked items
* linked external tasks
* status
* item history
* pending AI-related activity

Items open as full-page records in [Building blocks](/building-blocks) and can also be focused inside a journey with a stable slug-based link. Use **Fullscreen** when the team needs a dedicated review surface instead of a side panel.

## Shared fields

Every item can use basics such as:

* title
* description
* status
* owner where supported

## Type-specific fields

| Item type   | Useful fields                                                  | Use them for                                                |
| ----------- | -------------------------------------------------------------- | ----------------------------------------------------------- |
| Touchpoint  | channel, actor                                                 | where the experience happens and who experiences it         |
| Insight     | type, confidence, severity, affected segment                   | what the team learned, how strong it is, and who it affects |
| Opportunity | owner, impact, effort, priority, confidence                    | comparing problems and deciding what deserves attention     |
| Solution    | owner, solution type, impact, effort, priority, target date    | comparing responses and managing follow-through             |
| Metric      | owner, metric type, unit, baseline, current, target, direction | keeping progress measurable                                 |

Metrics can also use a connected **Data source** in the item **Details** tab. PostHog can track event counts, unique users, and event ratios. Stripe can track subscription, churn, payment failure, and refund metrics. See [Metrics](/metrics) for provider-specific setup, calculation options, card views, sync behavior, and limitations.

## Status

Status values are type-specific, so the useful meaning depends on the item type. For example, an insight can be an `Assumption` or `Validated`, while a metric can be `Active` or `Broken`.

## Files and attachments

Text-based files and PDFs can be previewed from the detail view. Other attachments still stay connected to the item, which is often enough to keep the trail clear.

## Image gallery

Image attachments appear in the item image gallery and can be opened from the detail view.

## External links

External links should use `https://` or `http://` URLs. Unsafe link schemes are blocked.

Each link can include a title and description.

## Comments

Comments support `@` mentions. Use them when a teammate, or Custory AI, should respond in the context of the exact item. When Custory AI is mentioned, the item can show pending activity and keep the response in the same thread.

## Relationships

Allowed relationships are:

* Touchpoint -> Insight
* Insight -> Opportunity
* Opportunity -> Solution
* Opportunity -> Metric
* Solution -> Metric

```mermaid theme={null}
flowchart LR
    T["Touchpoint<br/>Where the moment happens"] --> I["Insight<br/>What the team learned"]
    I --> O["Opportunity<br/>What is worth solving"]
    O --> S["Solution<br/>What you might change"]
    O --> M["Metric<br/>How you measure the problem or outcome"]
    S --> M
```

## Linked external tasks

Items can link to delivery work in tools such as GitHub, Jira, Linear, or Notion.

Read [External tasks](/external-tasks) for the task-linking model.

## History

Item history can show changes such as:

* item creation, edits, moves, and reordering
* field changes such as title, description, status, impact, effort, priority, assignment, and visible fields
* comment changes
* attachment changes
* external link changes
* item link changes
* linked task creation, deletion, status changes, and title changes

## Permissions and limitations

Your workspace role controls whether you can edit item details, fields, comments, links, and attachments.

Keep these practical limits in mind:

* Viewers can review context but may not be able to change item details.
* External links must use safe web URL schemes such as `https://` or `http://`.
* Connected metric data sources are configured from metric details, not from every item type.
* Repository items reused across journeys should be edited carefully because the same source record may appear in multiple maps.

## Related pages

* [Items](/items)
* [Metrics](/metrics)
* [External tasks](/external-tasks)