When you add the team add-on, multiple people share one prospiq subscription. This page describes exactly what's shared between team members and what stays private to each individual.
What is shared across the team
Credits
The team's monthly credit allowance is a single shared pool, not divided per person. If your plan is Growth (1,500 credits/month) and you have a five-seat team, the team has 1,500 credits to spend collectively — not 1,500 per person.
Each team member can see the team's current balance and how many credits have been used in the current cycle. The team owner can see usage broken down by member to spot anyone who's consuming disproportionately.
Shared lists
Saved lists can be marked as shared with the team. Once shared, all team members can view the list, see the contacts in it, and (depending on their role) edit or remove contacts.
Shared lists are intended for collaborative campaign workflows — one person builds the list, another person follows up on it. They're not intended as a way to bypass another team's privacy.
Verified enrichments
When one team member enriches a contact, that contact is now in the team's history and any team member can be granted access to it through a shared list. We don't re-charge the team for a second member viewing a contact someone else already enriched.
Integration connections
CRM connections (HubSpot, Salesforce, Zoho) configured by the team owner are available to team members. If your team has connected HubSpot, any member with the right role can push contacts to that HubSpot account.
Team management actions (visible to admins)
Adding members, removing members, changing roles — these actions are visible in the team's admin log to anyone with admin or owner access.
What stays private to each team member
Personal search history
The lookups you run individually are stored under your account. Other team members don't see your private search history unless you save the results into a shared list.
Private saved lists
Saved lists can be marked private. Private lists are visible only to you. Other team members — including the team owner — can't see private lists or their contents.
Your account profile
Your name, email, password (or rather, your OAuth identity), and authentication settings are yours. Other team members see your name and role on the team but not your security configuration.
Your API keys (Pro plan)
API keys are generated per user, not per team. If you generate an API key, it's tied to you and only you can see it. The team owner can see that you have an active API key, but cannot view its value.
What the team owner can see that members can't
A few things are visible only to the team owner (and, where applicable, admins):
- The full member list with each member's role and join date
- Per-member credit usage breakdowns
- Billing details, invoices, and payment history
- The full audit log of team management actions (invites, role changes, removals)
- Total team credit consumption in the current and previous cycles
The team owner cannot see individual members' search history or private lists — those remain private regardless of role.
What happens when someone leaves the team
When a team member is removed (by themselves or by the owner):
- They lose access to all shared lists from that point forward
- Their personal search history goes with them — it's stored under their personal account, not the team's
- Any contacts they personally enriched and saved into shared lists remain in those shared lists (they belong to the team, not the individual)
- Any private lists they created go with them — those are tied to their personal account
- Their API keys (if any) are revoked
- They can be re-invited later if they should return
What about contacts I enriched before joining a team?
If you used prospiq as an individual and were later invited into a team, your pre-existing lookups, lists, and history stay under your personal account. They don't automatically merge into the team.
If you want to make some of your prior lists available to the team, you can share them explicitly. Otherwise they remain private to you.