Raffaella Gozzini
09/08/2025, 5:24 PMRaffaella Gozzini
09/08/2025, 5:24 PMYvonne Changamuka
09/08/2025, 5:49 PMRaffaella Gozzini
09/08/2025, 5:53 PMYvonne Changamuka
09/08/2025, 7:48 PM?hideControl=[controlElement1,controlElement2]
To give you more context, in a URL such as:
<host_url>/dashboards/embedded/#/workspace/<workspace_id>/dashboard/<dashboard_id>?showNavigation=false&showEmbedButton=false
you can replace the part ?showNavigation=false&showEmbedButton=false with:
?hideControl=[topBar,widgetsCatalogue]
Here, controlElement1 is set to topBar and controlElement2 is set to widgetsCatalogue.
You can find more details on which elements can be hidden in our documentation here
Regarding your follow-up, the resizing of the embedded dashboard can be managed on your end by adjusting the width parameter of the iframe. For example, in the snippet below you can change the width value to fit your preferred display:
<iframe
title="Embed GD Application"
id="embedded-app-frame"
src="<host_url>/dashboards/embedded/#/workspace/<workspace_id>/dashboard/<dashboard_id>?apiTokenAuthentication=true"
width="1300"
height="800"
></iframe>
On mobile view, the behavior you are seeing with the Edit button is expected. The visibility of certain controls depends on the available screen width. When embedding via iframe, the size you allocate directly affects the display. If the horizontal space is less than 1170px, elements such as the Edit button will be hidden.
You can find more details about this behavior in the attached. documentation .
Let me know if this helps