Docs → Clan Administration → The Import Dashboard

Something arrived from a scan that the portal could not file, and it is waiting for you. That is the whole purpose of Clan Management → Import Dashboard: it is not a list of imports, it is a list of decisions only a person can make. When there is nothing to decide, the page says All Clear! and there is genuinely nothing for you to do.

The great majority of rows never reach this page. Names are read from the game and matched to your roster automatically; matched rows are filed and forgotten. What lands here is the residue: a name nobody recognises, a hero level that jumped further than a hero level should, a chest type your catalogue has never seen.

The tiles, and what each one is telling you

Across the top: Unknown Players, Hero Approvals, VIP Approvals, Chest Issues, a Player Fetching Issues tile that only appears while first-run name matching is outstanding, and Total Issues. Below them three shortcuts — Chest Imports →, Player Imports → and Event Imports → — take you to the imports themselves rather than to their loose ends.

The body of the page is up to three collapsible sections, each shown only when it has something in it.

Unknown Players

A name was collected that does not match anybody on your roster. Three things cause it, and they need different answers: the player is new and not yet on the roster, the player changed their name in the game, or the name was misread. Total Battle sets names in a decorative font over busy artwork, so I, l and 1, or O and 0, are genuinely hard to tell apart, and accented characters like ö, ü, æ and ø come out wrong more often than plain ones.

Each row shows the name, how many rows are affected and which sources they came from. Two buttons:

• Match/Alias opens a picker of your members with two ways to finish. Add Alias records the scanned spelling as an alternative name for that player — the portal will match it silently from now on, and the player keeps their real name. Match files the affected rows against the player without recording the spelling.
• Ignore drops the name from every import. Use it for a genuine misread that will never recur.

Hero Level Changes and VIP Level Changes

Most stat changes are applied without asking. These two are held back when the jump is large enough that a misreading is more likely than the real thing, because a wrong hero level quietly distorts every requirement and reward that depends on it.

Each row shows the player, Current → Scanned and the size of the change, with ✓ Approve and ✗ Reject. Approving writes the scanned value to the player. Rejecting leaves the current value alone and clears the item. Where the same player appears in several scans, only the highest scanned value is shown, and your decision covers all of them.

Missing from Scans

The mirror image of Unknown Players: somebody on your roster was not found in a scan that should have contained them. Almost always one of two things has happened — they changed their name in the game and the portal still has the old one, or they left the clan and the roster has not caught up.

The row shows their hero level and how many scans they have been missing from, with two actions:

• Match to New, offered when the same scan found a name nobody claims. Pick that name and Match & Rename renames your existing player to it, keeping all their history. This is the correct answer to a name change.
• Ignore removes them from the missing list without changing anything else.

Chest Issues

A chest import contained a chest type your clan's catalogue does not have, so those rows cannot be given a point value and cannot be imported. The row shows Chest Source, Chest Name and how many rows are affected, with a Review # button per affected import.

The fix is not on this page: add the chest to Clan Management → Chest Catalog with the point value you want it to be worth, then come back and re-run matching on the import. If your clan has Receive Global Chests switched on in Clan Management → Clan Settings, chests added to the shared catalogue arrive in yours automatically and this section stays much quieter.

What the import statuses mean

On Chest Imports every import carries one of six statuses. Two of them are the ones to know: Review is the import that needs you, and Ready is the import that is waiting to be committed.

An import can sit at Ready indefinitely. To clear them, either use Import All Ready Items on the Chest Imports page, or stop the situation arising: in Clan Management → Clan Settings, edit the 🔗 Webhook & Chest Import card and turn on Auto-import ready chests. Fully matched rows are then written as soon as they are read, and only rows with a problem wait for you.

Player Fetching Issues

This section belongs to the day your clan is connected, and only that day. When the portal first reads your clan from the game it has to decide which in-game member is which portal player, and it shows you its working: Auto-Matched Players to check, Unmatched Game Members the game knows and the portal does not, and Unmatched Portal Players the other way round.

Correct anything wrong, match what you can, and once the result is applied the whole section disappears permanently — from then on the ongoing sync handles it, and anything it cannot resolve turns up under Unknown Players instead.

Where the imports themselves live

Three pages hold the imports themselves. The three buttons at the top of this dashboard are the way in, and for two of the three they are the only way in — bookmark them if you use them often.

• Chest Imports → — one row per scan, with the counts for Ready, Player Missing, Chest Missing and Imported, plus Review, Re-run Matching and Import All Ready Items. Reached from this page only; it has no menu entry of its own.
• Player Imports → — the scans that carry hero level, Might and other stats. Also reached from this page only.
• Event Imports → — the record of event point imports. Almost every row here is the portal's own end-of-event collection from your clan journal, which arrives and approves itself; the rest are points files an admin uploaded by hand to repair an event. This is the one of the three that is also in the menu, as Clan Management → Imports: Event Points.

If your clan feeds chest data from its own tool rather than a chest grabber account, the endpoint and key for that are in Clan Management → Clan Settings under 🔗 Webhook & Chest Import. Whatever arrives that way lands in exactly the same place and is reviewed here in exactly the same way.

What never reaches this page

It is worth being clear about the limits of the word "import", because it covers far less than people expect.

• Event points are not something you import. While an event runs, your clan's linked game account reads the in-game event board on every check-in and writes each member's score straight into the event. When the event ends, the game writes the final scoreboard into your clan journal and the portal collects it on its own, normally within an hour or two of the daily reset. That collection ignores anybody it cannot place and approves itself — so a healthy event produces no work here at all. Uploading a points file is a repair tool for an event that got nothing, not the normal route.
• Event chest counts are never imported into the event. Chest claims are imported once, into your chest data, and that is what this page reviews. An event then counts those claims fresh every time a screen shows them. There is no second import step between your chest data and an event.
• Chat activity and resource deliveries are not imports at all. Chat is read from your in-game chat group once an hour while an event is open, and resource deliveries are read from your clan capital log on the same check-ins as everything else. Neither has an import record, a status or a review queue.

Common questions