Last verified: October 7, 2026
What You Can Now Do
Context Memo now lets you customize which Performance sub-pages, Scans, and Rules sections appear in your product navigation. If your team only works in two Performance views and never opens Rules, those entries no longer have to sit in the sidebar. The change is small in surface area and direct in effect: the nav you look at every morning matches the work your team actually does, and new users on your account stop clicking into sections that aren't part of your workflow. For admins running Context Memo across a marketing team, this turns onboarding from "here's everything, ignore most of it" into a shorter, cleaner path.
Where It Is in Context Memo
Navigation configuration lives in your account's settings area, under the navigation controls. From there you'll see the full list of Performance sub-pages, every Scans section, and every Rules section, each with a visibility toggle. The list reflects what your plan includes, so you're configuring from what you already have access to rather than a generic catalog.
How to Use It
- Open your account settings and go to the navigation controls. You'll see three groups: Performance sub-pages, Scans, and Rules.
- Review the Performance sub-pages list and switch off the views your team doesn't open. The sidebar updates to show only the ones you kept.
- Do the same for Scans sections. If your team runs scans on a fixed cadence and only reviews results in one place, hide the sections you skip.
- Configure the Rules sections. Teams that have their alerting set and rarely revisit it can collapse this down to the one section they audit.
- Reload the product and walk the nav as a new team member would. Confirm the remaining path gets someone from login to the view they need without a detour.
- Return to the navigation controls any time priorities shift, for example when you add a competitor set or start tracking a new persona, and switch the relevant sections back on.
Why We Built It
Customers told us they were navigating through sections they don't use to reach the three or four screens that matter to them. On a daily workflow, that's friction with no payoff: more clicks to get to share of voice, more noise during onboarding, and more support questions from team members who opened a section that wasn't relevant to their role. Teams running Context Memo across several people wanted the nav to reflect their priorities, not ours.
What It Does Not Do Yet
Visibility is configured at the account level, not per user or per role. Everyone on your account sees the same navigation once you set it. If you need different views for an analyst who lives in Scans and an executive who only checks Performance, the practical approach today is to configure for the broadest set of sections your team touches and point individuals to the views they own. Hiding a section also only affects navigation; it does not change permissions, disable scanning, or stop Rules from running. If you need to restrict access rather than tidy the sidebar, that remains a permissions decision, not a navigation one.