In Edge Delivery Services, when using document-based authoring, how can we restrict access to data in the website root, such as Excel and JSON files, to prevent external users from accessing them?

In our Edge Delivery Services, we're utilizing document-based authoring with a SharePoint repository and storing all documents in the website root folder. How should we manage documents created for testing and development, such as those for QA, Dev, and Staging environments?

Adobe documentation for Edge Delivery services mentioned about merging code into the main branch. Should all pull requests go straight to the main branch for the live site, or can we create separate develop and release branches like in typical AEM projects?

Thank you for your response @EstebanBustamante, much appreciated,The video demonstrates how to connect to AEM and import assets from a custom palette in EDS. I’m specifically looking for a way to integrate Dynamic Media and process EDS assets directly, without relying on AEM.Any insights on this wou...

I'm looking for guidance on integrating Dynamic Media with the Edge Delivery Service website. The goal is to have the site pages retrieve their assets directly from Dynamic Media URLs especially for images and videos. Could anyone provide insights or steps on how to do the integration?