Use case
Every mail an account sends carries the name from one of its JMAP identities. The WebUI doesn’t show them: on the account page an admin sees the Full Name, addresses and settings, but not the names the account actually sends under. Display names are free-form (Syncing mail identities from AD/LDAP to Stalwart wide), so a user can send under any name, and the organisation whose domain the mail comes from doesn’t see it until a recipient complains. Today an admin can only look by signing in as each user (master-user sign-in) or by calling JMAP with the user’s accountId, one account at a time.
How it would behave
The account page in the WebUI gets an Identities section that lists every identity of the account with its name, address, Reply-To, Bcc and signature. The admin can change them there and add or remove identities, with the same rules as Identity/set (the address has to belong to the account or one of its groups).
Who benefits
Every organisation where the admin, not the user, manages the accounts, which is the usual case: one account with one identity. It also makes visible what Custom name in From when I use aliases describes (an alias signing with the owner’s name), and it gives admins a way to correct names after a Full Name change, see .