My architect can't open the share link

02What you're seeing

You sent your architect (or another collaborator) a share link to one of your plans. They tap it, and instead of the plan they see a screen that says "This link is no longer available" — or they enter their email and the magic link they're meant to receive never arrives.

03Most likely cause

The link expired, or you (or another project member) revoked it.

Hemma deliberately shows the same generic "link is no longer available" screen for every failure reason — expired, revoked, invalid token. Not telling the visitor why keeps the link safer if it's been forwarded somewhere it shouldn't be. The reason is in the sharing centre, not the visitor's browser.

The fix: Open the plan in Hemma, open the sharing centre. Find the row for that recipient.

• If the status is Expired — the expiry timestamp ran out. Use the Extend action to give it 7, 30 days, or never. The recipient's existing link starts working again immediately.
• If the status is Revoked — someone cut access on purpose. Confirm with the rest of the project before re-sharing. If you do want them back in, generate a fresh share via the share form.

04Other things to check

• The recipient is signing in with the wrong email. Each share is bound to the email address you invited. If your architect has two addresses (a personal and an office one) and they're confirming with the wrong one, Hemma silently blocks the visit and the magic-link verification appears to "do nothing". Confirm which address you sent the invite to via the sharing centre, and ask them to use exactly that address.

• The magic link email never arrived. Hemma sends a magic link every time the recipient confirms their email on the share landing page. Common causes:

  • Junk / spam folder. Always check before assuming it didn't send.
  • Corporate filter. Some architecture firms aggressively filter outside emails. Ask if there's a personal address that works better, or have IT allow gethemma.app.
  • Rate limit. Hemma caps magic-link requests per recipient (5 per hour) and per IP (30 per hour). If your architect tapped the link many times in a row, they will be temporarily blocked. Ask them to wait an hour.

• They tapped the link before you finished setting it up. If they were extremely quick — opened the email before the share was fully created on Hemma's side — they may see "link is no longer available" on the first try. This is rare, but a single retry usually fixes it.

• Browser blocking cookies or third-party scripts. Hemma's magic-link sign-in needs cookies on gethemma.app. Strict privacy modes (Brave Shields, Safari Lockdown, certain Firefox containers) sometimes block them. Ask them to try in a regular browser window, or whitelist gethemma.app.

• They opened the link on a device that's already signed into someone else's Hemma account. If a project member of yours opens an architect's share link on their own laptop, Hemma sees an authenticated session that doesn't match the invited email and silently denies access. The fix: open the share link in a private window, or sign out of the existing Hemma session first.

• The link was forwarded. If the recipient forwarded the email to a colleague, the colleague will see the email-confirmation screen, enter the colleague's email, and get nowhere — because the share is bound to the original recipient's address. This is working as intended; the original recipient needs to open it themselves.

• The plan or the project was deleted. If you (or another project member) deleted the plan after sharing it, the link points at nothing and shows the same "unavailable" screen. The sharing centre will not list the share at all in this case.

05If none of this worked

If you've walked the list and the recipient still cannot get in, email hello@gethemma.app with:

• The plan name and the recipient's email address.
• The exact wording of the screen they're seeing.
• A screenshot if possible.
• Roughly when they tried (so we can match it to the audit log).

Every share has an audit trail on our side that records the precise reason every visit succeeded or failed (expired token, email mismatch, rate limit, etc.). We can tell you in a sentence what happened.

06Related

• Sharing a plan with your architect
• Managing share links — expiry, revoke, history
• What the recipient of a share link can see