Flag Missing or Incorrect Information From a Page

🎯 Who this article is for: Anyone who reads a page and notices something that's wrong, out of date, or no longer accurate.

💼 Package requirements: Knowledge Engine is available as an add-on for the Starter Package, Growth Package, and Enterprise Package on Google and Microsoft suites. 

🔒 Permissions: Any user can flag content from a page in Pages 2.0. Only admins can view and manage flagged issues in the Gap Dashboard.

💻 Desktop only: This feature is not available on mobile.

1. Overview

Knowledge Engine gives everyone on your team a simple way to keep your intranet accurate. When you spot something that looks wrong or out of date while reading a page, you can flag it on the spot — without leaving the page or tracking down who to contact. Every flag goes straight to the Gap Dashboard, where platform admins can review, assign, and resolve it. Content owners can view and manage the gaps assigned to them.

The more accurately your intranet reflects how your organization works, the more people can find answers on their own — without interrupting a colleague or sending a Slack message to track something down.

2. Use cases

• Keep your intranet one step ahead of change: Processes, policies, and tools change regularly, and pages don't always keep up. When an employee reads a page and recognizes that the guidance no longer reflects how things are done, flagging it ensures the right team is notified before the guidance causes confusion.
• Keep your intranet one step ahead of change: When something in your organization changes, existing pages can become inaccurate overnight. Flagging a page that no longer reflects the current reality gives admins a clear signal that it needs to be reviewed and brought up to date.
• Make every page genuinely useful: Some pages cover part of a topic but leave out information people need to act on. Flagging incomplete content gives admins a clear signal to expand it, so every page delivers what people actually need.

3. Before you begin

• Knowledge Engine must be enabled in your environment. If you're unsure, check with your admin.
• All search data used for gap detection is anonymized. Platform admins see overall search trends and cannot identify which individual employee searched for something.
• Flagging missing or incorrect information from a page is only available in Pages 2.0.
• Any user can flag content from a page. No admin access or special permissions are required.
• Once submitted, your flag is reviewed and resolved by your admins and assigned content owners through the Gap Dashboard. Tracking isn't available to end users at this stage.

4. How to flag incorrect or outdated information from a page

1. Navigate to the page you want to flag.
2. Highlight a piece of text within a text widget that looks wrong, outdated, or incomplete.
3. Click Mark as incorrect in the floating toolbar that appears.
4. In the side panel, select a category: Missing information, Incorrect information, or Other.
5. Optionally, click Add details to expand the form. In the first field, describe what looks wrong (for example, "The policy still references the previous parental leave entitlements"). In the second field, explain what the correct information should be (for example, "The policy was updated in January. The page needs to reflect the current entitlements").
6. Click Submit.

⚠️ Important: Manual flagging from a page is currently only available on text widgets. If the content you want to flag is in a different widget type, navigate to the nearest text widget and highlight the most relevant surrounding text to flag the gap.

5. What happens after you flag an issue

Once you submit a flag, it goes directly to your organization's admins for review.

• The flag appears in the Gap Dashboard as a content gap — a recorded issue that admins can review and act on.
• When a user manually flags an issue, the priority of the gap is bumped to high. This is because a deliberate flag is a clear signal that someone was actively looking for something and deserves a reliable answer.
• Related gaps are grouped and surfaced together in the Gap Dashboard, giving admins a clearer picture of where content issues are most frequent.
• If no similar issue exists, a new one is created.
• Admins review the issue, assess its priority, and assign it to the right person to resolve.
• Once the content has been updated or corrected, the assignee or platform admin must manually update the status to resolved in the Gap Dashboard.

6. Best practices

A specific flag is a useful flag. The more context you add, the faster it gets resolved — and the easier it becomes for your organization to keep its intranet accurate without extra coordination. Here's how to make your flags as useful as possible.

• Describe what's wrong, not just that something is wrong: When flagging, include a short note about what doesn't look right. Whether it's a step that no longer works or guidance that references something outdated, that context helps admins understand the issue and assign it to the right person faster.
• Flag it even when you're not completely sure: If something reads as confusing, inconsistent, or possibly out of date, flagging it is still useful. Admins can review the context and dismiss it if the content turns out to be accurate. A flag that gets dismissed is better than an issue that goes unreported.
• (Admins) Review page flags alongside automatically detected gaps: Manual flags from pages and automatically detected gaps tell different parts of the same story. Reviewing them together in the Gap Dashboard gives you a fuller picture of where your organization's knowledge needs attention and helps you prioritize what to address first.
• (Admins or assignees) Let people know when a page has been updated: When content has been updated, posting a short note in the relevant channel closes the loop for the people who flagged it, and reduces the chance of the same issue being raised again.

7. Frequently asked questions

What if I'm not completely sure the information is wrong? 

Flag it anyway. Admins review every flag and will dismiss it if the content turns out to be accurate. It is better to report something that turns out to be fine than to leave a genuine issue unaddressed.

Can I track what happens to my flag after I submit it? 

Once submitted, your flag moves into the Gap Dashboard for admins to review and manage. End users don't currently receive notifications when a flag is reviewed or resolved. If you want to stay informed, ask your admin or relevant content owner (if known) to post an update in the relevant channel when content is corrected.

Will the person who wrote the page be notified when I flag it? 

Not immediately. Admins review flagged issues in the Gap Dashboard and decide who to assign them to. Once a gap is assigned, the designated owner is notified and becomes responsible for resolving it.

Can a gap come back after it has been closed? 

Yes. If similar issues are flagged again after a gap has been marked as closed, it can resurface in the Gap Dashboard. This helps ensure that fixes hold over time, rather than the same problem quietly returning.