Sharing and embedding
A link shows one published report and nothing around it. Revoke it and it stops working on the next request. Embed it in a page of your own if you would rather.
A link, not an account
A share link shows one published report and nothing around it. No navigation into the rest of your project, no sign-in wall, no account for the recipient to forget the password to. The people who most need to see a number are usually the least willing to create a login for it.
Revoking actually revokes
Revoke a link and it stops working on the next request, not at the end of a cache window. Rotate one instead if you want the same report at a new address, which is the honest fix when a URL has been forwarded further than you meant.
Embedding in your own pages
The same report can be embedded in a page of your own, so a client portal or an internal wiki can carry the live chart rather than a screenshot somebody took in March.
You can see whether it was read
Views are recorded against the link, so you know whether the weekly report anybody asked for is being opened. It is a small thing that settles a lot of arguments about what to keep producing.
Share a report this afternoon
Every plan includes share links. The free plan carries one, which is enough to find out whether the person you are sending it to actually opens it.
Start free