Skip to Content

Sharing

Collections can be shared with people inside or outside your org by email. Recipients get a tokenized link they can open from any device, and you can change or revoke their access at any time.

When to share

  • View-only — sending a pitch list to a client for review.
  • Edit — collaborating on a plan with a colleague at another agency.
  • Internal — sharing a research collection across departments without granting full org membership.

Opening the share modal

Open the collection, then either:

  • Click Share in the header, or
  • Right-click the collection in the sidebar → Share, or
  • Spotlight (⌘K) → “Share <collection name>”.

Sending a share

  1. Add recipients — type one or more email addresses into the tags input. Validation happens per-tag; invalid entries are rejected before sending.
  2. Choose permission:
    • View — recipient can browse the collection and its shows, copy data out, but can’t edit cells, add/remove shows, or rename the collection.
    • Edit — recipient can do everything an owner can except delete the collection itself.
  3. Optional message — short note included in the share email.
  4. Click Send.

Catalog generates a unique share row per (collection, email) pair. Each row carries its own token used in the URL.

What recipients see

Recipients receive an email with a link of the form https://catalog.frequency.media/shared/{share-token}.

Clicking the link:

  1. Sends them to sign in if they’re not already.
  2. Resolves the token to the share + collection.
  3. Opens the collection in their own session, respecting their permission level.

Pending shares

If you share with an email address that doesn’t have a Frequency account yet, the share is held in a pending state. When that user signs up later — using the same email — the pending share auto-resolves and the collection appears under their Shared with me.

This works even if the user signs up months later; pending shares don’t expire by default.

Managing existing shares

The Share modal lists every active recipient under “Shared with”:

  • Avatar + email + relative timestamp (“shared 2 days ago”)
  • Permission selector (view ↔ edit) — change in place.
  • Trash icon to revoke.

Revoking is immediate — the token becomes invalid and the recipient sees an “unavailable” screen on next attempt.

Finding what’s shared with you

  • Sidebar → Shared section lists collections shared with your email.
  • /browse/shared is a full page with artwork-mosaic cards for each shared collection.
  • /shared/<token> opens a specific shared collection (this is what the link does).

Edit-share specifics

A recipient with edit permission can:

  • Add and remove shows
  • Reorder shows within the collection
  • Rename the collection and edit the description
  • Edit show fields (subject to RLS on the underlying shows — typically that requires being in the same org)

They cannot:

  • Re-share the collection
  • Delete the collection
  • Change anyone else’s share permission
  • See or change other recipients in the Share modal

Permission cheat sheet

CapabilityOwner / adminEdit shareView share
Open collection
Copy data out (CSV / clipboard)
View insights
Add / remove shows
Reorder shows
Rename / edit description
Inline-edit show cells✓ *
Re-share / change other recipients
Delete the collection
* subject to the recipient’s own access to the underlying shows.

Edge cases & gotchas

  • Email mismatch on signup — if a recipient signs up with a different email than the share was sent to, the pending share won’t resolve. Re-issue the share to their actual address.
  • Revoke takes effect immediately but already-loaded sessions may keep working until the next request. The session-stale-detection effect catches this within a few seconds.
  • Sharing a collection in a workspace you’ve left — admins can re-assign ownership before you go. If you’re removed from the org but still own collections, an admin can transfer them.
  • Public links — there is no public/no-login share link. Every share requires a Frequency account.
  • One token per (collection, email) pair — sharing the same collection with the same email twice updates the existing share rather than creating a second token.
Last updated on