Skip to main content

For buyers

Collaborate with your buyer team

Invite teammates, set access, assign responsibility across Brands and Plans, find work with Mine, and review recent RFP activity.

4 min readUpdated

Understand access and responsibility

Buyer collaboration in Tap has two separate layers:

  • Workspace access determines what a teammate can see and do across the workspace.
  • Brand and Plan teams identify who is responsible for coordinating a specific Brand or Plan.

Every active workspace member keeps the same baseline visibility and editing access they already have. Adding someone as a lead or collaborator does not grant another permission, make the work private, or change who can send an RFP or Order.

Invite teammates and set their access

Open Settings, then Team, to see current members and pending invitations. Teammates with Invite teammates access can send and resend invitations. Teammates with Manage team access can also choose permissions, change a member's access, revoke an invitation, or remove a member.

Tap offers three common access levels:

AccessWhat it allows
PlannerCreate and edit Plans and drafts, coordinate Brand and Plan teams, and review activity. Cannot send live RFPs or Orders.
BuyerEverything a Planner can do, plus send RFPs and Orders.
AdminEverything a Buyer can do, plus manage the team, company settings, and billing.

A custom label appears when a teammate's exact permissions do not match one of these levels. A pending invite cannot be added to a Brand or Plan team. The person becomes eligible after accepting the invitation and joining the workspace.

Assign a Brand team

Each Brand can have one optional lead and any number of collaborators. Open the Brand and use its Team section to choose current workspace members. Brand headers and list rows show the assigned team so responsibility stays visible while you browse.

A new Brand assigns its creator as lead. You can replace that lead, add collaborators, or leave the Brand unassigned.

The Brand team is a default for future Plans. Changing it does not rewrite the teams on Plans that already exist.

Keep each Plan team independent

When you create a Plan for a Brand, Tap copies that Brand's current team onto the new Plan. If the Brand has no team, the person creating the Plan becomes its lead.

After creation, the Plan team is independent:

  • Changing the Brand team affects future Plans only.
  • Changing an existing Plan's Brand does not replace its team.
  • Editing a Plan team does not change the Brand team.
  • Every RFP under the Plan uses that Plan's team.

You can edit the team from the Plan header or from an RFP surface. Editing it from an RFP updates the whole Plan team, including every other RFP under that Plan. V1 does not create separate per-RFP teams.

Find the work assigned to you

Brand and Plan lists show team avatars and offer All and Mine filters. Mine shows records where you are the lead or a collaborator.

The Plan list keeps this responsibility filter separate from the existing Plan filter, so you can combine both without losing your current view.

Existing Brands and Plans remain unassigned until someone chooses a team. Tap does not guess historical ownership. Unassigned records still appear under All, but not under anyone's Mine view.

Review recent RFP activity

The Plan overview includes a compact recent RFP activity section across broadcast and digital out-of-home requests. It can show:

  • RFP creation
  • The latest draft edit for each RFP
  • Recipient changes
  • Sends and revisions
  • Deadline changes
  • Digital out-of-home delivery outcomes

Tap collapses repeated autosaves into the latest draft edit instead of filling the list with noise. Each item includes an actor and timestamp when available. RFP History also identifies the actor and gives context about the latest editor. Former members and system actions remain identifiable without exposing private notes or saved payload contents.

Handle changes from another session

Team assignments refresh when their queries refresh or when you return focus to the window. Tap does not use live cursors or presence indicators for these updates.

If someone changes the same Brand or team while your editor is open, Tap prevents your save from silently overwriting their work. The conflict state keeps your selections available so you can review the current team and retry.

Know what v1 does not add

Responsibility assignments do not change workspace visibility or role capabilities. They do not add internal comments, mentions, notifications, email alerts, presence, live cursors, private work, or separate RFP teams.

Use assignments to make ownership clear, Mine to focus your lists, and recent activity to understand what changed. Planner, Buyer, Admin, and custom permissions remain the authority for consequential actions.

Continue through the guide

Something missing from this page? Email help@tap.co