From nothing to a protected inbox

The onboarding page shows the code as soon as the account exists. Afterwards it lives in the dashboard under Settings, in the Organization code card, with a copy button next to it.

It reads BLD- followed by the code, and it is visible to owners and admins only. Treat it as a credential: anything holding it can submit and read scan traffic for your organization. Regenerating it unlinks every install you have already set up.

Build the extension, open chrome://extensions, turn on Developer mode, choose Load unpacked, and select frontend/packages/extension/dist. Then click the Blade toolbar icon, paste the organization code under Organization code, and press Link.

Chrome 120 or newer. The manifest is generated at build time, so build before loading: VITE_BACKEND_URL=http://localhost:8000 pnpm --filter @bladedlp/extension build. The popup status card changes from Not linked yet to protection on for your organization, which is how you know the link took.

Open Approved domains and add a row for each domain that matters, with a direction of sender, recipient, or both, and a classification of internal, partner, or blocked. Recipient classification is what the policy rules react to.

The field accepts a full email address as well as a bare domain. Add the address you send from as a sender row classified internal, or every message carrying a detection is blocked by the unapproved sender rule before the rest of the policy is reached.

Send a message with patient identifiers from the linked account. The same body gets three different answers: allowed to a recipient on your internal or partner list, held for review when it is high risk to a personal mailbox, and refused outright to a domain you classified as blocked.

Held messages wait in Quarantine until someone approves or rejects them, and the sending tab picks the decision up within a few seconds. Every scan shows up on the dashboard overview under Recent events, with its action and where it happened, and in the audit log.