---
title: "DAM Governance & Folder Guidelines"
path: https://www.eonshowroom.eon.com/en/aem-basics/dam-governance-and-folder-guidelines.html
lastModified: 2026-02-12T11:14:08.753Z
---

# DAM Governance & Folder Guidelines

### DAM Governance & Folder Guidelines

Dynamic media images are images that can be manipulated and transformed on-the-fly to suit different needs. This guide will help you understand how to create, upload, and manage these images effectively.
 Images will still live in the local dam, but can be published to a dynamic media server for delivery.

## Structure & Hierarchy - per Program

in implementation - notification will be shared once it's ready for use! - **Central Storage**: A top-level "shared" or "global" folder (e.g., /content/dam/eon/shared) is used to store common assets like logos, icons, fonts, and brand illustrations.
- **Avoid Duplication**: If an asset is required by more than one tenant, it must be stored in this global folder and referenced from there instead of being copied locally.
- **Setup Notice**: This area is currently in the **setup phase**. We will provide a separate update as soon as the official E.ON assets from **Frontify** are available for use there.
- **Access Control**: A dedicated role/permission is set up for the /content/dam/eon folder, limiting write access (Add/Update/Delete) to a specific group of editors.

## Structure & Hierarchy - per Tenant

- **Root Directory**: Each website tenant must use /content/dam/<tenant> as the root of its own DAM structure.
- **Local Organization**: Tenant-specific assets must be organized into the following sub-folders to allow specific areas (like "archive" or "newsletters") to be excluded during content copy filters on Dev/Stage: 
  - images (categorized into global, sites, products)
  - videos (categorized into brand, products)
  - documents
  - newsletters (assets for non AEM hosted newsletters)
  - archive
  - apps (assets for non AEM hosted mobileApps)
  - mail-templates / email-templates/ (New: Provided via the Foundation)
- **Tenant Separation**: Editors are not permitted to use site-specific images stored under another tenant's folder (e.g., eon-com cannot use assets from eon-drive).

## Naming Conventions

To prevent broken URLs in Dynamic Media and ensure system compatibility, all DAM folders must follow these naming rules:

- **Lowercase only:** Do not use capital letters.
- **Hyphen-separated:** Use hyphens (-) to separate words; do not use underscores or spaces.
- **No Special Characters:** Avoid characters such as &, %, @, #, or _.

## Folder & Asset Maintenance

- **Nesting Limit:** Folder nesting under /content/dam/<tenant> must not exceed **5 levels** to ensure optimal performance and readable paths.
- **Search Before Upload:** Editors must search the DAM before uploading new assets to avoid creating duplicate images.
- **Newsletter Assets:** Store newsletter images in a dedicated folder so they can be excluded from content copy filters on Dev/Stage environments.
- **Archive, Don't Delete:** Never delete assets without verifying references. Move unused or outdated assets to an **archive folder** instead to prevent broken links across sites and tenants.
- **Campaign Management:** Group assets for time-bound campaigns logically (e.g., by campaign name or year) and move them to the archive once the campaign is complete.