The admin console — Nixt DNA Server docs

The admin console is the web application for running Nixt DNA Server day to day. Everything it does goes through the admin API, so each page shows only what your role may use, and an error is shown in the server’s own words.

Signing in

Open the console.
Under Sign in as, choose Administrator, Domain administrator, Helpdesk or Auditor. A domain administrator also enters The domain you look after. To manage a server other than the one the console came from, open Use another server and enter its Server address.
Choose Continue, and sign in on your server’s own page with your mail address and password and, if asked, your second step.

The console never sees your password: you type it on the server’s page. What each role may do is set out in Roles and the audit log.

The server’s operator opens the console from inside the server itself; see The operator’s console.

Finding your way

The pane on the left lists the pages your role may use.
Go to anything: press ⌘K (Ctrl+K on Linux), or choose Go to in the title bar. Type any word of a page, a person, a domain or a thing to do, and press Return.
Press ? to list every keyboard shortcut. They are also under Keyboard shortcuts in the account menu.

The pages

Page	What you do there
Overview	See whether mail is working, in one sentence; what needs attention first, each item with the page that fixes it; what changed lately; today’s counts and two weeks of mail; and each domain’s state.
People	Find anyone in the organisation. For a person: their name and addresses, password and sign-in, second steps and recovery codes, app passwords, delegates, role, storage and sending limits, automatic reply, legal hold, and where they are signed in. Groups and aliases are here too. See Domains and accounts.
Domains	Each domain’s state, its DNS records, its proof of ownership and its signing keys, with Check again after you change DNS. See DNS records.
Mail flow	The queue, and what to do with a message in it; the message trace of any message; reports from other servers about your domains; and requests to forward mail outside the organisation.
Usage	Storage across the organisation and the fullest mailboxes; who sent the most in the last day against their limits.
Protection	Quarantine, with release and discard; allowed and blocked senders; the filter’s rules; the spam classifier; and Scan again, which checks mail already received against today’s filtering. See Spam and malware filtering.
Sign-in and sync	Access rules for apps, protocols and networks, tested before you save; single sign-on; directory sync; and SCIM tokens.
Records	For the organisation’s auditor: cases and legal holds. See Discovery for legal cases.
Settings	The organisation’s settings in plain words, with every earlier version kept and one click to put one back: MTA-STS, encryption, password length, second steps at sign-in, forwarding outside the organisation, and the storage ceiling. See Runtime settings.
Alerts	Who is told when something goes wrong, and at what level, and every alert of the last 90 days. See Monitoring.
Audit log	Every change made to the organisation: who, when, and what it was before. Searched, filtered, and saved as a CSV file.
Changes coming	What an upgrade changes that your people could notice, and your choice for each: Take it on or Keep it as it was. See Upgrades.
Organisation	Its name and state, its usage, and which console and server are answering.
Storage	How much each organisation stores, by kind, and how it grew.

The operator’s pages

The System pages are for the server’s operator alone, opened from inside the server:

Page	What the operator does there
Topology, Cluster	See every node and where it is; drain a node, put it back, or forget one gone for good. See Nodes of a cluster.
Disaster recovery, Links	The standby site and how far behind it is, and links to other clusters. See A standby site.
Upgrade	The rolling upgrade of every node, and the installation’s own changes. See Upgrades.
Backups	Daily backups, Back up now and Test a restore now. See Backup and restore.
Listeners’ TLS, Integrity	The TLS floor for every listener, and the integrity scrub of stored mail.
Storage	Each node’s disks, how fast they fill, and what each organisation stores.