> ## Documentation Index
> Fetch the complete documentation index at: https://help.pipelime.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Plan limits reference (what is enforced)

> Every limit a plan can carry, which ones actually block an action, and how each one is measured.

Fourteen separate quantities are measured against your plan: credits, team seats, connected channel accounts, managed infrastructure and more. Only some of them can actually stop you from doing something; the rest are only counted.

<div className="pl-availability">
  <div className="pl-availability__row">
    <div className="pl-availability__label">Where</div>
    <div className="pl-availability__value"><span className="pl-path">Your avatar<span className="pl-path__sep">→</span>Subscription</span></div>
  </div>

  <div className="pl-availability__row">
    <div className="pl-availability__label">Partner-branded workspaces</div>
    <div className="pl-availability__value">Not shown in partner-branded workspaces.</div>
  </div>

  <div className="pl-availability__note">Visible to the account owner. In a partner-branded workspace the end users never see billing; the partner manages the plan.</div>
</div>

## The fourteen dimensions

| Dimension               | What counts against it                                                                                                                           | Blocks the action? |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------ |
| `credits`               | Every chargeable lead your workspaces analyze this period, plus every phone number revealed: a revealed phone number costs more than a lead does | Yes                |
| `users`                 | Team members across every workspace you own                                                                                                      | No (see below)     |
| `companies`             | Workspaces you own                                                                                                                               | No (see below)     |
| `leads`                 | Every lead your workspaces have ever created, deleted ones included                                                                              | No                 |
| `warmups`               | Warm-ups currently running                                                                                                                       | No                 |
| `senders`               | Every email account in your workspaces, on any provider, archived ones included                                                                  | No                 |
| `recipients`            | Distinct lead-and-campaign pairs with a campaign message this period                                                                             | No                 |
| `identified_companies`  | Companies identified through website tracking this period                                                                                        | Yes, silently      |
| `linkedin_accounts`     | Connected LinkedIn accounts                                                                                                                      | Yes                |
| `whatsapp_accounts`     | Connected WhatsApp numbers                                                                                                                       | Yes                |
| `instagram_accounts`    | Connected Instagram accounts                                                                                                                     | Yes                |
| `mercadolibre_accounts` | Connected MercadoLibre accounts                                                                                                                  | Yes                |
| `domains`               | Domains on PipeLime managed infrastructure, live or on order                                                                                     | Yes                |
| `email_accounts`        | Mailboxes on PipeLime managed infrastructure, live or on order                                                                                   | Yes                |

What a lead and a phone number each cost is on [what consumes credits](/en/billing/what-consumes-credits).

Five of the fourteen never appear as a balance anywhere you can see: `users`, `companies`, `leads`, `warmups` and `senders`. The account balance the app reads leaves all five out, so no screen can show them. `recipients` does get a bar, with a tooltip calling it "Your monthly email recipient limit", but nothing stops a campaign once you are past it. The bar turns red as it nears full, and that is all it does.

## Blocked, silent, or ignored

Six dimensions behave the way "limit" suggests: connect one more LinkedIn, WhatsApp, Instagram or MercadoLibre account than your allowance covers, or order one more managed domain or mailbox, and the action is refused outright. All six are counted per workspace: each workspace has its own tally of connected accounts and its own tally of managed infrastructure. The refusal is the dialog covered on ["Subscription Required" and the locked plan screen](/en/billing/subscription-required-and-lockout).

`senders` and `email_accounts` sound like the same thing and aren't. `senders` counts every email account in your workspaces, on any provider, and never blocks anything. `email_accounts` counts only mailboxes on PipeLime managed infrastructure (live or still on order), and ordering past that allowance is refused.

`identified_companies`, the capacity behind website-visitor tracking, is enforced the same way as the six above but never tells you at the moment it happens. The tracking script keeps recording every visit; once the period's allowance is spent, a visit that would have identified a brand-new company is dropped instead. Companies already identified keep updating as normal.

`credits` blocks too, but the gates that matter most count account-wide rather than per workspace. Generating leads, importing them, and looking up a contact's details all measure what every workspace you own has spent this period against one allowance: spend credits in one workspace and there is less left for all of them. The credit check inside a workflow's enrichment step is the exception: it counts only the workspace that workflow runs in.

`users` and `companies` are checked in the code the same way the six blocking dimensions are, but that check always resolves to no limit for either one. Inviting another team member or creating another workspace is never refused, whatever your plan says about seats.

## How the allowance is set

Your plan sets the base number for the dimensions it includes. A dimension your plan leaves uncapped resolves to unlimited rather than to a very large number: credits then show as an infinity symbol in the [credits and usage popover](/en/billing/usage-meter), and the other dimensions are left out of that popover's list entirely rather than drawn as a full or empty bar.

A workspace can also carry limits set directly on it, outside any plan. Where one of those exists it replaces the plan's number for that dimension rather than adding to it. It only applies to the checks that are scoped to a workspace, which is all of them except the account-wide credit gates above.

Managed domains, managed mailboxes and website-visitor tracking are the exception to plan-granted capacity: no plan includes any of the three. Domains and mailboxes each come from their own separate subscription, billed apart from your plan. Tracking capacity is also bought separately, but as an extra line on the same subscription your plan sits on, not a second one.

Two things add on top of your plan. A credit package you buy becomes another line on that same subscription, so its credits are granted again every period alongside your plan's. Separately, a one-off grant (the credits and recipients your account starts with, or an exception applied by support) is recorded against your account with its own start and end date, which is why the starting credits run out on a date and a purchased package does not. A grant like that can be made against any of the fourteen dimensions, though it changes nothing for `users` and `companies`, which resolve to no limit before a grant is ever consulted.

## The billing period

Your billing period is a rolling month anchored to the day your subscription began, not the calendar month: [your billing period and when limits reset](/en/billing/billing-period-and-renewal) covers it in full. Only `credits`, `recipients` and `identified_companies` reset when it rolls over. Every other dimension (seats, workspaces, connected accounts, managed domains and mailboxes) is a running count of what exists right now, and never resets on its own.

## Related

<CardGroup cols={2}>
  <Card title="Reading the credits and usage popover" icon="gauge" href="/en/billing/usage-meter">
    Where these numbers actually show up, and what unlimited looks like on the bar.
  </Card>

  <Card title="&#x22;Subscription Required&#x22; and the locked plan screen" icon="lock" href="/en/billing/subscription-required-and-lockout">
    What happens the moment one of the six blocking dimensions runs out.
  </Card>

  <Card title="Feature availability matrix" icon="table" href="/en/reference/feature-availability">
    Every surface in the product and what gates it: permission, role or plan.
  </Card>
</CardGroup>
