Send a share
Send a share link by Gmail, SMS or Slack from the detail pane, and see the preview card a link shows when you paste it into a chat app.
You can send a share link straight from Yardmaster by email, text or Slack, and wherever you paste a link it unfurls into a preview card that never shows your content.
Send a link from Yardmaster#
A collapsible Send to… sub-panel sits inline in the detail pane of a share in Shares.
Expand Send to… and pick Gmail / SMS / Slack from the 3-tile channel picker.
Enter the recipient (email address, phone number in
+15551234567form, or a raw Slack channel ID likeC0123ABCDEF).Add an optional note (Yardmaster appends the share URL after a blank line).
Hit Send.
You'll see a success toast like "Share sent via Gmail," or a failure toast naming the channel's error if the send didn't go through (e.g. channel_not_found from Slack). Revoked, expired, or unpublished shares fail the pre-flight check before any channel call.
Every send (success or failure) writes an audit row to share_send_log tied to that share, so there's always a record of who you sent it to and when.
What does the link preview look like?#
Every share automatically gets a polished link preview when you paste the URL into Slack, Discord, iMessage, Twitter/X, Teams, or any other app that reads OpenGraph metadata.
The preview is a designed 1200×630 card: a near-black field, the YARDMASTER wordmark in the top-left, your share's title set large underneath (up to three lines), a small outlined pill naming the kind of thing it is (Conversation, Web page, Document, PDF, Image, Graphic, Code, Component, Note…), and an indigo rule along the bottom edge.
The card never shows your content. That's deliberate, not a limitation. Slack, iMessage and Discord fetch a preview image anonymously (there's no way for them to log in as you), so anything that route can serve would be readable by anyone who ever saw the link.
The card is therefore built from three harmless pieces of information only: the title you gave the share, the word for what kind of file it is, and whether the link still works. Your actual image, PDF, page or document is never drawn onto it. That's why a password-protected share can safely unfurl at all: there is nothing on the card to leak.
Nothing is stored and nothing is pre-built. The card is drawn fresh each time an app asks for it, and it's explicitly marked "don't cache this." That's what keeps Revoke honest: the moment you revoke a link, the very next preview anyone fetches says the share is gone. There's no stale thumbnail sitting in a bucket that outlives the revoke.
Active: your title, and no second line. The card just looks like a share.
View cap reached: your title, plus the line "View limit reached". The recipient can see what it was and that they're too late.
Password protected: the line "Password protected", and no title and no kind pill. A title can itself be sensitive ("Q3 budget cuts"), so a locked share gives away nothing but the fact that it's locked.
Revoked and Expired, both show exactly the same thing: "This share is no longer available." with no title and no kind pill. They're word-for-word identical on purpose, so a stranger can't tell from the preview whether you pulled the link or it simply timed out.
Never existed: a bad or made-up token gets no card at all, just a plain "not found." Yardmaster won't burn the effort of drawing a picture for a link that was never real.
To show a share inside another page rather than as a link, see Embed a share in another page.
Related
- Text from Yardmaster with your Android phoneConnect an Android phone to read and send your text messages in Yardmaster, through Pushbullet or straight through your phone.
- Read and send email with GmailConnect your Google account to read, answer and tidy your Gmail next to your agents. The same sign-in also connects Calendar, Drive and Sheets.
- Clean up your Gmail inboxEmail Cleanup groups the newsletters, promotions and other bulk mail in your Gmail by sender, so you can archive or unsubscribe a whole group at once.