Indexing scope
Choose which announced systems the Ledger Data reads on each network.
A system counts as announced once the platform has recorded its address on a network, whether or not an organisation is linked to it yet. An announcement alone does not enable indexing. If the system is outside the tracking scope, the platform records the announcement and skips its data until the system is included. Indexing scope is where that inclusion happens: it controls which announced systems the Ledger Data, the platform's off-chain layer that turns on-chain activity into queryable data, reads on each network in the platform's catalogue. Excluding a system does not delete anything: it sets a scope flag the indexer's work-selection query filters on, so already-indexed data for that system stays exactly as it is, and the indexer stops claiming new work for it.
Reach for this page only to change what the platform's indexer tracks, never to change what an organisation can do on-chain. An excluded system keeps working for every organisation using it and keeps its already-indexed data visible; only new activity stops, until you re-include it.
Changing a system's scope is recorded server-side, but the Console has no page where a platform administrator can review that history.
The choice on this page is narrower than it looks: include or exclude, with no middle setting like a reduced sampling rate or a partial history window. Include a system when a screen inside any organisation's own Console needs to query its activity, its token list, its balances, or its history. Exclude a system only when nothing in the platform reads its indexed data and the indexer's capacity is better spent elsewhere. Indexing more systems means the indexer claims and processes more work per pass across every network it covers, not just the one you are looking at.
Excluding a system carries to everything it deployed. The dashed line marks what it never reaches: data already indexed.
Steps
Open Indexing scope
Open Platform settings, then Indexing scope. Find the required network and system: if a network's list runs long, only the first 50 systems show, and selecting Show more loads the rest. A system on a chain the platform's catalogue does not carry appears under a plain Chain <id> heading instead of a network name.
Screen equivalent: the page groups announced systems by network and shows each one's status: Not indexed, Catching up, Attention, or Indexed.
Change the scope
Use the Indexing switch on a system's row to change its scope. Including a system applies immediately, with no confirmation asked. Excluding one opens a Stop indexing this system? dialog first, because it is the costly direction: a later re-include replays the system's entire history from scratch rather than resuming where it left off. Confirm there to stop indexing. Excluding a system stops indexing for it and everything beneath it in its contract hierarchy: excluding a parent system excludes every child contract that system deployed too, even if you never selected them individually.
Troubleshooting
No systems have been announced
The platform has no systems available for scope selection. Confirm that an organisation has announced a system on a network in the platform's catalogue.
An organisation reports missing indexed data for a system
Check whether indexing scope excludes that system on the network it runs on: exclusion only stops the platform from reading new activity, exactly as the page's opening describes.
Excluding a system also hid data for a contract you expected to keep
Check whether the affected contract was deployed beneath the system you excluded: exclusion cascades down the whole hierarchy, as Change the scope describes.
Indexer capacity is tight across a network with many included systems
Every included system adds to the indexer's ongoing workload on that network, not just at inclusion time. If the indexer is falling behind current activity across a network, review which included systems no organisation's own Console screen actually reads from, and exclude the ones that are not, rather than adding indexer capacity before checking scope. This page carries no on-screen signal for indexer lag itself; that assessment happens elsewhere.
Frequently asked questions
Is a newly announced system indexed automatically?
An announcement does not add a system to the tracking scope. The indexer processes it when the system is already tracked; otherwise, it records the announcement and waits for inclusion. Check the Indexing switch for the current state.
Can I exclude a system for one organisation but leave it included for another?
No. Indexing scope is a property of the system on that network, not of any organisation that uses it. Two organisations can legitimately point at the same system address. Toggling that system's scope changes what the indexer reads for both of them together, and the Console has no control that scopes indexing to a single organisation's view of a shared system.
What does No organisation next to a system mean?
It means no organisation's account currently points at that system's address. One cause: a deploy that fails partway through announces the system address on-chain without linking any organisation to it in the platform's records. The system still shows up for scope selection, and including or excluding it works the same as for any other system.
Does disabling a network in the platform's network catalogue also stop indexing for its systems?
No. A disabled network still lists its systems with a working Indexing switch on each, because the scope you set applies as soon as the platform re-enables the network. Disabling a network is a separate control in the platform's network catalogue; it does not change what the indexer would read for that network's systems once the network comes back.
Why does a system show under a chain number instead of a network name?
The system's chain has no entry in the platform's network catalogue at all, so the page falls back to a plain Chain <id> heading, like Chain 84532, instead of the network's usual name. This is expected for a chain the platform has not formally onboarded. The system underneath that heading can still be included or excluded from indexing like any other.