What's New

Most enterprise software release notes read like they were written to satisfy a compliance requirement. "Various improvements and bug fixes." "Enhanced user experience." Nobody learns anything.

We take a different view. If you are trusting Sharpr with your organization's institutional knowledge, you should be able to see exactly what changed, when, and what problem it was meant to solve. This page is the running record. It is updated as we release, and it covers platform capability, integrations, security posture, and the small quality of life changes that add up.

If you want this in your inbox instead, tick the product updates box when you request a demo, or ask your customer experience manager to add you.

How to read this page

Entries are grouped by release period, newest first. Each one carries a tag so you can scan for what matters to you:

• Search covers GenAI search, summarization, and retrieval quality
• Capture covers ingestion, Sharp It, integrations, and processing
• Distribution covers briefs, newsletters, alerts, and audience targeting
• Analytics covers reporting and engagement measurement
• Admin covers permissions, provisioning, and hub configuration
• Security covers certifications, authentication, and data protection
• Platform covers performance, mobile, and interface work

Recent releases

Search: conversational follow-up in GenAI search

You can now refine a search without starting over. Ask what the research says about loyalty program abandonment, then follow with "just the European markets" or "anything from the last eighteen months," and the platform holds the thread.

Why we built it. Watching customers use search, the pattern was consistent. The first question is rarely the real question. People were retyping long queries with one word changed. The follow-up model matches how people interrogate a body of work.

Search: source-grounded answers with expandable citations

Search results now show which documents an answer drew from, with a direct path to the underlying material. Click through from any point in a summary to the page or section it came from.

Why we built it. Two reasons. First, trust. An insights leader is not going to let a summary go into a board pre-read without being able to check it. Second, discovery. The citation is often the more valuable output, because it points you to the study you did not know existed.

Capture: bulk Sharp It for research sessions

Sharp It now supports capturing multiple open tabs in one action. If you spend a Friday afternoon going through a competitor's site, their careers page, their release notes, and three trade articles, that is one click rather than seven.

Why we built it. Competitive researchers work in bursts, not steadily. The tool needed to match the behavior.

Capture: improved handling of long-form video and audio

Recorded focus groups, advisory council sessions, earnings calls, and internal training now process with better transcript accuracy and produce structured summaries with topic markers, so you can jump to the relevant six minutes of a ninety minute session.

Why we built it. Qualitative research is the most underused asset in most insight libraries, entirely because it is painful to consume. A transcript nobody can search is a recording nobody watches.

Distribution: audience-level brief personalization

Briefs can now be configured so that a single publication renders differently by audience segment. The pricing team, the field organization, and the executive committee receive the same brief cut to their interests, without three separate builds.

Why we built it. Distribution effort was scaling linearly with audience count, which meant teams capped the number of audiences they served. This decouples the two.

Distribution: alert digests and frequency controls

Recipients can now set their own alert cadence, from immediate through daily and weekly digest. Administrators can set defaults by role.

Why we built it. Alert fatigue is the fastest way to lose an executive audience. Giving people frequency control keeps them subscribed, which is better than perfect timing on a channel they muted.

Analytics: content lifecycle reporting

New reporting on content age, engagement decay, and coverage gaps. Identify material that is still being used but is old enough to need review, and topics where search demand exceeds the content available.

Why we built it. Two questions came up in nearly every customer review: what should we retire, and what should we commission next. Now the platform answers both.

Analytics: engagement export and BI connectivity

Engagement data can be exported for use in your own reporting environment, so knowledge usage can sit alongside other operational metrics in the dashboards leadership already reads.

Why we built it. The strongest budget case is the one that appears in the report the CFO is already opening.

Admin: hub templates

Spin up a new hub from a template with structure, permission model, brief schedule, and taxonomy pre-configured. Useful for organizations that create a hub per project, per brand, or per competitor.

Why we built it. Customers with federated structures were rebuilding the same configuration repeatedly. This takes a twenty minute setup down to about two.

Admin: bulk permission management

Apply permission changes across content sets rather than item by item, with a preview of the resulting access before you commit.

Why we built it. Reorganizations happen. They should not require an afternoon of clicking.

Security: SCIM 2.0 provisioning enhancements

Expanded attribute mapping and group-based entitlement sync with Okta, Azure AD, and other identity providers, so hub access follows role changes automatically.

Why we built it. Offboarding that depends on someone remembering is not a control. Entitlements should track employment without human intervention.

Platform: mobile brief experience

Briefs, newsletters, and alerts now render properly on mobile, with readable layout for long-form content and direct access to source material.

Why we built it. Executive audiences read on phones between meetings. A brief that requires a laptop is a brief that gets archived.

What we are working on next

We publish this section because customers ask, and because it gives you a chance to tell your customer experience manager if we have the priorities wrong.

Deeper integration coverage. We currently connect to Box, Confluence, Dropbox, Microsoft Teams, ServiceNow, SharePoint, Slack, and Salesforce. We are working through the next tier based on customer demand. If a system you depend on is missing, tell us. Demand drives the order.

Richer competitive workflows. Competitive intelligence teams are among our most intensive users, and they have asked for structure around competitor profiles, change tracking, and battlecard freshness. That work is underway.

Expanded analytics on decision impact. Engagement data tells you what was read. The harder and more valuable question is what it changed. We are exploring ways to connect content usage to decision points without turning it into a survey exercise nobody fills in.

How we decide what to build

Three inputs, weighted roughly in this order.

What customers tell their customer experience managers. Every Sharpr account has a named CX manager, and the notes from those conversations come directly into product planning. This is the highest signal input we have, because it comes with context about why something matters.

What the usage data shows. We can see where people abandon a search, where configuration takes too many steps, and which features get adopted and then quietly dropped. Drop-off is usually more informative than a feature request.

Where the category is going. Knowledge management changed more between 2023 and 2026 than in the decade before it. Retrieval quality, summarization, and the expectations people bring from consumer AI tools have all moved. We build toward where our customers' users will be.

What we deliberately do not do is ship capability because it is fashionable. There is a version of this product that is one chat box and nothing else, and it would demo beautifully and fail in production, because the hard part of enterprise knowledge was curation, permissions, distribution, and adoption. We keep building the unglamorous parts.

Release cadence and notification

Platform updates ship continuously. Significant capability changes are communicated in advance to administrators, with release notes, and where relevant, training materials from your customer experience manager.

Breaking changes are rare and always pre-announced. Security updates ship immediately.

If you administer a Sharpr hub and are not receiving release communications, contact your customer experience manager and we will fix that today.