Skip to content
AtlasDocs
Sign inGet started
Updated Oct 16, 2026

Logs

Every sign-in and what became of it, and a separate record of who changed what. When a customer says it does not work, start here.

Open it now:Logs

Two logs

TabAnswers
Connection logsWhat your program and its customers did: sign-ins, refusals, bans, sessions ending, messages your program sent.
Application logsWhat people and tools did to the application: you, your resellers and your integrations generating keys, banning, changing settings. Filter by actor (owner, reseller, API, system) and by kind of action.

The rest of this page is about Connection logs.

Reading a row

A row has a colored type, the time with how long ago, and the message. Under it, the identity of the event: USER for an account or LICENSE for a key, EMAIL, IP, location, device, HWID, the build's HASH and the session. Click any key, address or hardware ID to open everything linked to it, or click the row for its details panel.

Many messages carry an i button. Hover it, or tap it on a phone, for what the message means and what to do. A refused sign-in often has an action on the right of its row: Authorize this build for an unauthorized program, Reset this license for a hardware or IP mismatch, Extend this license for an expired one, and so on.

Event types

TypeMeans
SUCCESSA sign-in was accepted.
DENYA sign-in was refused. The message says why; Why a sign-in was refused lists every cause and fix.
BANA ban was applied, by you or by an alert rule.
DISCONNECTA session ended: the program signed out or disconnected, timed out with no check-in for 30 seconds, was ended by an admin, or ended because the key was banned or the application disabled.
ADMINAn action you or a teammate took on a license or session.
ERRORThe server hit a problem handling a request.
WARNWorth a look, nothing was refused. A failed running-build proof in Log only mode is one.
LOGA message your own program sent with Network::SubmitLog.

Account events are tagged too: Register, Account login, Verify (email codes and resends), Redeem and Password reset.

Find things

  • The strip across the top counts events by type; click one to filter. Account filters sit beside it.
  • Search matches the message, the key, the username, the email, the IP, the device and the location. Press / to focus it.
  • Sort by date or by type, newest or oldest first.
  • Live tail follows new events as they arrive. Turn it off to read a fixed list; a pill then counts the new rows waiting.
  • Export saves the filtered rows as a CSV file.

Arriving from a key, an address or a ban opens the list already filtered to it.

Clear logs

Clear all permanently deletes the connection logs of the application after a confirmation. It is a separate permission, and it cannot be undone. Atlas also removes old entries on its own over time.

Was this page useful?