Understand the signed-in news surfaces across feed review, impact timeline, entity enrichment, and research handoff.
Use this guide when you need to move from raw feed browsing into entity and event enrichment without losing watchlist, instrument, or time-range context.
These are the current signed-in news and enrichment surfaces that shape the workflow.
Browse workspace-linked macro, market, and social feed items from the primary news page.
Constrain the feed by watchlist, linked instrument, date range, source scope, impact, and sentiment.
Review time-bucketed impact trends and inspect the selected item in the same workflow.
Use research news enrichment to identify which entities are being discussed and how often.
Use event streams to classify catalysts and news themes before they become research inputs.
Use this sequence to keep news review tied to real workspace context instead of generic feed browsing.
Pick the watchlist, instrument, time range, and filter posture before you interpret item volume or impact.
Use feed items and the timeline in one pass so the selected story is grounded in recent activity, not viewed alone.
Move into entity mentions and event tags once a story or cluster looks important enough to classify more deeply.
Once the signal is meaningful, pass it into research or agent workflows while preserving the feed context you used.
The feed becomes useful only after its watchlist, time, and scope inputs are made explicit.
Pick the watchlist and instrument first so the feed reflects a real workspace context instead of an arbitrary global slice.
Use the date window and refresh button together. Changing the range without refreshing can hide the context behind the current feed state.
Search, sentiment, and impact threshold are the fastest way to move from feed volume into a reviewable signal set.
Macro, stock, crypto, FX, and social chips reshape the feed semantics. Use them deliberately so you know what kind of signal you are reviewing.
The right-hand review surfaces are where a story becomes a useful signal instead of a headline.
The feed panel is the primary selection surface. Use its empty state and row selection behavior to tell whether the problem is data scope or item relevance.
Read the impact timeline next to the feed so a single headline is judged against the surrounding burst or lull in activity.
Use the summary card to inspect total item count, provider mix, and sentiment buckets before escalating one provider's narrative.
The selected item panel combines summary, linked instruments, source link, detail payload, and market handoff. Use it to preserve context when escalating into research.
Use these scenarios when you need a more concrete news-review pattern than the generic workflow loop.
Scope the feed to the relevant watchlist and date window, raise the impact threshold, and compare the selected headline against the impact timeline before deciding whether it is a one-name event or the start of a broader move.
You leave with one validated story, a clear symbol context, and a documented handoff into research or agent follow-up.
Use search, sentiment, scope chips, and provider mix together, then inspect entity mentions and event tags to see whether multiple names share the same catalyst.
The review ends with a narrower theme thesis instead of a watchlist-wide reaction to one article cluster.
Once the selected item, summary card, and timeline agree, carry that exact context into Agent Workbench or Research rather than summarizing it again from memory.
The downstream workflow inherits the exact article, timing, and impact context you already validated.
Jump into the signed-in news surface and review the live feed, filters, and impact timeline.
Use the research workflow when a news signal becomes a factor or label investigation.
Use the agent workflow when recurring briefs, alerts, or inbox delivery should be built on top of the news signal.
Mar 24, 2026
Report unclear guidance, stale contracts, missing coverage, or broken docs UI on this page.
Open feedback issueJump to the section you need without losing your place.
Mar 24, 2026
Report unclear guidance, stale contracts, missing coverage, or broken docs UI on this page.
Open feedback issue