# Content Shield (/docs/memory/governance/content-shield)
Memories can hold sensitive details about your users. Your team often needs to manage a memory space without reading what's in it. Content Shield hides memory content in the dashboard.

<Callout type="info" title="Turn on Content Shield when...">
- Memories hold personal, health, or financial details.
- People who manage the space don't need to read individual memories.
</Callout>

## Levels [#levels]

| Level | Hidden in the dashboard | Still visible |
| --- | --- | --- |
| Off | Nothing | Everything |
| Standard | Content and title | Tags, entities, type, and confidence |
| Maximum | Content, title, tags, entities, type, and confidence | The number of memories |

Content Shield changes what dashboard users see. Your app's recalls through `Lynk` still return memory content as normal.

## Turn it on [#turn-it-on]

Turn on Content Shield and choose a level when you create a memory space in **DUM**, or later in the space's **Settings** tab.

| Change | What's needed |
| --- | --- |
| Off to Standard or Maximum | Takes effect at once. |
| Standard to Maximum | Takes effect at once. |
| Maximum to Standard | A one-time code. |

## Reveal content [#reveal-content]

When someone must read a shielded memory, they choose **Reveal** and enter a one-time code. The content is shown for a limited time, then hidden again.

<Callout type="idea">
Combine Content Shield with a PIN on the space, so opening the space and reading its content each need their own check.
</Callout>

## Next steps [#next-steps]

Dashboard access is under control. Learn how to erase everything about one person next.

<Cards>
  <Card title="Deleting a person's data" href="/docs/memory/governance/entity-deletion" description="Erase every memory about one entity." />
  <Card title="Memory spaces" href="/docs/docklee/memory-spaces" description="All space settings in one place." />
  <Card title="Retention" href="/docs/memory/governance/retention" description="How long memories are kept." />
</Cards>
