Share a document as an email, in your own name

Sending a document used to mean sending a PDF. The node menu's send entry exported the page to a file, attached it, and put a one-line note in the message — so the recipient got an attachment to open rather than something to read, and the copy-and-paste alternative lost the parts of the page that matter most.

Share ⇒ as email now puts the document in the message. Open it from the node menu, next to Export to PDF and Export to DOCX, pick a contact or type an address, and the page arrives as the email itself. The PDF attachment is still there as an option when a file is what you actually want.

It comes from you

Sharing is a personal act, so the message goes out from your own mailbox, using the same Microsoft 365 connection your personal assistant uses. The recipient sees you, replies come straight back to you, and the message is in your own Sent Items where you would look for it.

If you have not connected Microsoft 365 yet, the dialog says so and offers to connect — it will not quietly send a client-facing document from a generic portal address. Sending from the shared mailbox stays available as a deliberate choice, and then replies are still addressed to you.

Embedded views now survive the trip

The important part is what stops going missing. A page can embed a live view — a grid of link-preview cards, a catalog, a table pulled from the mesh — and until now every export dropped it. The PDF and DOCX pipelines never understood the embed syntax, so an embedded view was printed as its own raw source text; the print-to-browser path emitted the empty placeholder a browser would have filled and printed a blank space.

Emailing a document resolves those views on the server and writes them into the message as real content. A card grid arrives as cards, with their titles, descriptions and links intact.

Built for mail clients, not browsers

Outlook on Windows draws email through Word, which quietly ignores much of what a page relies on. The document is rewritten for that reality:

Reconnecting…
The server was updated. Reloading the page to pick up the latest version.