Indexing scope sets which announced systems the Ledger Data reads return on each network in the platform's catalogue. The Ledger Data is the platform's off-chain layer that turns on-chain activity into queryable data. A system is announced once the platform has recorded its address on a network, whether or not an organisation is linked to it.
On every network the indexer follows, it indexes each announced system and the contracts it deploys, in scope or not. Excluding a system deletes nothing and does not stop the indexer. It sets a scope flag that the platform's reads filter on, so the system's data stays indexed and current while reads stop returning it. An organisation's Console screens that read an excluded system show no data for it, and the organisation gets no notice of the change.
The page does not change what an organisation can do on-chain. The contracts of an excluded system stay as they are on the network.
The page groups announced systems by network and shows each one's status: “Hidden from reads”, “Catching up”, “Attention”, or “In reads”.
Steps
Open Indexing scope
Open “Platform admin”, then Indexing scope. Each network lists its announced systems, 50 at a time. Select “Show more” for 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.
Change the scope
Use the Include in reads switch on a system's row to change its scope. Both directions apply at once for every organisation that uses the system, with no confirmation and no second approver. After you exclude a system, a message offers “Undo” for a few seconds, which includes the system again. Excluding a system also excludes every contract it deployed, even ones you never selected.
What excluding a system does
A system is either included or excluded. There is no reduced sampling rate and no partial history window. Include a system when an organisation's screens need to read its activity, token list, balances or history. Exclude a system when its data must not appear in platform reads, for example a system that a failed deploy announced and no organisation uses. Excluding a system does not reduce the indexer's workload.
Each change writes an Audit trail entry with your name and the old and new scope. The entry belongs to no organisation, because the change reaches every organisation, so no organisation's Audit trail lists it. A platform administrator reads it through the platform-wide query of the audit trail.
Excluding a system also excludes everything it deployed, and a dashed line marks the indexed data that exclusion never reaches.
Troubleshooting
The page is empty and reads No systems announced yet
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 hides the system's data from reads. Including it again makes the data readable.
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.
Frequently asked questions
Is a newly announced system indexed automatically?
The indexer indexes every announced system on a network it follows. An announcement alone does not add the system to the scope, so its data stays out of reads until you include it. A system the platform deployed for an organisation is in scope from the start.
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 reads expose for both of them together, and the Console has no control that scopes reads 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 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 change the scope of its systems?
No. A disabled network still lists its systems with a working Include in reads 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 reads would expose 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, so the page shows a plain Chain <id> heading, such as Chain 84532. The indexer does not follow a chain outside the catalogue, so the system has no indexed data yet. You can still set its Include in reads switch, and the scope applies once the network is added to the catalogue.