The issue is that admins frequently submit support tickets due to confusion about permission levels, despite an existing help article. The best WalkMe solution is aLauncher next to the field that activates a Resource, which links directly to the help article. This approach provides context-sensitive access to the documentation exactly where admins need it-near the permission level field-encouraging its use and reducing support tickets without disrupting the workflow.
The other options are less effective:
* ShoutOut every time admins add a user(A) is intrusive and not directly tied to the permission field.
* Validation SmartTip(B) is for enforcing input rules, not linking to help content.
* Smart Walk-Thru to the help Resource(C) is overly complex for simply accessing documentation.
Extract from Official WalkMe Documentation:
According to the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 2.3: Launchers):
"Launchers placed next to form fields can activate Resources, such as help articles, providing instant access to relevant documentation to reduce user errors and support tickets." The courseGetting Started with Building WalkMe Solutionsstates:
"For underutilized help content, place a Launcher near the relevant field to trigger a Resource,ensuring users access guidance in context to resolve confusion efficiently." Option D is the best solution to reduce support tickets by leveraging the existing help article.
References:
SAP WalkMe Digital Adoption Consultant Study Guide, Section 2.3: Launchers.
WalkMe Editor User Guide, "Using Launchers with Resources" Section.
Course:Getting Started with Building WalkMe Solutions, Module 11: Reducing Support Tickets.

The WalkMe Asset Library is the centralized repository for storing and managing reusable assets, such as images, videos, and other media files, used across WalkMe deployables (e.g., Smart Walk-Thrus, ShoutOuts, Launchers). Storing the company logo in the Asset Library ensures it is easily accessible for consistent use across all WalkMe content, supports version control, and allows for efficient updates if the logo changes. This approach aligns with WalkMe's best practices for asset management, as it promotes scalability and maintainability.
The other options are not suitable for storing a logo:
* WalkMe Admin Centeris used for account management, user permissions, and configuration settings, not for storing media assets.
* Local Settingsare specific to individual WalkMe items or environments and are not designed for centralized asset storage.
* Engaged Elementsrefers to UI elements targeted by WalkMe for interaction, not a storage location for assets.
Extract from Official WalkMe Documentation:
Per the WalkMe Editor User Guide (SAP WalkMe Digital Adoption Consultant Study Guide, Section 2.4:
Asset Management):
"The Asset Library is a centralized hub within the WalkMe Editor where Builders can upload and manage images, videos, and other media files. Assets stored here can be reused across multiple deployables, ensuring consistency and simplifying updates." The courseAdvancing Your Skills in Building WalkMe Solutionsfurther states:
"To maintain brand consistency, store commonly used assets like logos in the Asset Library. This allows Builders to apply the same asset across ShoutOuts, SmartTips, and other content types without redundant uploads." Thus, option A, "The Asset Library," is the best place to store the company logo for use in WalkMe deployables.
References:
SAP WalkMe Digital Adoption Consultant Study Guide, Section 2.4: Asset Management.
WalkMe Editor User Guide, "Asset Library" Section.
Course:Advancing Your Skills in Building WalkMe Solutions, Module 3: Managing Assets and Branding.