Messages

From the contact form. The row is the record and the email is only a notification, so a message is here whether or not the email about it arrived. Relay says which: “no” means the message reached us and the notification did not.

Message

People

Newest activity first, and counts only: how many tools each person has favourited, opened and saved. Never which ones. What is inside a saved calculation is not shown here at all. For which tools get used across everybody, read the Usage tab.

This is where Pro is granted. Select a name, and the panel below carries the control. A Pro user opens any tool marked 'access' => 3 in config/tools.php, which is the level to use for a tool you want a chosen group to see before it is published. An administrator already opens those without the flag, so granting Pro to one is refused rather than recorded.

The selected account

Delete this account

This deletes the account and everything in it, at once and permanently. It is also the only way to end somebody’s access: the allowlist decides who may open an account, not who may sign in, so an account keeps working after its address leaves the list.

Specialities

Accounts

What is stored

A “series” is one patient on one tool for one clinician. The same patient seen by two clinicians counts twice and cannot be matched across them, because each account derives its keys from its own salt. That is the design working, not a counting error.

Most favourited

Most opened

One row per person per tool, not one per visit: opening the same tool twice in a day does not count twice. This is “how many people use it”, not “how busy it is”.

The catalogue

Counted from the registry, not from the database. Restricted means a tool carries an access level below 4, so it is off the public hub and opens only for the levels named against it. Unlisted is the editorial decision, and no level brings one back.

Due for review

Every module is re-checked against its sources at least every 18 months. Listed tools only: a tool still behind a gate is not in front of anybody. Never reviewed comes first, then the longest wait. Stamp one with node tools/review.js <slug> from cdss-dev, and never by hand.

Sign-in email, last 24 hours

This is the part worth checking after a quiet complaint that “the site never emailed me”. Two daily ceilings can stop a code: one on how many are delivered across the whole site, and one on how many go unredeemed to a single address. Neither says anything to the person it stops. A clinician who gets no code sees a form that appeared to work, so this card is the only place either becomes visible.