Receiving Email

Every matter, task, and trust transaction in Laminar has its own email address. Forward an email to it, or copy the address into Cc when you write to a client, and the message files itself onto the right entity: attachments included, threaded with the rest of the conversation.

This is the end of “the email is in someone’s inbox.” The file holds its own correspondence.

The Addresses

The pattern is the entity’s ID at Laminar’s mail domain:

• Matter M-42: m42@app.laminar.so
• Task T-107: t107@app.laminar.so
• Trust transaction TT-9: tt9@app.laminar.so

You don’t need to memorize this. Every matter summary, task, and trust transaction has a Copy inbound email address button (the @ icon) that puts the address on your clipboard. If you belong to more than one firm, the copied address includes your firm’s identifier (like m42.your-firm@app.laminar.so) so the email can never file to the wrong organization; use that form.

Ways to File Email

Forward it. Received something relevant in your own inbox? Forward it to the entity address. Laminar detects the forward and files the original message: original sender, original date, forwarding cruft stripped.

Bcc Laminar when you send. Writing to the client from your own mail client? Add the entity address in Bcc. Laminar files it as outbound correspondence, with the real recipients recorded.

Let replies file themselves. When someone replies to an email you sent from Laminar, the reply routes back to the conversation and threads under the original automatically.

Duplicates are handled: if the same email reaches an entity twice (say, forwarded by two people), Laminar keeps one copy and quietly drops the rest.

Who Can File Email

Inbound mail is only accepted from the work email address of an active user in your firm. This is a security boundary, not a bug:

• Sending from a personal or unrecognized address gets a bounce asking you to forward from your work email.
• A deactivated account’s mail bounces with “your account isn’t active.”
• Mail that fails sender authentication (DMARC) is dropped silently, with no bounce, so spoofed addresses learn nothing.

If an address is mistyped or the entity number doesn’t exist, the bounce says so and shows the correct format. Bounces always quote your original message so nothing is lost.

Tips

Copy the address into the matter’s kickoff email. If the whole conversation starts with the entity address in Cc, every reply in the chain files itself for free.

Attachments travel with the email. Files arriving by email are stored with the interaction; open it in the feed to preview or download them. If a document should also live in the matter’s files, upload it to Assets, which additionally runs PDFs through automatic data extraction.

Nothing is ever lost. Even mail that can’t be routed is stored and recoverable by an administrator. When in doubt, forward it; the worst case is a helpful bounce.