Salesforce already has In-App Guidance and a help menu. Why would I need Digadop Help?

Salesforce’s built-in tools are useful for what they cover, and Digadop Help is designed for what they do not. In-App Guidance shows short prompts and a limited number of walkthroughs; it is good for announcing a feature or nudging a new user, but it is not a home for real documentation. The customizable help menu is a set of static links that looks the same on every page. Learning Paths assigns onboarding curricula, which is training rather than in-context reference. Digadop Help provides the layer those tools leave open: full articles, videos, documents, and knowledge checks delivered on the specific page a user is viewing, targeted down to object, record type, profile, application, and interface type.

Compare

Digadop Help vs Salesforce built-in help

Salesforce's built-in tools, In-App Guidance, the help menu, and Learning Paths, are useful for what they cover. Digadop Help is built for what they leave open: real in-context documentation on the exact page a user is viewing. The two work well together.

At a glance

Use the native tools and Digadop Help together

Capability	Digadop Help	Salesforce built-in help
In-App Guidance prompts	Complements it: prompts announce and nudge; Digadop Help is where the full answer lives.	Short prompts and a limited number of walkthrough sequences. Good for announcing a feature or nudging a new user.
The help menu	Page-aware: shows only the articles that apply to the page a user is viewing.	A set of static links that appears the same on every page, with no page-level context.
Learning Paths	In-context reference help on the page, available whenever a user needs it.	Assigns onboarding curricula. Training, rather than in-context reference help.
Content formats	Rich-text articles, videos, documents and images, external links, and quiz-style knowledge checks.	Built for short prompts and links rather than full documentation.
Targeting	By object, record type, profile, application, page, and interface type, most-specific-first.	The help menu shows the same links on every page, with no record-level or interface-type targeting.

Salesforce's built-in capabilities evolve across releases; check Salesforce's own documentation for the current behavior of In-App Guidance, the help menu, and Learning Paths.

A complement, not a replacement

Reach for Salesforce's built-in tools to announce a new feature or walk a brand-new user through their first steps. Reach for Digadop Help when a user needs the real answer in context: a full article, a short video, a document, or a knowledge check, shown on the specific page they are on and matched to their profile and app. Using both means announcements and onboarding stay in Salesforce's native surfaces while your documentation lives one click away on every page that needs it.

Documentation, targeted to the page

The customizable help menu shows the same static links everywhere. Digadop Help matches content to the page a user is viewing, targeted down to object, record type, profile, application, and interface type, most-specific-first, so different users see the right help on the same screen.

See it for your org

Free for up to 20 users of Help, then as low as $2/user/mo for additional users. Digadop counts the people who use Help, not your whole org. Past 20, Help keeps working and your admins see a notice in the Digadop admin portal. Nothing is billed automatically: to add paid users you confirm a paid plan with us on a quote, and billing starts only when you do. Get a live estimate on the pricing page, or talk to us. See also Digadop Help vs browser-extension enablement tools and Digadop Help vs digital adoption platforms.