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

# Understand what your plan meters

> What Introw counts against your plan: partner portals, internal seats, reports, goals and languages, plus the modules that are on or off, and where each limit shows up.

> For the person who owns the Introw contract and keeps getting asked "can we add one more".

Most limit questions are really one question asked late: what exactly counts, and when.
This page answers it so the number is never a surprise at the moment you publish.
For what your own plan includes, and what it costs to change, see [introw.io/pricing](https://introw.io/pricing).

## What you'll achieve

A clear picture of the six things Introw counts, the rule that decides when each one is consumed, and what you see when you reach it.

## Before you start

<Steps>
  <Step title="Know that limits are per organisation">
    Everything below is counted for your whole Introw organisation, not per user or per team.
    If you run several organisations, each has its own plan.
    See [Access multiple organisations](./access-multiple-organisations).
  </Step>
</Steps>

## What is counted

<Steps>
  <Step title="Partner portals">
    This is the one that matters most, and the one worth understanding precisely.

    **A partner consumes a portal the moment you publish an experience to them**, because publishing is what creates their portal.
    A partner sitting in your partners list with no experience assigned costs nothing, however many of them there are.
    So importing a thousand partners from your CRM does not touch the limit; publishing to the eleventh one might.

    Two consequences worth planning around.
    Editing and republishing a live experience never consumes anything, because those partners already have portals: the check counts only the partners you are adding.
    And a partner whose portal you no longer need still holds it until it is removed.

    Sold as "up to N partners", counted as portals. The two are the same number in practice, since a partner with a portal is exactly what you are paying for.
  </Step>

  <Step title="Internal seats">
    Your own colleagues in Introw. Partner contacts are never seats: partners reach the portal without an Introw seat and without a seat in your CRM, however many of their people you let in.
    See [Invite a team member](./invite-a-team-member).
  </Step>

  <Step title="Reports">
    Saved reports in the report builder. Dashboards are assembled from reports, so it is the reports that are counted.
    See [Build a report](/features/reporting/report-builder/guides/build-a-report).
  </Step>

  <Step title="Goals">
    Goal and KPI definitions, not the partners enrolled in them. One goal applied to two hundred partners is one goal.
    See [Launch a partner goal](/features/reporting/goals/guides/launch-a-partner-goal).
  </Step>

  <Step title="Portal languages">
    How many languages can be active at once. Translation itself is automatic; the count is on active languages.
    See [Set up portal languages](/features/localization/multilingual/guides/set-up-portal-languages).
  </Step>

  <Step title="API credits">
    Every plan includes a free monthly allowance, with no add-on to buy first.
    This one is metered differently from the rest and has its own reference: [API credits](/general/api-credits).
  </Step>
</Steps>

<Note>
  Any of these can be set to unlimited, and unlimited is a real setting rather than a very large number. An unlimited count is never reached, so an area that has never shown you a limit may simply not have one on your plan.
</Note>

## Modules are on or off, not counted

Separately from the counts above, whole areas of Introw are switched on or off per plan: commissions, courses and certificates, goals, MDF, partner quoting, affiliate campaigns, Power BI, custom domains, sending from your own email domain, a custom font, removing the Introw mark, portal SSO, internal SSO, portal embedding, MCP connections, Crossbeam, billing integrations, batch upload and WhatsApp among them.

The tell is consistent: **if an area shows an upgrade prompt where the feature should be, it is not on your plan.**
That is a different situation from a count you have reached, and no amount of tidying up will free one.

Two practical notes.
A module being off does not delete anything, so switching one on later finds your configuration where you left it.
And the section picker in the experience builder hides the groups your plan does not include, which is why **Marketing Funds** or **Affiliate Campaigns** may not appear for you.

## Where you meet each limit

<Steps>
  <Step title="At publish, for portals">
    Publishing an experience to more new partners than you have portals left blocks the publish with **Select fewer new partners or upgrade your plan to add more portals**.
    Nothing is half-applied: the partners you already had keep their portals and nothing changes until you either narrow the selection or add portals.

    This is the limit that lands at the worst moment, right when you are trying to go live, so it is worth checking your remaining portals before a rollout rather than during one.
    See [Launch the portal and run the first two weeks](/features/portal/portal-access/guides/launch-and-the-first-weeks).
  </Step>

  <Step title="At the point of creation, for everything else">
    Seats, reports, goals and languages stop you as you add the next one, in the area you are working in.
    Nothing already created is affected.
  </Step>

  <Step title="At the request, for API credits">
    A request beyond the monthly allowance is rejected with a `402`, and the rejected request does not itself spend a credit.
    Every metered response carries what is left, so an integration can see it coming.
    See [API credits](/general/api-credits).
  </Step>
</Steps>

## Verify it worked

Before any rollout, confirm two things: how many partners in the wave do not yet have a portal, and that every module the wave depends on is actually on your plan.
Those are the only two ways a launch gets blocked on commercials rather than on configuration.

To change any of it, see what your plan includes at [introw.io/pricing](https://introw.io/pricing).

## Related

<CardGroup cols={2}>
  <Card title="Invite a team member" icon="user-plus" href="./invite-a-team-member">
    Seats and what each one can do.
  </Card>

  <Card title="Draft, published and preview" icon="eye" href="/features/portal/experiences/guides/draft-publish-and-preview">
    What publishing does, including the portal check.
  </Card>

  <Card title="Reuse an experience" icon="copy" href="/features/portal/experiences/guides/reuse-an-experience">
    Reusing content is free; giving more partners a portal is not.
  </Card>

  <Card title="Implementation reference" icon="screwdriver-wrench" href="../technical">
    Full configuration options.
  </Card>
</CardGroup>