USER GUIDE
Logs and security
Activity, sign-in attempts, server errors, and blocking an address or unlocking an account.
Admin → Logs & security is where an administrator can see what has been happening on the workspace, and step in when something looks wrong — locking, blocking and the logging behind them are configured in Installation settings; this is where you read the result.
Four counters, three tabs
The page opens with failed sign-ins in the last 24 hours, locked accounts, blocked addresses and errors in the last 24 hours — then three tabs, each with search and paging:
- Activity — who created, changed or deleted what, across the workspace.
- Security — sign-ins, failed sign-ins, lockouts, blocks, and changes to the security settings themselves.
- Errors — server errors, if your workspace has that switched on.
Click any row to see its full detail.
Blocked addresses and locked accounts
- An account locks itself after too many wrong passwords in a row (the count and the lock length are set in Installation settings); a locked account cannot sign in, even with the right password, until the lock expires or an admin presses Unlock.
- An address that fails to sign in too many times in a short window is blocked automatically; every page and request from a blocked address is refused until the block expires or an admin unblocks it. An admin can also block an address by hand, for a fixed length of time or until unblocked, with a reason.
- Your own current address can never be blocked, by the system or by hand, and neither can
localhost.
What secrets look like here
Nothing on this page, or anywhere in Admin, ever shows a stored password, API key or secret back to you once it is saved — a field that already has one shows a note that it is stored, and saving it again without typing a new value keeps the one you already have.
Related: Installation settings, Account security, App settings overview.