Ideas, accounts, and customer signal are closer together.
This release tightens the loop between customer-facing idea collection, account-aware prioritization, and day-to-day Discovery review. Ideas now carry richer working context, demand trends, attachments, ownership, and status review. Account context is easier to inspect across signals, insights, ideas, opportunities, Gong, Salesforce, and rollups. Integration, API, and MCP surfaces also moved forward so product context can keep traveling into the systems where teams already work.
What changed
- Ideas can now carry briefs, clarifying questions, assignees, custom statuses, attachments, Kanban review, and vote trends over time
- Customer-facing portal and idea import paths now preserve more product, status, vote, contact, account, and taxonomy context
- Account and Linked ARR context is easier to inspect across signals, insights, ideas, opportunities, account pages, Gong, and Salesforce workflows
- Discovery review gained calmer trend, import, snooze, hidden-insight, Evidence Atlas, and tree controls for teams reviewing large signal sets
- Jira, Teams, Gong, Salesforce, Pendo, External API, and MCP surfaces all moved closer to a practical connected workflow
Ideas became a working surface
Ideas can now hold more of the context a PM needs while deciding what should happen next: generated briefs, clarifying questions, assignees, custom statuses, attachments, linked evidence, and a Kanban view for status review. A new idea demand trends view shows vote momentum over time so portal demand does not stay trapped in a flat backlog.
- Product teams can review customer demand without separating the idea from its supporting evidence
- Portal votes become a trend signal, not just a lifetime count
- Supporting files, exports, screenshots, and notes can stay attached to the idea being evaluated
Portal and idea migration work is less lossy
The Ideas Portal now supports more of the customer-facing replacement path: product-scoped portals, customer-prefix access, SSO launch paths, portal branding, visible requests, simple voting, taxonomy-scoped submission and browse controls, and header access from Discovery when configured. Idea imports also preserve more workflow status, votes, creator, contact, domain, and account context.
- Teams moving from an existing idea system can preserve more of the context they already rely on
- Different products can expose different portal scopes and request language
- Customer-facing votes and internal idea review can meet in the same Discovery graph
Account context is easier to trust
Signals, insights, ideas, opportunities, and account pages now carry richer account links, Linked ARR context, source icons for inherited relationships, portal-user and vote metrics, and clearer related-record rollups. Gong imports can match calls back to accounts, and Salesforce account linking supports search, inspection, selected-field linking, external account links, and safer re-imports.
- Prioritization can show which accounts are behind a pattern instead of only what was requested
- Inherited account relationships are easier to inspect and explain
- Salesforce and Gong can support account-aware Discovery instead of creating orphan evidence
Discovery review is calmer at scale
Discovery gained more review controls for teams working through large evidence sets: trend actions, flexible trend windows, source-type filtering, copyable summaries, feedback and approval actions, snoozed and hidden insight handling, import review for call sources, scoped analysis input, Evidence Atlas polish, and better tree and trace navigation.
- Weekly review can happen from the same surfaces where new patterns appear
- PMs can reduce noise without losing the trail back to source evidence
- Large workspaces have more ways to narrow review before committing records to the graph
More connected paths for technical teams
Integration and technical surfaces continued to expand. Teams have stronger paths around Jira import reliability, Teams calendar transcript selection, Pendo setup, External API context documents and OKRs, and MCP tools for Discovery review and initiative operations.
- Existing systems can feed Zentrik without forcing a wholesale workflow change
- Technical evaluators have more concrete API and MCP surfaces to inspect
- Product context can travel into agent and delivery workflows with less manual copying
More in this release
Additional updates
- Idea briefs, clarifying questions, assignees, custom statuses, and Kanban review
- Idea attachments with safe text preview, download, rename, delete, and drag-and-drop support
- Idea demand trends with activity and total lenses, status filtering, taxonomy filtering, and vote momentum
- Ideas Portal product scopes, customer-prefix access, SSO launch paths, branding, taxonomy controls, visible requests, and header access
- Idea import status mapping, vote import, creator attribution, organization-domain matching, and account/contact/domain backfill controls
- Account links, Linked ARR context, source icons, related rollups, portal-user counts, vote metrics, and account table polish
- Gong account matching and Salesforce account linking with search, inspection, external links, and safer re-imports
- Discovery Trends review actions, source filters, stable colors, loading polish, and copyable summaries
- Import review, scoped analysis, Evidence Atlas polish, trace navigation, snoozing, and hidden insight visibility
- Teams calendar transcript selection, Jira OAuth hardening, Pendo setup, and expanded External API and MCP context surfaces
- Plan-limit copy, session reliability, dark-mode table row contrast, assignee sorting, and import dropdown layering polish