> For the complete documentation index, see [llms.txt](https://codifi-fdm.gitbook.io/codifi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codifi-fdm.gitbook.io/codifi-docs/mobile-app/getting-in-the-field/composition-summary-view.md).

# The Composition Summary View

The Composition Summary is a quick reference for "what does this Project contain?" It shows the Composition's archetype tree — every Record type, how they relate, and what's allowed where — without having to open the web app.

It's useful when you're new to a Project, when you're prepping for a field day, or when a crew member asks "what archetypes are in this one?"

***

## How to open it

From the Project's map screen:

1. Tap the **Project name** in the header.
2. Tap the **Composition name** that appears below it.
3. The Composition Summary opens.

You'll see the relationship tree — Project Details at the top, then all the archetypes available in this Composition, indented to show parent-child relationships.

***

## What you see

```
Project Details
├── Site
│   ├── Feature
│   │   └── Artifact
│   └── Shovel Test Probe
├── Transect
│   └── Shovel Test Probe          ← multi-parent
└── Photo Log Entry
```

For each archetype, the summary shows:

* **The archetype name** (label).
* **Geometry type** — point, line, polygon, or no location.
* **Where it can sit in the tree** — what parents are allowed, whether it's used in more than one place.

***

## When to open it

**Before a field day** with a Project you haven't worked on recently — a 30-second skim refreshes you on what Records the day will involve.

**When training new crew members** — show them the tree before handing over an iPad. Concrete archetype names land faster than abstract explanations.

**When a Quick Action surprises you** — sometimes seeing the tree makes "why is Codifi suggesting this archetype" obvious.

**Before reporting a "this looks broken" issue to your PM** — confirm the archetype actually exists in the Composition you're on; sometimes the issue is that you're on the wrong Project.

***

## What it doesn't show

The summary is a tree, not a field-level browser. It doesn't show:

* Individual fields on each archetype.
* Ripple formulas.
* Specific field requirements (required-or-not, default values).

For field-level detail, you have to either open a sample Record (tap **+**, pick the archetype, see the form) or ask your PM to walk you through the Composition on the web.

***

## Common questions

### Why is an archetype I expected missing from the tree?

Three possibilities:

* The Composition genuinely doesn't include it.
* The Composition is a different version than you remember — Projects snapshot the Composition at creation time and don't auto-update.
* You're on the wrong Project (different tenant, similar name).

### Can I edit the Composition from this view?

No — the summary is read-only. Composition editing happens on the web via the **Composer** role.

### What if the tree shows archetypes I don't have permission to create?

Composition trees show every archetype in the Composition; RBAC controls which ones you can actually create. If you tap **+** and an archetype is grayed out, you have permission to *see* it but not to *make* one.

***

## Related

* [**Getting in the Field**](/codifi-docs/mobile-app/getting-in-the-field.md) — the broader pre-field checklist this fits into.
* [**Understanding Archetypes and Relationships**](/codifi-docs/mobile-app/creating-records/understanding-archetypes-and-relationships.md) — the concept behind the tree.
* [**The Records List in Practice**](/codifi-docs/mobile-app/records-in-context/records-list-in-practice.md) — how the same tree shows up once you have Records in it.