Collections

Scale your team’s best thinking

Share a Capture with your whole team in one click, and Scuba organizes it and puts it in your teammates’ daily briefings. When a project or a research area deserves its own space, curate a shared Collection. One person’s insight becomes the whole team’s edge.

Start one on your own in about two minutes. Add your team when you’re ready.

One click to your whole team
Share any Capture with everyone. Scuba puts it in their briefings later that day.
Or a Collection you curate
Give a project or a research area its own shared space. Scuba suggests what belongs in it.
Share it across teams
Bring in another team, a customer, or a partner by email. They see only that Collection.
Scuba brings it into your AI tools
Claude, ChatGPT, Cursor, and Slack start from what your team shared. You stop pasting the background into every chat.

A Collection keeps everyone on a project in sync and moving in the same direction

Collections give your team a shared space to go deep on an area or move a project forward. An area could be AI agents, a new market, or customer research. A project could be a product launch, a fundraising round, or a website redesign.

Ask the Collection. It answers like an agent built for your project.

Start a session on a Collection and ask what you’d otherwise ask in a meeting. The answer is grounded in everything your team put there, and it cites each Capture it used.

  • Get feedback. Pressure-test a plan against what the team already decided.
  • Draft the spec, the proposal, or the customer follow-up from it. You edit instead of starting from scratch.
  • Have a coding agent work a PR from it. Scuba brings the Collection into Claude, ChatGPT, Cursor, and Slack.
  • It powers your daily briefing, which recaps what changed in your Collections.

A session is yours. Teammates don’t see it unless you share a response.

A session on the Atlas launch Collection answers what is still open before shipping. It cites an eng plan saved from Claude, a Slack thread, and Kelly’s voice debrief.
what’s still open before we ship Atlas?
Scuba read 42 Captures in Atlas launch

Two things.

  • The sales deck still promises offline mode. The eng plan cut it. Dolapo is pulling it from the deck today.
  • The pricing page still shows one price. Finance signed off on two tiers on Tuesday.
Eng plan: Atlas syncClaude · Tian · 2d
#atlas-launch: do we hold for offline mode?Slack · 14 replies · 1d
Pricing debrief: finance signed off on two tiersVoice note · Kelly · Today

Comments, @mentions, and reactions sit on the Capture itself

Comment on any Capture your team shares. Type @ to bring a teammate in, and they’re notified right away. Add a reaction when 👍 says enough. Scuba also writes each person the takeaways for their role.

A Capture of a Claude answer comparing three ways to ship offline mode. Scuba wrote Dolapo her own takeaway from it. In the comments, Dolapo mentions Tian, Tian replies, and teammates add reactions.
Offline mode: three options and what each costs
Claude compared three ways to ship offline mode. A read-only cache takes a week. Full two-way sync takes three and would move the launch.
Claude
2
1h
For DolapoDon’t promise two-way sync in the sales deck.
Dolapo2m

@Tian can the read-only cache ship by March 12?

Tiannow

Yes. It’s a week of work.

32

Share with your whole team in one click. Scuba sorts it from there.

One good link doesn’t need a Collection. Share it with everyone, and Scuba puts it in their briefings later that day. When a Capture fits a Collection, Scuba suggests it and one click adds it. Filing is optional.

Brian shares a captured competitor pricing page with his whole team in one click. Scuba suggests the Atlas launch Collection for it, and one more click would add it.
Brightside pricing: plans and add-ons
Brightside sells two tiers and charges extra for offline access. Their top tier is priced just under the Atlas team plan.
brightside.co
2m
Shared with everyone
Atlas launchScuba suggests this CollectionAdd

A Capture stays private until you share it. Nothing joins a shared Collection until you say so.

The summary rewrites itself when someone adds a Capture

Every Collection has a running summary at the top. Each line points to the Capture it came from. No manual edits required.

The running summary of the Atlas launch Collection. Each of its four sentences cites the Capture it came from: an eng plan saved from Claude, Kelly’s voice note, a Slack thread, and a ChatGPT research answer.
Atlas launchUpdated just now
Summary of 42 Captures

Launch is March 12. Sync is built and in testing. Eng plan: Atlas sync

Pricing is settled at two tiers. Finance signed off on Tuesday. Pricing debrief

The team is split on holding the launch for offline mode. #atlas-launch

Brightside charges extra for offline access, so it’s a real gap. Competitor pricing research

Rewritten when Kelly added her debrief

Share a Collection with the people doing the work

A launch team, an account team, or a hiring loop each gets its own Collection. Share it with your whole team or a few people. Editors add and remove Captures. Viewers read.

The Atlas launch Collection is shared inside one company: everyone at Northfield can view it, and Kelly and Tian, who are on the launch team, can edit it.
🚀 Atlas launch
+39
Launch is March 12. Sync is done. Pricing is settled: two tiers, and finance signed off on Tuesday.
42 Captures
2h
Shared with
KellyEditorTianEditorNEveryone at NorthfieldViewer

Only the people you add can open a Collection. Scuba shows who’s in it before you add a Capture.

Share it across teams, or with a customer or a partner

When the work crosses a boundary, add people on another team or at another company by email. A guest sees that one Collection and nothing else of yours.

  • You choose whether each guest can edit or only view.
  • Anyone not on Scuba yet gets an invite. They don’t need a Google account.

A Collection can’t be shared by public link. Everyone in it has signed in.

The Website redesign Collection is shared with Pedro on another team as an editor, and with a guest at the design agency as a viewer. A note says the guest sees only this Collection.
🖥️ Website redesign
+20
The new homepage is in its second round. The agency’s three concepts are in, and the team prefers the one that leads with customer quotes.
23 Captures
1h
Pedro · Another teamEditorSsam@lumenstudio.co · Outside NorthfieldViewer
Sam sees only this Collection

A channel, a wiki, and a weekly meeting keep a project in sync the slow way. A Collection gives your team something to work from.

Today

  • The project channel is messy coordination. The decision scrolled away.
  • The wiki page is out of date the day after it’s written.
  • The meeting that catches everyone up is slow and expensive.

With Scuba

  • Ask the Collection in a session. The answer comes from everything the team put there.
  • Get feedback on a plan, draft the update, or hand a PR to a coding agent. Scuba brings the Collection into Claude, ChatGPT, and Cursor.
  • Your daily briefing recaps what changed, so the meeting can be about the decision.

Start it alone. It gets better with every person you add.

A Collection works with only you in it. Most of its value shows up once your team is there.

  1. First two minutes

    Start one for the project on your mind

    Name it after a launch or a customer. The collection builder fills it from a web search or from what you’ve already captured. You have a summary before you’ve written anything.

  2. First week

    Bring in the people on the project

    Share it with the few people doing the work. Each Capture someone adds reaches the rest as takeaways.

  3. First month

    What you learn starts to compound

    Scuba connects related Captures across Collections, so an insight from one project or research area shows up in the next. Your briefing and your sessions draw on all of them.

How teams use shared Collections

Our own team runs complex projects with under two hours of meetings a week. The specs, eng plans, and discussions live in shared Collections.

Run a shared project in one place

Sebastian adds the research readout. Design, engineering, and support each get their own takeaways. The debate about step three happens on the readout.

Sebastian adds a research readout to the shared Onboarding redesign Collection. It is summarized with six comments on it, and Adam asks Pedro a question in a comment.
🧭 Onboarding redesign
+25
Four of six new users stall at step three, the calendar permission. The team is testing a version that asks for it later.
28 Captures
just now
Sebastian added this
Research readout: where new users stall
Four of six people stopped at the calendar permission. They didn’t know yet why Atlas needed it. Two said they’d have continued if asked later.
Google Docs
6
just now
Adamnow

@Pedro can we ask for the calendar later?

You decide who’s in

Sharing is always a deliberate choice.

  • Yours until you share it

    A new Collection is visible only to you. It stays that way until you add people or your team.

  • You choose who edits and who reads

    Editors can add and remove Captures. Viewers can only read. You can see and change who has access at any time.

  • You see who’s there first

    Scuba shows who a Collection is shared with before you add a Capture to it.

  • Only people you add get in

    A Collection can’t be shared by public link. Only single Captures and session responses can, and those links are off by default.

Read how Scuba handles security and privacy

In their words

The details

For the person, or the agent, checking the specifics.

What a Collection is
A named, shared set of Captures with a running summary and its own sharing settings. A Capture can be in more than one.
Who you can share with
Paste up to 50 email addresses at once. People at other companies don’t need a Google account.
Discussion
Comments, reactions, and @mentions work on Mac, web, iPhone, and Android.
Staying in the loop
Collection recaps in your daily briefing. Mute any Collection’s emails and push notifications.
Read how Scuba handles security and privacy

Questions people ask

The ones we hear most, answered straight.

Security and privacy

I already use Claude or ChatGPT. What does this add?

A shared place for the project that outlasts the chat. Paste a spec into Claude and it helps you, for that one conversation. A Collection keeps the spec, the Slack thread, and the call debrief together for the whole team.

You keep the tools you have. Connect Claude, ChatGPT, or Cursor and Scuba brings the Collection into them, so you stop pasting the background in. They can add to it too.

Can I use a Collection on my own?

Yes. A Collection with only you in it still gets a running summary, and you can ask about it in a session. Plenty of people keep one for their own research or a project they haven’t shared yet.

It’s built for a team, though. Takeaways for each person, comments, and @mentions only show up once other people are in it.

We have a wiki, a shared drive, and Slack. Isn’t this one more thing to keep current?

No, because nobody has to keep it current. A wiki page needs an author. A status doc needs someone to rewrite it every week. A Collection fills up as people capture what they’re already looking at, and Scuba writes the summary.

It sits alongside those tools. The doc stays in Google Docs and the thread stays in Slack. The trade-off: you can’t edit a Collection like a wiki page. You change the summary by adding or removing Captures.

Do I have to file everything into a Collection?

No. Search finds a Capture whether you filed it or not, and you can share one with your whole team in one click. Collections are for when a project or a research area deserves its own space.

If I add something to a shared Collection, who can see it?

Everyone that Collection is shared with, and no one else. Scuba shows you who that is before you add the Capture. Your other Captures stay private.

One thing to know: they can read the Capture even without access to the original doc. A Capture is Scuba’s saved copy of what you could see, and everyone in the Collection can read that copy. Check who’s in a Collection before you add a restricted doc to it.

Can other teams, or people outside my company, join?

Yes to both. Share a Collection with people on another team, or with a vendor or a customer at another company, by email address. They see that Collection and nothing else of yours.

Anyone not on Scuba yet gets an invite. They don’t need a Google account. A Collection can’t be opened by a public link, so everyone in it has signed in.

How does a Collection stay current when things change?

The summary rewrites itself each time a Capture is added. Capturing a page again updates the Capture you have. Saved Google Docs refresh when you revisit them, if they changed.

Scuba doesn’t mark a Capture as approved or out of date. That call stays with your team. An editor can remove what no longer applies, and the summary is built from what’s left.

How many people should we start with?

A small group works best: around five to eight people on one or two messy projects. Pick a big launch, a key customer, or a research area you keep coming back to.

Skip the backfill of everything you’ve ever written. Add more people once those Collections are useful.

Will a busy Collection fill my inbox?

Only if you let it. You’re notified when a teammate adds or shares something, with the takeaways for your role, and right away when someone @mentions you. Your daily briefing recaps your Collections too.

You can mute any Collection. Muting stops that Collection’s emails and push notifications. You stay in the Collection and can still open it anytime, on Mac, web, iPhone, or Android.