Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
Full In-App Guidance entry
How-to guide

Build a Lightning prompt with In-App Guidance

Authoring a prompt is a 10-minute task once the message is clear. The harder work is deciding what message users actually need.

By Dipojjal Chakrabarti · Founder & Editor, Salesforce DictionaryLast updated May 21, 2026

Authoring a prompt is a 10-minute task once the message is clear. The harder work is deciding what message users actually need.

  1. Open Setup, In-App Guidance

    Setup, Quick Find, type In-App Guidance, click the result.

  2. Click Add Prompt or Add Walkthrough

    Prompt for single-step; Walkthrough for multi-step. Pick based on the message complexity.

  3. Pick the target page

    Choose the Lightning page (record page, Home page, app page) where the guidance should appear.

  4. Author the content

    Use the rich-text editor for the title and body. Add an image or video if it helps. Configure the action button.

  5. Set targeting

    Filter by profile, permission set, or user attributes. Pick the audience carefully; broad targeting produces noise.

  6. Activate and monitor

    Activate the guidance. Check engagement metrics weekly; adjust copy or targeting if the prompt is being ignored or universally dismissed.

Mandatory fields
Target pagerequired

The Lightning page where the prompt appears.

Contentrequired

Rich-text body of the prompt or walkthrough step.

Audience filterrequired

Profile, permission set, or user-level criteria.

Display frequencyrequired

Once per user, every visit, on a schedule, or until dismissed.

Gotchas
  • Targeting too broadly produces guidance fatigue. Users dismiss everything once they have seen too many irrelevant prompts.
  • In-App Guidance does not work in Salesforce Classic. Orgs on Classic see the Setup node but cannot deliver guidance to end users.
  • Engagement metrics take a few days to accumulate. Do not judge a new prompt by its first 24 hours.
  • Walkthrough steps targeting components that are not currently visible silently skip. Test walkthroughs on real records with the components actually loaded.

See the full In-App Guidance entry

In-App Guidance includes the definition, worked example, deep dive, related terms, and a quiz.