jcoffey-dev
0054b8a3ce
Administration used to open on its first section. It opens on a grid of cards now: users, domains, messages waiting in the delivery queue, server memory, and the last 24 hours' received and sent. Each card is there only when the role holds what its number needs -- a count is a query, the metric history a query and a get -- so a helpdesk role that reads accounts and domains sees those two cards and nothing about the server. What the cards count is whatever Stalwart answers for the signed-in account, which scopes a tenant administrator's accounts, domains and queue to the tenancy. The metric history has no tenant in it, and Stalwart's Tenant Administrator role does not hold it, so a tenant's dashboard is users, domains and pending. The history is Enterprise-only and switched off by default. A server that refuses it leaves those cards off; one that records nothing says so rather than showing zeroes. Received and sent add up the queue counters Stalwart's own dashboard uses, filtered with the comparison names the live server accepts (a bare timestamp is unsupportedFilter). The column count follows the number of cards so rows stay even, and falls back by the grid's own width rather than the window's. The server's test for whether an account is offered Administration matches the client's again, now that a count is enough. The mock answers the queue and an hourly history ending in the current hour; MOCK_METRICS=off refuses the history as Community does, a tenant administrator gets the queue, and helpdesk reads domains, as the demo's does. ROADMAP and FEATURES said reporting and queues were out of scope; they say the dashboard reads a handful of numbers and that managing queues, logs and settings stays out. KNOWN-ISSUES records what was settled on the live server and what was only read from source. Fourteen new strings, in all nine catalogues.
36 lines
1.5 KiB
TypeScript
36 lines
1.5 KiB
TypeScript
import type { ReactNode } from "react";
|
|
import { Redirect } from "wouter";
|
|
import { adminSections, type AdminSection } from "@/lib/adminAccess";
|
|
import { AccountsAdmin } from "./AccountsAdmin";
|
|
import { AdminDashboard } from "./AdminDashboard";
|
|
import { DomainsAdmin } from "./DomainsAdmin";
|
|
import { currentAdminSection } from "./AdminNav";
|
|
import { usePermissions } from "./usePermissions";
|
|
|
|
const RENDER: Record<AdminSection, (id?: string) => ReactNode> = {
|
|
dashboard: () => <AdminDashboard />,
|
|
accounts: (id) => <AccountsAdmin selectedId={id} />,
|
|
domains: (id) => <DomainsAdmin selectedId={id} />,
|
|
};
|
|
|
|
/**
|
|
* Administration: what the signed-in account's Stalwart role lets it manage.
|
|
*
|
|
* The page is only the open section. Its list of sections is in the folder
|
|
* pane (see AdminNav), so the tables here get the width Settings spends on a
|
|
* second column. A bare /admin opens the dashboard, and a section the role
|
|
* cannot read -- typed into the address bar, say -- opens the first one it can.
|
|
*/
|
|
export function AdminView({ section, id }: { section?: string; id?: string }) {
|
|
const allowed = adminSections(usePermissions());
|
|
// A role taken away since the menu was drawn. Stalwart would refuse every
|
|
// call anyway; this spares the page of refusals.
|
|
if (!allowed.length) return <Redirect to="/mail" />;
|
|
const current = currentAdminSection(allowed, section)!;
|
|
return (
|
|
<div className="admin-layout">
|
|
<div className="settings-content admin-content">{RENDER[current](section === current ? id : undefined)}</div>
|
|
</div>
|
|
);
|
|
}
|