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

# Smart Limits & Account Safety

> Daily limits, warm-up levels, working hours and health scores: the rules that keep every sender safe.

Senders are real people's LinkedIn accounts and mailboxes, so every outbound action is limited. The limits are enforced by the database for everyone, including admins and the Claude connector. You can lower a sender's limits, but nobody can raise them above the platform ceiling.

## How much a sender sends each day

Each sender has a daily limit (a **cap**) for each type of action. The cap is worked out fresh every day:

<Steps>
  <Step title="Take the lowest limit">
    The lowest of the **platform ceiling**, the **warm-up level cap**, and any **manual cap** you set.
  </Step>

  <Step title="Adjust for health">
    Multiply by ×1 at health 70 or above, ×0.6 from 50 to 69, and ×0 below 50 (the sender is paused).
  </Step>

  <Step title="Vary it slightly">
    Vary it by ±10% so the volume isn't identical every day. It's never below 1 if the base cap is at least 1.
  </Step>

  <Step title="Apply the schedule and weekly limit">
    Days with no working hours get a cap of 0. Invitations also stop once the **150-per-week** limit is used up (weeks start on Monday).
  </Step>
</Steps>

You can see today's used, reserved and cap figures on each sender's **Budgets** tab.

<Info>
  Replies you send from the Inbox don't count against any cap.
</Info>

## Platform ceilings

These are the most any sender can do per day, whatever its level or settings.

| Action                 | Per day               |
| ---------------------- | --------------------- |
| Invitations            | 80 (and 150 per week) |
| Profile views          | 100                   |
| Messages               | 100                   |
| InMails                | 50                    |
| Likes                  | 100                   |
| Comments               | 100                   |
| Endorsements           | 50                    |
| Search pages (imports) | 50                    |
| Withdrawals            | 20                    |
| Emails                 | 150                   |
| Post fetches           | 100                   |
| Follows                | 50                    |

**Post fetches** cover every time we read someone's posts: a like step, a comment step, an AI draft that mentions a post, and [profile enrichment](/ai-and-data/profile-enrichment) that needs posts. Reading posts is a separate allowance from profile views, so enriching a lead's posts never eats into profile views.

<Info>
  Every LinkedIn call the platform makes passes through one of these budgets. There is no back door and no setting that turns one off.
</Info>

## Warm-up levels

A new sender starts slow and earns higher limits by staying healthy.

| Level | Invites | Messages | Profile views | Likes | Comments | InMails | Search pages | Endorse | Withdraw | Emails | Post fetches | Follows |
| ----- | ------- | -------- | ------------- | ----- | -------- | ------- | ------------ | ------- | -------- | ------ | ------------ | ------- |
| **0** | 4       | 5        | 10            | 5     | 0        | 0       | 5            | 0       | 2        | 20     | 5            | 0       |
| **1** | 9       | 10       | 20            | 10    | 3        | 5       | 10           | 3       | 4        | 40     | 10           | 3       |
| **2** | 15      | 20       | 30            | 15    | 5        | 10      | 20           | 5       | 6        | 60     | 15           | 5       |
| **3** | 25      | 35       | 40            | 20    | 8        | 20      | 40           | 8       | 8        | 80     | 20           | 8       |
| **4** | 35      | 50       | 50            | 30    | 10       | 30      | 60           | 10      | 10       | 100    | 30           | 12      |
| **5** | 45      | 60       | 60            | 30    | 10       | 40      | 80           | 10      | 10       | 120    | 30           | 15      |

* LinkedIn senders start at **level 0**. Mailboxes start at **level 3**.
* A sender goes up one level after **14 days in a row at health 85 or above**.
* LinkedIn accounts with **fewer than 150 connections** (or an unknown count) stay at level 0 for at least **28 days**.

<Warning>
  **Free (non-Premium) LinkedIn accounts never go above level 1.** Only Premium LinkedIn accounts and mailboxes can reach level 5. Free accounts also have a small monthly allowance of invitations with a note.
</Warning>

## Working hours

Actions only run inside each sender's working hours, in the sender's own timezone. The default is **Monday–Friday, 09:00–18:00**. Every action is given a random time within those hours, so nothing goes out on a round minute or in a burst.

Each night the planner schedules the next day's actions for each sender. To plan the rest of today straight away, use **Plan now** on the sender's Overview tab. Change working hours on the sender's [Schedule tab](/senders/sender-profiles#schedule).

## Health score

Each sender has a health score from 0 to 100. It's the **lowest** of six sub-scores, so one weak area pulls the whole score down.

| Sub-score             | What it measures                                                                     |
| --------------------- | ------------------------------------------------------------------------------------ |
| **Session stability** | Disconnects in the last 14 days, and whether the sender is connected now             |
| **Rejection rate**    | How often LinkedIn rejects actions                                                   |
| **Acceptance rate**   | Share of invites accepted (counted once 20+ invites have been sent in 14 days)       |
| **Reply rate**        | Share of messages answered (counted once 20+ messages have been sent)                |
| **Consistency**       | How steady daily volume is. A sudden burst after days of inactivity scores very low. |
| **Verification**      | LinkedIn checkpoints (security checks) in the last 30 days                           |

Health is recalculated every hour, and again soon after events like a disconnect or a rejected action.

| Score        | Effect                                           |
| ------------ | ------------------------------------------------ |
| 85 and above | Excellent. Counts toward the next warm-up level. |
| 70–84        | Good. Full caps.                                 |
| 50–69        | All caps scaled to ×0.6                          |
| Below 50     | Sender auto-paused for 24 hours                  |

## Automatic pauses

| Condition                                                         | Effect                                                      | Resumes                                                                                           |
| ----------------------------------------------------------------- | ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------- |
| Health below 50                                                   | Auto-paused 24h                                             | When a recompute scores 50 or more                                                                |
| Health 50–69                                                      | All caps ×0.6                                               | When a recompute scores 70 or more                                                                |
| 3 or more rate-limit or server errors from LinkedIn within 1 hour | Auto-paused 24h                                             | Automatically after 24h                                                                           |
| LinkedIn says "cannot resend yet" on an invite                    | Invites blocked until next Monday (sender's time)           | Automatically                                                                                     |
| Sender not connected                                              | All actions held (they stay queued)                         | When the sender reconnects                                                                        |
| Manual pause                                                      | Nothing planned for the sender                              | A manager clicks **Resume**                                                                       |
| Workspace suspended for billing                                   | All senders paused, workspace read-only                     | **On their own**, as soon as the payment goes through. Nobody has to restart each sender by hand. |
| Full profile sections came back empty twice in a row              | Enrichment backs off for a few hours; sending is unaffected | Automatically                                                                                     |

## Two more guards

**InMail speed.** LinkedIn has restricted accounts that jumped from a few InMails a day to many, even with credits left. Week-over-week InMail growth is therefore capped at about **50% above the previous week's daily average**. You'll see InMails pace up over a few weeks rather than all at once.

**Background enrichment.** Filling in profiles for leads that aren't in a sequence uses only the profile views **left over** after the day's sequence actions, at most 30% of the sender's allowance, and none at all at warm-up levels 0 and 1. Campaigns always come first.

## Where to see these rules in the app

Go to **Settings → Safety**. Everyone in the workspace can view it. It shows the platform ceilings, the pause and resume rules, the warm-up caps by level, and any manual caps your team has set on each sender. Each sender has a **Budgets →** link to change its caps.

## Related articles

* [Sender Insights](/senders/sender-insights)
* [Understanding Sender Health: Key Metrics & Their Impact](/deep-dive/understanding-sender-health)
* [Warm-Up Best Practices for New Sender Profiles](/getting-started/onboarding-first-steps/warm-up-best-practices)
* [Sender's Schedule Explained](/senders/senders-schedule-explained)
* [Why Is There a Delay Between Actions?](/sequences/sequence-troubleshooting/why-is-there-a-delay-between-actions)
