Each tenant's page carries its legacy protocols switch

jcoffey-dev commented

2026-09-21 20:39:59 +00:00

Owner

A card above the tenant form: whether legacy mail protocols are on or off
for the organization, a one-click "Turn legacy protocols back on", and
"Turn off legacy protocols…", which opens -- before anything can change --
the impact panel with the tenant's own people (LP-15), the statement at
tenant scope and the typed confirmation (LP-16, LP-17). The statement reads
"everyone in {organization}" and names no ports and no firewall: a
tenant's switch closes nothing, other tenants share the ports (LP-13).

It reads and turns inbuxa:TenantProtocolPolicy, with the domain
permissions the server checks for it. It shows on the read-only tenant page
too: a tenant administrator reads its tenant without changing it (MT-12)
and may still turn the switch. Turning it back on while the server has
legacy protocols off is refused by the server, and the refusal is shown.

The banner (LP-18) falls back to the tenant's switch where the server's
can't be read -- inside a tenant -- and reads "off for your
organization".

The impact panel, statement and confirmation move to parts.tsx, shared by
Hardening and the tenant card; the statement takes its scope.

Checked by hand against a local server with a tenant, two of its users and
the admin signed in over IMAP: the tenant card's panel lists the tenant's
two users and not the admin; the statement reads "everyone in Example Co"
with no ports or firewall; turning it off makes the tenant's user get "NO
[ALERT] Your organization allows only INBUXA webmail and JMAP apps" over
IMAP; one click turns it back on; Hardening's panel lists all three. Not
checked by hand: the banner as a tenant administrator sees it.

A card above the tenant form: whether legacy mail protocols are on or off for the organization, a one-click "Turn legacy protocols back on", and "Turn off legacy protocols…", which opens -- before anything can change -- the impact panel with the tenant's own people (LP-15), the statement at tenant scope and the typed confirmation (LP-16, LP-17). The statement reads "everyone in {organization}" and names no ports and no firewall: a tenant's switch closes nothing, other tenants share the ports (LP-13). It reads and turns inbuxa:TenantProtocolPolicy, with the domain permissions the server checks for it. It shows on the read-only tenant page too: a tenant administrator reads its tenant without changing it (MT-12) and may still turn the switch. Turning it back on while the server has legacy protocols off is refused by the server, and the refusal is shown. The banner (LP-18) falls back to the tenant's switch where the server's can't be read -- inside a tenant -- and reads "off for your organization". The impact panel, statement and confirmation move to parts.tsx, shared by Hardening and the tenant card; the statement takes its scope. Checked by hand against a local server with a tenant, two of its users and the admin signed in over IMAP: the tenant card's panel lists the tenant's two users and not the admin; the statement reads "everyone in Example Co" with no ports or firewall; turning it off makes the tenant's user get "NO [ALERT] Your organization allows only INBUXA webmail and JMAP apps" over IMAP; one click turns it back on; Hardening's panel lists all three. Not checked by hand: the banner as a tenant administrator sees it.

jcoffey-dev commented

2026-09-21 20:39:59 +00:00

Author

Owner

assigned to @jcoffey-dev

jcoffey-dev commented

2026-09-21 20:44:09 +00:00

Author

Owner

mentioned in commit 4859607bab

mentioned in commit 4859607bab04269752c14c2305d22201a1140106

jcoffey-dev merged commit 4859607bab into main

2026-09-21 20:44:09 +00:00

Each tenant's page carries its legacy protocols switch #5