How credits work for teams

Credits are counted per seat and pooled into one team balance. On a paid plan, every seat you pay for adds its People Search credits to the team's pool each cycle: 4 seats on Apex at 6,000 each is 24,000 People Search credits a cycle, shared by the whole team. Email reveal allowances work the same way: counted per seat and shared by the whole team. AI credits are different: each plan includes one AI pool for the whole team, whatever the seat count (2,000 a month on Apex). Top-up credits you buy join the team balance and last until they are used. Plan credits do not roll over. A seat added part-way through a cycle adds its credits from the next billing date.

Who spends them. By default, anyone whose role can spend credits draws from the shared balance, so one busy rep can use most of it, while an admin who never searches uses none. To make it fair, an admin can give members a monthly budget. Open Team, then the Credits tab (members with Team Management only). It shows the team's credits this cycle, for example 24,000 People Search credits, 4 seats x 6,000, shared by your team, with a bar of what members used, what is set aside in budgets and what is shared. Switch between People Search and AI credits at the top. Each member's row shows their budget, what they used this cycle, what is left, and their daily limit.

Budgets. Press the pencil next to a member's budget and enter a whole number of credits, or leave it empty so they share. A budget sets those credits aside for that member: only they can spend them, up to the budget, this cycle. Members without a budget share what is left once the unspent part of every budget is set aside. A Super Admin never has a budget and shares what is left. You cannot change your own budget, not even with Split evenly or Clear all budgets. Split evenly shares the team's credits for the cycle out in equal monthly budgets among every member who can spend these credits and is not paused, and clears everyone else's: an admin who never spends, plus 3 reps on 24,000 credits, gives each rep 8,000 a cycle. If you can spend these credits yourself but are not a Super Admin, your even share stays shared for you, and a budget you already have stays as it is. Clear all budgets lets the whole team share again. Budgets can never add up to more than the team's credits for the cycle (the plan's credits plus top-up credits you still hold): a change that would is refused with a message saying so, while lowering a budget always works. Part-way through a cycle, budgets can set aside more than the team has left, for example when you raise a budget late in the cycle or after a seat is removed. The Credits tab then shows a warning: until your credits reset, members with a budget share what is left, first come, first served, and members without one cannot spend. When every member who can spend has a budget and some credits are in none, the tab says so, because only Super Admins can spend those.

The cycle. People Search budgets follow your plan's credit cycle and reset when your plan credits reset (your billing date on a paid plan). AI budgets reset on the 1st of each month, when AI credits reset. What a member spent earlier on the day credits reset stays with the cycle before. Credits handed back, such as a lookup that finds nothing or the unused part of a search page, go back to the member's budget. A daily limit still applies on top of a budget.

What members see. A member with a budget sees it under Usage in the sidebar, on the Billing page and under Credits in Discover, for example "Your budget: 5,000 of 8,000 left". A member without one sees what the team shares, for example "Shared: 2,000 left". If the team has less left than a member's budget, they see both, for example "Your budget: 1,400 of 8,000 left, team has 300". When a budget is used up, a paid action is refused before anything is charged, with "You have used your 6,000-credit budget for this cycle. Ask your admin for more." Work a member started in the background, such as Add all to list, a bulk email check or an automation they built, counts toward their budget and stops at it, keeping what finished.

Good to know. A budget is visible only to that member and to admins with Team Management. A paused member's budget stays set aside and still limits the work they started. Removing a member gives their budget back to the team. Checks the workspace runs on its own before campaign emails send, automatic call summaries and meeting scoring do not count toward any budget, and neither do requests made with an older workspace API key that has no owner. They are never stopped by a budget, so campaign emails always go out: they are paid from the team balance and can use credits set aside in budgets. If you give out every credit in budgets, leave a little for them. Every budget change is recorded in Settings, Activity as "Changed credit budgets", with who made it.