Notifications and Logs

Notification Templates

Three tabs: Channels & Templates, Email Layouts and Test Sender. This is where the wording your members receive is edited, and where you can send yourself a specimen to check a template renders and that your SMTP provider is actually delivering.

Delivery Queue

What has been sent and what is waiting. Tabs for Email Queue, Push Queue and Test Sender, each with an hourly chart above the table and filters for period, template or type, and status.

Send yourself a magic link or use the test sender after changing your SMTP provider — that is the quickest confirmation that mail is going out.

Send Bulk

Listed in the sidebar under Notifications, and refused on a node. It reads and decrypts every user’s details across a whole deployment, so it stays a central operation. Expect an error if you open it.

Audit Log

Headed User Activity Logs. Every recorded user action, newest first, with CSV to export what you are looking at and Refresh to re-read it.

Function Logs

Two tabs, Execution Logs and Errors. This is what the backend recorded about itself — the first place to look when something on a client failed and you want to know whether the server saw it.

The Dashboard

The landing page. On your node one panel on it works and the rest do not.

Recent Activity is real: the eight most recent recorded actions, each linking to the account that performed it, with View all going to the audit log. The Users, Vaults and Function Logs quick links at the bottom are real too.

The four cards across the top — Active Promos, Affiliates, Campaigns and Kill Switches — and the Marketing Snapshot panel all read from areas your role cannot reach. They will sit at zero or empty, and the Entitlements quick link goes to a page that tells you the area is managed centrally. Nothing is wrong with your node.

The tc Manual

Help → tc Manual renders the operator manual inside the console. The manual is not bundled in the node distribution, so on your box the page reads The operator manual is not bundled in this distribution. Use these pages and tc-operator --help instead.

Diagnostics

There is a diagnostics page at /diagnostics on the admin host, headed Environment Diagnostics. It tells you what backend the console you are looking at is connected to, and which step of the resolution decided it. It is behind the admin sign-in, because what it prints is a fingerprint of your deployment.

Reach for it when you are not certain which backend a console is talking to.

Your Own Account

Two rows at the bottom of the sidebar, below the navigation.

Your display name sits above them with a pencil beside it. Click it to edit in place; Enter saves and Escape cancels.

Account is the password screen — see Signing in. Sign Out ends your admin session.