Hi @Aniket_H,
As per my understanding, in AEM SDK v2024.3 and earlier, overlaying /libs/dam/gui/content/assets/adhocassetsharedialog
to /apps/...
worked fine for customizing the "Share Link" popup. But in AEM SDK v2025.4+, Adobe has started locking down or refactoring some dialogs and components — making overlays ineffective unless done very specifically.
In newer versions:
-
The Adhoc Asset Share dialog is dynamically built using client-side JS rendering, particularly via Coral UI components and internal Granite JS APIs.
-
The /libs/dam/gui/content/assets/adhocassetsharedialog
path may still exist, but it’s not directly editable or respected anymore, because Adobe has started moving toward client-side rendering from JavaScript modules.
So even if you overlay the dialog in /apps
, it won’t affect the UI, because the dialog is being generated in JS from internal code (often from /libs/dam/gui/coral/components/commons/sharelink
, etc.).
You may consider workaround for AEM SDK 2025.x+
To make custom fields appear in the Share Link dialog, you have two main paths:
Option 1: Extend using JS customization
This is the safest and most future-proof way.
-
Overlay the JS clientlib used for the share dialog, usually at: /libs/dam/gui/coral/components/commons/sharelink/clientlibs
-
Create your own custom clientlib in /apps/dam/gui/.../clientlibs
and include your JS code that hooks into the share dialog’s Coral components after render.
-
Use Coral API like:
$(document).on("foundation-contentloaded", function () {
const dialog = document.querySelector("coral-dialog.sharelink");
if (dialog && !dialog.querySelector(".custom-share-extension")) {
const container = document.createElement("div");
container.className = "custom-share-extension";
const textField = new Coral.Textfield();
textField.label.textContent = "Text Field";
container.appendChild(textField);
const button = new Coral.Button();
button.label.textContent = "Button";
container.appendChild(button);
dialog.querySelector("form").appendChild(container);
}
});
-
Add the proper categories, e.g., dam.gui.sharelink
, and embed it.
Option 2: Overlay the underlying component (may break in future)
If you're okay with risk (for SDK-only or local dev use), try:
-
Still overlay /libs/dam/gui/content/assets/adhocassetsharedialog
to /apps/...
-
But also overlay and modify the sharelink.html
and related dialog rendering files under: /libs/dam/gui/coral/components/commons/sharelink/
Be aware: this is not recommended by Adobe, and updates might break your customization.
Hope that helps!
Regards,
Santosh
Santosh Sai

