How a team shares contacts, lists and pipelines

When several people work in the same Swimlane organization, some things are shared by everyone, some belong to each LinkedIn account, and some stay personal. Knowing which is which avoids two reps writing to the same prospect without knowing it.

Shared with the whole team

Contacts. Every contact belongs to the organization. All Leads in Lists shows every contact of the team. A LinkedIn profile exists only once per organization: if two members import the same person, they work on the same contact.
Notes. The Notes field on a contact is a single shared note. Anyone can read and edit it.
Tags. A tag put on a contact is visible to everyone.
Archiving and deleting. Archiving or deleting a contact does it for the whole team.
Lists. Every member sees every list. On a computer, the Owner column shows who created each list. Any member can edit or delete any list.
ICP fit. The fit levels computed for a campaign audience are visible to the team.
A contact's campaigns. The Campaigns section of a contact shows every campaign of the organization it is enrolled in, including a teammate's campaign (name and status, not who runs it).

Tied to each LinkedIn account

These come from your own LinkedIn account. You see yours, your teammates see theirs, and nobody sees another member's:

conversations and messages (the inbox is personal, there is no team inbox);
connection degree, invitations sent and accepted;
the last message exchanged and the AI analysis of the conversation;
sent and received invitations pages.

Swimlane does not show that a teammate is already connected to, or talking with, a contact. Use the shared signals instead: a note, a tag, or the contact's Campaigns section (see Best practices: dividing LinkedIn prospecting across a sales team).

Personal to each member

Campaigns. The Campaigns page lists only your own campaigns. A campaign always sends from the LinkedIn account of the member who created it, and uses that member's daily limits.
Pipelines created in the app are private to their creator.
Reminders and the calendar.
Message templates and saved list views.
Recurring imports. They run on the LinkedIn account of the member who set them up.
Daily limits (Import & Automation Limits) and Virtual Office Hours. Limits are never pooled: each member has their own.
Webhooks and API tokens.

Sharing a pipeline with the team

Pipelines created in the app are private. A pipeline becomes shared only when its visibility is set to team through the public API (see Swimlane public API reference). Every member then sees it and can edit it, and the team digest reports how many contacts sit in each of its stages.

What this means in practice

Two campaigns can target the same person. Swimlane prevents enrolling a contact twice in the same campaign, not in campaigns run by different members. Split your source lists (see the best practices article).
A note is your "I'm on it". Since conversations are private, write in the shared note or add a tag when you start talking to someone.
Removing a member keeps the shared data. Contacts and lists stay; their private pipelines and campaigns are no longer visible to anyone (see Invite teammates and manage roles).
The digest shows who did what. The team digest email lists, per member, invitations sent and accepted, with the names of the people who accepted (see The team digest: daily recap and weekly report).