Capability Availability
This reference explains stable availability classes. It does not report live production settings for NataPulse or for any particular account.
How to read availability
Section titled “How to read availability”Current surface means the product surface is implemented and appears when the account has its ordinary product permission and required data.
Capability-dependent means the surface appears only when the workspace is eligible for that capability.
Optional category or data layer means a current page remains usable while one subsection, dataset, or visualization can be absent.
Limited means access can also depend on plan, approval, provider, payment path, or another operational boundary.
The live interface, account terms, and the empty or unavailable state shown to the user are authoritative.
Current product surfaces
Section titled “Current product surfaces”Core signed-in surfaces such as Live Pulse, Event Explorer, Report Center, Narratives, Calendar, Quant Signals, Watchlists, Alerts, and Settings are current when the user has the relevant base permission. Their content can still be empty because of filters, source coverage, freshness, or publication state.
Current does not mean universal access to every action. Report generation, alert management, watchlist editing, or narrative actions can require a more specific permission.
Capability-dependent surfaces
Section titled “Capability-dependent surfaces”| Surface | Availability class | Stable boundary | What the interface does |
|---|---|---|---|
| Screener | Capability-dependent; limited | Workspace eligibility plus market-data permission | Hides its navigation entry or shows a clear unavailable page; Market Desk remains the fallback. |
| Macro Desk | Capability-dependent; limited | Workspace eligibility plus supported macro data | Hides its navigation entry or shows an unavailable page without loading a partial desk. |
| NPTA | Capability-dependent; limited | Workspace eligibility, permission, and plan limits | Hides its navigation entry or shows an unavailable state; no run is started. |
| Deep Research / Equity Master | Capability-dependent | Deep Research access and separate eligibility for applicable Equity Master runs | Shows only eligible launch controls and reports an unavailable or failure state when a run cannot proceed. |
| Agent access | Limited | Authorized agent identity, live tool catalogue, and any applicable access or payment path | Discovery and execution availability can differ; the public agent page and live catalogue remain authoritative. |
These classifications do not assert that any capability is enabled globally or for the reader’s workspace.
Optional categories and data layers
Section titled “Optional categories and data layers”| Category or layer | Availability class | Fallback behavior |
|---|---|---|
| Macro Calendar | Optional category | The Calendar continues with available corporate-action categories; Macro remains visible as a disabled presto placeholder until the filter is available. |
| Earnings Calendar | Optional category | The Calendar continues without earnings rows; Trimestrali remains visible as a disabled presto placeholder until the filter is available. |
| Advanced charts | Optional data layer | Market Desk keeps the available simpler price-history view when advanced charting is unavailable. |
Other page sections can also be empty when a provider returns no supported record. An absent block is not evidence that the underlying real-world event or value does not exist.
Provider, plan, permission, and jurisdiction boundaries
Section titled “Provider, plan, permission, and jurisdiction boundaries”Provider coverage determines which assets, fields, schedules, and history are available. Plan and workspace eligibility can limit heavier or specialist surfaces. Permissions determine which users can read or manage a capability. Jurisdiction can restrict a data source, payment path, or feature.
These boundaries can overlap. Documentation status alone cannot determine an individual user’s access. See Current Product Scope and Account Access.
What the interface shows
Section titled “What the interface shows”NataPulse uses explicit states rather than simulated access:
- unavailable surfaces say that the workspace does not have the capability;
- hidden navigation avoids presenting an ineligible entry as active;
- missing categories or fields remain absent or display a gap;
- empty results explain that no matching published record was returned;
- load failures are distinct from empty data and can offer a retry;
- permissions can disable an action even while the page remains readable.
If the interface and a general documentation example differ, use the interface state for the current account and contact the official support channel available to the workspace.