> ## 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. # Building blocks > Maintain reusable journey items in one workspace library, then place them on multiple journeys without duplicating the source record. Use this page when the same item should appear in more than one journey, or when your team needs a workspace-level library of reusable journey context. For item-type definitions, read [Items](/items). ## What this is Building blocks is the workspace repository for reusable journey content. Instead of living only inside one journey, an item can live in the repository and be attached to multiple journeys and steps. A journey placement is only a reference to that shared item. Removing it from one journey does not delete the source record. ## When to use it Use building blocks when: * the same touchpoint appears in more than one journey * one metric should be reviewed across several flows * the same insight keeps showing up in onboarding, activation, and retention * you want one canonical item link the whole team can reuse If an item only matters in one journey and is unlikely to be reused, keep it local to that journey for now. ## What lives here In the sidebar, open **Building blocks**. This workspace-level area includes: * **Personas** * **Journeys** * **Insights** * **Opportunities** * **Solutions** * **Metrics** * **Touchpoints** Personas and journeys appear here too, so the workspace-level model stays in one place instead of being split across separate admin screens. `Add screenshot of the Building blocks sidebar and tab header here` ## Source record vs journey placement The source record is the reusable item in building blocks. A journey placement is where that source item appears on a specific journey step. This distinction matters because the same source record can appear in multiple maps. If you edit the source item, the team sees the updated record wherever it is attached. If you remove one placement, the source item still exists for other journeys. ## Create the shared record once Create a building block directly in the repository, or create it from a journey and keep it reusable from the start. Open any block as a full-page record with a readable URL such as `/{workspaceSlug}/metrics/churn-rate`. From there you can edit fields, details, links, attachments, and related items in one place. `Add screenshot of a full-page metric or touchpoint record here` ## Attach it where it belongs Inside a journey grid view, hover a step cell to reveal: * **Link item** to search existing building blocks * **+** to create a new item on that step The link picker shows useful context such as title, description, status, and whether the item is already attached elsewhere. ## Detach without deleting Use **Delete from journey** when the item should leave this map but still stay in the repository. Use **Delete from repository** only when the item should be removed from the workspace entirely. That distinction matters. One action removes a placement. The other removes the source item. ## Which views help most Different tabs are useful in different views: | Tab | Typical views | Best for | | ---------------------------------------------- | --------------- | --------------------------------------------- | | **Personas** | Grid or table | Reviewing customer roles across the workspace | | **Journeys** | Table | Opening any journey from one list | | **Insights**, **Opportunities**, **Solutions** | Table or matrix | Comparing records at scale | | **Metrics**, **Touchpoints** | Table or grid | Scanning cards and previews quickly | Metrics and touchpoints are especially useful in grid view because their cards surface previews and current state well. ## Example A B2B SaaS team maps both `New user onboarding` and `Trial to paid`. The same touchpoint shows up in both: `Workspace invite email`. Instead of making two separate records, the team: 1. Creates `Workspace invite email` once in **Building blocks**. 2. Attaches it to the invite step in onboarding. 3. Attaches the same touchpoint to the relevant step in trial to paid. 4. Links related insights from each journey back to that one shared touchpoint. When new evidence comes in, they update one record and both journeys stay aligned. ## Delete options that matter When you are cleaning up older work, keep these paths straight: * **Delete from journey** removes the placement and keeps the reusable block. * **Delete from repository** removes the shared record from the workspace. * **Delete journey** removes the map but can keep reusable blocks. * **Delete journey and items** removes the map and deletes the items too. Use the lighter option unless you are sure the source item is no longer useful anywhere. ## Common mistakes If the record already exists in building blocks, use **Link item**. The extra copy is usually what creates maintenance pain later. Check whether you want to remove the placement or remove the source item. They are different actions. Keep journey-specific experiments local until you know they will be reused. Building blocks is not only an item library. It is also a workspace-level navigation surface for the wider model. ## What good looks like A healthy building-blocks setup lets the team: * find the canonical version of an item quickly * reuse it across journeys without copy-paste upkeep * share one stable item link * clean up journeys without losing reusable evidence ## Next step Read [Items](/items) for the item model, or [Item details and fields](/item-fields) for what can live inside a full-page record.