Adobe edge delivery service | Community
Skip to main content
D
DaipayanCh
May 7, 2025
Solved

Adobe edge delivery service

  • May 7, 2025
  • 3 replies
  • 949 views

Hi, 

 

I am new to this AEM tech. Can you please help me with a few doubts I have?

We are trying to setup the Adobe commerce new Edge Delivery Services storefront following the documentation from Adobe https://experienceleague.adobe.com/developer/commerce/storefront/get-started/ .

I have a few questions:

1. Why are we required to give google drive/SharePoint folder edit access to helix@adobe.com. What purpose does this adobe email serve.

2. Can the setup be done without giving the hosted folder access to this email ID?

3. Our organization has certain policies regarding file sharing to external domains. If someone is unable to directly share the access to helix@adobe.com, what can be the workarounds?

4. If ultimately nothing works out, can we raise a ticket with Adobe regarding this?

Best answer by AmitVishwakarma

Hi @daipayanch ,

Purpose of Granting Edit Access to helix@adobe.com

The helix@adobe.com account, also known as Helix Admin, is integral to Adobe's Edge Delivery Services. Granting it edit access to your Google Drive or SharePoint folder enables:

  - Content Synchronization: Facilitates the seamless integration of your content into the EDS framework.

  - Document Conversion: Allows automated transformation of documents (e.g., DOCX) into HTML for web delivery.

  - Publishing Workflow: Supports the end-to-end publishing process, ensuring that updates in your documents reflect on your storefront promptly.

This setup is essential for the document-based authoring approach in EDS. Experience League | Adobe

 

2. Is Granting Access to helix@adobe.com Mandatory?

Yes, for the document-based authoring method, providing edit access to helix@adobe.com is necessary. This access ensures that EDS can process and publish your content effectively. Experience League | Adobe

However, if your organization's policies restrict sharing with external accounts, consider the following alternatives:

  - Universal Editor: A WYSIWYG authoring tool that doesn't rely on external document repositories.

  - AEM Sites Integration: Utilize AEM's native capabilities to manage and publish content without external dependencies. https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/edge-delivery/overview?utm_source=chatgpt.com

 

3. Workarounds for Organizations with Strict Sharing Policies

If direct sharing with helix@adobe.com is not feasible:

Internal Hosting: Host your content on internal servers and configure EDS to fetch content from these locations.

API Integration: Develop APIs that allow EDS to access content without direct folder sharing.

Consult Adobe Support: Engage with Adobe's support team to explore customized solutions tailored to your organization's needs.

These approaches may require additional setup and configuration but can align with stringent security policies.

 

4. Raising a Support Ticket with Adobe

Absolutely. If the above alternatives don't align with your requirements, it's advisable to contact Adobe Support. They can provide guidance, potential workarounds, or custom solutions to accommodate your organization's policies.


Regards,
Amit

3 replies

konstantyn_diachenko
Community Advisor
konstantyn_diachenkoCommunity Advisor
Community Advisor
May 7, 2025

Hi @daipayanch ,

 

I am not the creator of this integration, but from an architectural point of view, granting access to your SharePoint for helix@adobe.com is vital for content synchronization (both consuming and supplying), DOCX conversion to HTML, and the publication flow. Otherwise, how would the AEM EDS engine gather and process your content if it's protected? This is a crucial part of the integration because, between document authoring and page rendering, there is a process in the middle that handles your content and combines it with configuration and client libraries.

 

I suggest submitting a ticket to Adobe, and they will help you with an appropriate solution. I assume they will recommend using the Universal Editor as an authoring method.

 

Best regards,

Kostiantyn Diachenko.

Kostiantyn Diachenko, Community Advisor, Certified Senior AEM Developer, creator of free AEM VLT Tool, maintainer of AEM Tools plugin.
    D
    DaipayanChAuthor
    May 12, 2025

    Hi @konstantyn_diachenko , thank you for the explanation. The issue is resolved now.

    AmitVishwakarma
    Community Advisor
    AmitVishwakarmaCommunity AdvisorAccepted solution
    Community Advisor
    May 8, 2025

    Hi @daipayanch ,

    Purpose of Granting Edit Access to helix@adobe.com

    The helix@adobe.com account, also known as Helix Admin, is integral to Adobe's Edge Delivery Services. Granting it edit access to your Google Drive or SharePoint folder enables:

      - Content Synchronization: Facilitates the seamless integration of your content into the EDS framework.

      - Document Conversion: Allows automated transformation of documents (e.g., DOCX) into HTML for web delivery.

      - Publishing Workflow: Supports the end-to-end publishing process, ensuring that updates in your documents reflect on your storefront promptly.

    This setup is essential for the document-based authoring approach in EDS. Experience League | Adobe

     

    2. Is Granting Access to helix@adobe.com Mandatory?

    Yes, for the document-based authoring method, providing edit access to helix@adobe.com is necessary. This access ensures that EDS can process and publish your content effectively. Experience League | Adobe

    However, if your organization's policies restrict sharing with external accounts, consider the following alternatives:

      - Universal Editor: A WYSIWYG authoring tool that doesn't rely on external document repositories.

      - AEM Sites Integration: Utilize AEM's native capabilities to manage and publish content without external dependencies. https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/edge-delivery/overview?utm_source=chatgpt.com

     

    3. Workarounds for Organizations with Strict Sharing Policies

    If direct sharing with helix@adobe.com is not feasible:

    Internal Hosting: Host your content on internal servers and configure EDS to fetch content from these locations.

    API Integration: Develop APIs that allow EDS to access content without direct folder sharing.

    Consult Adobe Support: Engage with Adobe's support team to explore customized solutions tailored to your organization's needs.

    These approaches may require additional setup and configuration but can align with stringent security policies.

     

    4. Raising a Support Ticket with Adobe

    Absolutely. If the above alternatives don't align with your requirements, it's advisable to contact Adobe Support. They can provide guidance, potential workarounds, or custom solutions to accommodate your organization's policies.


    Regards,
    Amit

      D
      DaipayanChAuthor
      May 12, 2025

      Hi @amitvishwakarma , thank you for the detailed explanation. Really helpful

      aanchal-sikka
      Community Advisor
      aanchal-sikkaCommunity Advisor
      Community Advisor
      May 12, 2025

      @daipayanch Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!

      Aanchal Sikka
      D
      DaipayanChAuthor
      May 12, 2025

      Hi @aanchal-sikka, I have marked one answer as correct. Thank you

        Terms & ConditionsAccessibility statement

        Loading footer...