Skip to content

Add Embed SDK FAQ updates (Clover use case)#289

Merged
sravyap017 merged 7 commits intomainfrom
update-sdk-clover-faq
Apr 8, 2026
Merged

Add Embed SDK FAQ updates (Clover use case)#289
sravyap017 merged 7 commits intomainfrom
update-sdk-clover-faq

Conversation

@sravyap017
Copy link
Copy Markdown
Collaborator

Description

This PR updates the Adobe Express Embed SDK FAQ by incorporating common partner integration questions identified from the Clover use case.
The changes generalize partner-specific questions into reusable documentation and improve clarity around real-world integration scenarios.

Related Issue

N/A

Motivation and Context

The existing SDK FAQ primarily covers basic usage and does not address several common partner integration questions.

This update improves documentation by:

  • Addressing gaps identified during partner discussions (e.g., Clover)
  • Providing clarity on authentication flows and user experience patterns
  • Documenting responsibilities between Adobe and integrating applications
  • Reducing repeated partner questions and onboarding frictions

How Has This Been Tested?

  • Changes were tested locally using the docs development environment
  • Verified rendering and formatting via local dev server (localhost)
  • Confirmed that:
    • New FAQ entries appear under correct sections
    • Markdown formatting is consistent with existing documentation
    • Links and configuration references (e.g., loginMode, appConfig) render correctly

Screenshots (if appropriate):

Screenshot 2026-04-07 at 10 10 42 AM

Types of changes

Documentation update

link : http://localhost:3000/express/embed-sdk/docs/guides/troubleshooting/faq/

Checklist:

NA

@sravyap017 sravyap017 requested a review from nimithajalal April 7, 2026 04:55
@sravyap017 sravyap017 self-assigned this Apr 7, 2026
@sravyap017 sravyap017 added the documentation Improvements or additions to documentation label Apr 7, 2026
Copy link
Copy Markdown
Collaborator

@apoos-dev apoos-dev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

~Can we avoid redundancy. I see "loginMode" multiple times and same for "terms of use" question and the entitlements question. Can you consolidate them.
~We can also remove this questions "Can generative AI features be disabled?" because it is not a frequently asked question, it was a one off from clover and I think the generative AI is express's USP. @njalal can confirm on this
~I'm not sure if it's okay to mention Adobe IMS in the public FAQ. AFAIK it seems like an internal dependency
~ for "Can I control which templates are shown to user", it's good to also add link to the selectedCategory and other properties like this: https://developer.adobe.com/express/embed-sdk/docs/v4/shared/src/types/editor/app-config-types/interfaces/base-editor-app-config

@sravyap017
Copy link
Copy Markdown
Collaborator Author

Can generative

Hi @apoos-dev

Thanks for the feedback!

  • Removed redundant content across loginMode, Terms of Use, and entitlements sections
  • Removed the generative AI question.
  • Updated wording to avoid internal references like Adobe IMS to Generic - "Adobe Account"
  • Added documentation link for template configuration (appConfig)

Please take another look.

cc: @nimithajalal

Copy link
Copy Markdown
Collaborator

@apoos-dev apoos-dev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added a comment please review

Entitlements follow the user’s Adobe account subscription: free accounts have limited templates, assets, and generative features; premium accounts have broader access and higher limits. Your app can supply premium access or let users sign in with their own Adobe account.

Your application can choose to provide premium access to users or allow users to authenticate with their existing Adobe accounts.
To control how premium generative features appear for users without entitlements, you can use configuration such as `SHOW_FIREFLY_PAYWALL_FOR_UNENTITLED_USERS` (whether they see a paywall when using those features).
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you remove this line. Users cannot configure feature flags themselves

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @apoos-dev , removed the feature flag configuration line as suggested.I did verify in slack thread and yes it requires Engineering effort.

@nimithajalal could you please take look and provide your comments.
Thanks !

Copy link
Copy Markdown
Collaborator

@nimithajalal nimithajalal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left a few comments

@sravyap017 sravyap017 merged commit a7bde21 into main Apr 8, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants