Sharing a preview
MaShop has no private preview link. What the Share window really copies, when it works, and who can open the address you send.
Sharing
MaShop has no private preview link, and no read only link to a project in progress. The only address you can hand to someone outside the project is your live site.
What the Share window copies
The Share button, at the top of the workspace, opens a window in two halves. The left half invites people by email. The right half is labelled Lien public, the public link, with a Copier button next to it.
That button copies the address of your live site, and only once the site is genuinely online. Before that it copies an address on the workspace domain, under /p/, followed by your project identifier. No page answers there. Whoever receives it gets a 404.
The strip along the bottom reads Lien prive and Expire dans 7 j. Both belong to the email invitation on the left, not to the link. A live site address does not expire.
Publish before you share
Sharing anything means publishing first. Publishing creates your Supabase database, your GitHub repository and two Netlify sites, on your own accounts.
The first publish requires a Pro or Max plan and debits no credits. A free account is refused. Later updates cost nothing either, and each build runs on your own Netlify account. The full sequence, its quotas and its failures are covered in Going live.
Who can open what
| What you hand over | Who can open it | How long it lives |
|---|---|---|
| Your live site address | Anyone who has it | As long as the site exists |
| Your back office address | Only someone with a sign in on that back office | As long as the site exists |
| An email invitation | Only the exact address you invited | 7 days |
| A link to your MaShop workspace | Only the account that owns the project | Not applicable |
Publishing puts no password on the public site. Treat the address as public the moment you send it, and assume it will be forwarded.
Your back office is a separate site
One repository produces two Netlify sites. One carries your public site. The other carries your back office, at the same name with admin appended. Sending the first address grants nothing on the second. The back office sends a visitor without a session to its own sign in page.
Showing work in progress
The workspace preview is not shareable. It sits behind your MaShop sign in, and the project screen opens only for the account that owns the project. Inviting someone as a Viewer puts them on the member list, but read Inviting people to a project before you rely on it.
Until that lifts, the practical way to show work in progress is to publish an update and send the site address.
If the copied link answers 404
Three checks, in order.
- Has the project ever been published? If the button still reads Publish, the answer is no.
- Is the site confirmed online? The window switches to your real address only once the build is finished and the address answers.
- Did that first publish finish while the workspace was open? The address is read when the workspace loads, and a later publish does not rewrite it. Reload the page, then copy again.
One more thing before you send a link. Renaming the project identifier can move the address, and a custom domain replaces it altogether. Both are covered in Going live, and both leave anyone holding the old address pointing nowhere. Resend the link after either one.