Stephen Turner
Akash Kumar
Jordan Lee
Taylor Scott
Share a project's meeting history without sending ten links
When someone joins a project or a client asks for the history, sending meeting links one by one doesn't scale. Group the related meetings into one shared collection, give each person the access they need, and keep adding meetings as they happen. Decide up front which meetings belong there and which stay private.
When a shared collection beats sharing one meeting
Share a single meeting when one person needs one recap. Share a collection when people need the thread across many meetings: a new teammate catching up, a manager following a client account, or a partner on a long project.
A collection also stays current. New meetings appear for everyone with access, and you don't send another link.
Decide what belongs, before you add anything
Write a one-line rule for the collection, such as "every meeting about the Acme rollout, including internal prep." Then decide what stays out.
Access to a collection usually means access to every meeting in it. So keep out anything only some viewers should see: pricing debates, performance conversations or a frank internal retro. Share those meetings one by one instead.
Give each person the role they need
Match access to what each person will do. Someone who should read along needs less than someone who files meetings or invites others.
Teammates who maintain the collection can add meetings. A client contact usually only needs to read.
Doing this with spaces in Bridge
In Bridge, a space is a shared collection of meetings. Choose Add Space in the sidebar, name it and pick an emoji. Then open each completed meeting and use Add to Space.
To share, open the space and click Share. You can invite people by email, share with a workspace group (Business and Enterprise plans) or open it to the whole workspace. Inviting collaborators needs a paid plan.
| Role | Can do | Good for |
|---|---|---|
| Owner | View meetings, use the Space Assistant, add or remove meetings, manage sharing | The person who maintains the space |
| Member | View meetings, use the Space Assistant, add or remove meetings | Teammates who file their own meetings |
| Guest | View meetings only | Clients, partners and anyone who just reads |
Access rules worth knowing
- Everyone with access to the space can open every meeting in it.
- Everyone you invite needs a Bridge account to open the space. People outside your workspace join as Guests.
- Space Assistant chats are private to each person, and Guests can't use the Assistant.
- Someone who is a Guest on a meeting but an Owner of its space gets Owner rights while the meeting stays in that space.
- Deleting a space removes the grouping and its shared access, not the meetings.
Example: onboarding a new account manager
A new account manager takes over a client (fictional example). Their lead, who owns the space, adds them as a Member of the client's space, which already holds the kickoff, three check-ins and the last renewal call.
On day one, they ask the Space Assistant what the team promised this client in the last two months. They also ask what's still open. Then they check each answer against the meeting it came from before their first call.
Keep the collection worth opening
Add meetings right after they end, while you know where they belong. Check the member list each quarter, and remove people who've left the project.
When the project ends, decide whether to keep the space for reference or delete it. Deleting it doesn't delete the meetings.