A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.
Both behaviors relate to how the FAQ web part is currently designed rather than configurable issues.
- "Copy link to question" goes to the top of the page
The FAQ web part produces organized FAQ sections on a SharePoint page, but the documentation only guarantees that it can share specific Q&A pairs by copying the link, not that the link will auto-scroll or deep-link to the exact question location. The behavior described (landing at the top of the page) is consistent with a limitation of how the web part anchors questions on the page, not something that can be changed in settings. There’s no documented workaround to force the link to jump directly to the specific question; the supported behavior is that the link points users to the page that contains that Q&A. - Viewer-submitted questions being filtered out
The FAQ web part’s viewer feedback pipeline is explicitly designed to filter submissions:
- As the FAQ author, viewer submissions can be enabled or disabled in the right-hand property pane using a toggle.
- When enabled, viewers type their question and select “Send to author.”
- When the author returns later, enters Edit mode, and selects Add a question, only viewer-submitted questions that the system considers relevant appear in the dropdown list.
- Non-relevant questions are automatically filtered out by design.
There is no documented way to see all submitted questions or override this relevance filter. The system does not expose a separate log or list of filtered-out questions. This behavior is independent of whether the FAQ content was imported manually or generated by AI; the relevance filter applies in all cases.
Given the current documentation:
- The inability to deep-link directly to a specific question and
- The loss of viewer submissions deemed non-relevant
are limitations of the FAQ web part’s current implementation, not misconfiguration. For scenarios where every viewer question must be retained, an alternative feedback mechanism (for example, a separate form or list) would be required outside of the FAQ web part.
References: