Message display stays original
MLV is not translated in v0. Hunt can find the message; it does not rewrite the row.
Sublime Security · Organization capability
Multilingualv0 auto-translate
In progressI designed auto-translate as an organization setting that Hunt, Rules, and Automations can honor, without pretending the product already speaks every language.
Job to be done
One org gate. Downstream surfaces know what “on” means. Hunt can match other languages; the results stay original.
Product principleThe account setting is the source of truth. Everything else follows or stays off.
- My role
- Lead Product Designer
- Status
- v0 · in progress
- Team
- Product, engineering
- Scope
- Account, Hunt, Rules, Automations
01 · The gap
English-only matching in a multilingual inbox.
Customers hunt and write rules in English. The mail they care about is not always English. A query that only hits the original string misses the messages that matter.
The first useful version is not a translation product. It is a shared capability: the organization can opt in, and the surfaces that search or compile already know how to use it.
Account setting as the gate
Auto-translate is shown on. The setting starts off; enabling it makes translation available to Hunt, Rules, and Automations.02 · The decision
One setting. Four surfaces that agree.
I did not want Hunt, Rules, and Automations to grow three different definitions of translated. The account page owns the decision.
01
Account is the gate
Auto-translate lives on the organization. When it is off, Hunt, Rules, and Automations show the control, but it is disabled and points back here.
02
Hunt can match, not rewrite
A query like “verify your account” can hit Japanese and French messages. The results table still shows the original subjects. That is intentional.
03
Rules and Automations know what on means
The create-modal toggles sit next to Activate immediately and Triggers. Downstream surfaces do not invent their own source of truth.
03 · The surfaces
One decision, carried through the workflow.
Each surface makes the organization setting understandable where analysts do their work. These are the behaviors defined in the v0 design.
01
Hunt results stay original
With Auto-translate on, Japanese and French messages can match an English query. The subject column stays in the original language.
02
Hunt detail explains the hit
An Auto-translation: enabled label explains why a non-English message matched, without changing the message itself.
03
Rule editor toggle
The translation control sits beside Activate immediately in the creation dialog. Its availability follows the account setting.
04
Automations toggle
Translation sits beside Triggers during creation and Run on excluded messages in the detail view. Changing it shows a short recompilation state.
04 · What's honest
A v0 capability, not a ship trophy.
This is the locked UX plan, now a working prototype. I am not treating it as a finished launch.
V1 is a different product
MDV original ↔ English, Search, Feeds, Exclusions, and matched-on-translated badges are out of scope here.
What I would carry forward
Let one setting decide. Do not let every surface invent its own language policy.