Sharing a brief with a client.

A read-only public page for one brief — no login needed, never indexed. Four things will bite you if nobody tells you: links never expire, every click makes a new one, closing the dialog loses your only revoke button, and deleting the brief is the one thing that kills them all.

A share link turns an archived brief into a public read-only web page. No login, no seat, no ScoutRival account — you send a URL and your client reads the brief. It's the cleanest proof-of-work artefact the product has, and it has four sharp edges worth knowing before you send one.

Making a link

1

Open Share

The Share button on an open brief, or Share link in the menu on any archive row.

2

Create public link

One button. It mints a token and shows you the URL immediately.

3

Copy it — before you close the dialog

Hit Copy and paste it somewhere you'll still have it tomorrow. This step is not optional; see the gotchas.

The URL looks like this:

share link// the token IS the permission — anyone holding it can read the brief
https://user.scoutrival.com/b/{token}

What the recipient sees

A clean, branded, read-only page — the same document as the HTML export: the verdict, what your rivals did, and the posts and blog the brief drafted. Your brand's name at the top, a ScoutRival credit at the bottom.

  • No login and no account. It opens on a phone, in a client's browser, anywhere.
  • Read-only. There is nothing on the page to click, edit or run — no scripts at all.
  • Not indexed. The page tells search engines not to index or follow it, so a shared brief won't turn up in Google.
  • Dismissed suggestions are excluded — prune the brief first and the client only sees the drafts you stand behind.
  • Only that one brief. A link exposes one day. It is not a door into your archive, your other brands, or your account.

Four things to know before you send one

// 1 · LINKS NEVER EXPIRE

There is no expiry date and no time limit. A link you sent a client eighteen months ago still opens the brief today. The only thing that closes it is revoking it — or deleting the brief.

// 2 · EVERY CLICK MINTS A NEW LINK

Pressing Create public link a second time doesn't show you the first link again — it creates a brand-new one. The old token stays live. Click it five times and that brief now has five working public URLs, all of which you have to revoke separately.

// 3 · CLOSE THE DIALOG AND THE TOKEN IS GONE FROM THE UI

The Revoke this link button only revokes the token currently on screen. There is no list of a brief's live links anywhere in the app. Close the dialog without copying the URL and that link keeps working forever with no way to revoke it from the interface. Copy first, close second.

// 4 · IT'S COMPETITIVE INTELLIGENCE

The page carries your verdict, your rivals' activity and your unpublished drafts. Anyone with the URL can read all of it. Treat the link like a password — don't put it anywhere public, and don't post it in a channel your competitor sits in.

Revoking a link

While the share dialog is still open, Revoke this link kills the token you just made. The public page then shows “This brief isn't available” instead of the brief.

Revocation takes effect at our end immediately, but the public page is cached for up to five minutes. Someone who loaded it seconds before you revoked may still see a cached copy for a few minutes. Plan on five minutes, not five seconds.

Killing every link at once

If you've lost track of how many links a brief has — the “every click mints a new one” problem — there's one clean way out:

// DELETE THE BRIEF

Deleting the brief kills every share link that points at it. The token can't resolve to anything, so every one of them 404s at once. Export it first if you want to keep a copy — deleting is permanent. What else the delete removes →

Embedding it

The page is allowed to be framed, so you can drop it into a client portal, a Notion page or an internal dashboard with an iframe and it will render. Same caveats apply — anyone who can see the frame can see the brief, and can lift the URL out of it.

Still stuck?
Contact support