LLM Request Rejected: Ask Your Workspace Admin to Claim the Organization Credit

Matthew Diakonov··10 min read

LLM Request Rejected: Ask Your Workspace Admin to Claim the Organization Credit

You are working in Cursor, Claude Code, or another AI tool connected to your company's Claude workspace. Mid-task, you get this message: "third-party apps now draw from extra usage, not plan limits. We've added a credit to your organization to get you started. Ask your workspace admin to claim it and keep going."

The fix is straightforward, but it requires someone with admin permissions on your Claude workspace. Here is what happened, who needs to act, and exactly how to resolve it.

Why This Message Appears on Organization Accounts

Anthropic changed how third-party app usage is billed. Previously, tools like Cursor and Claude Code drew from your team's shared plan limits. Now, third-party app requests pull from a separate "extra usage" credit pool that is tied to your organization, not individual seats.

When Anthropic rolled out this change, they added a starter credit to each organization account. But unlike individual Pro accounts where each user claims their own credit, organization credits require a workspace administrator to accept them. Until the admin does this, every team member hitting Claude through a third-party app will see the rejection message.

Organization billing flow (after the change)Team member usesCursor / Claude CodeOrg extra usagebalance = $0?yesREQUEST REJECTEDnoRequest succeedscredits deductedFix: Workspace admin claims the credit at claude.ai/settings/usageThen set up auto-reload or manual top-ups so the team never hits $0 again

Who Is the "Workspace Admin"?

The workspace admin is whoever created your Claude Team or Enterprise workspace, or anyone they promoted to the admin role. If you are not sure who that is:

  1. Open claude.ai and sign in with your work account
  2. Click your profile icon in the bottom-left corner
  3. Go to Settings, then look for the Members or Team section
  4. Admins are labeled with an "Admin" badge next to their name

If you see the admin badge next to your own name, you are the admin and can claim the credit yourself. If not, you need to reach out to one of the listed admins.

| Role | Can claim org credit? | Can add more credits? | Can enable auto-reload? | |---|---|---|---| | Owner | Yes | Yes | Yes | | Admin | Yes | Yes | Yes | | Member | No | No | No | | Guest / External | No | No | No |

How to Claim the Organization Credit (Admin Steps)

If you are the workspace admin (or if a team member just sent you this article), here is the step-by-step process:

  1. Sign in to claude.ai with your admin account
  2. Click your profile icon, then Settings
  3. Navigate to the Usage tab (or go directly to claude.ai/settings/usage)
  4. You should see a banner at the top about your organization's starter credit
  5. Click Claim credit (or the equivalent button)
  6. The credit will appear in your organization's extra usage balance immediately
  7. All team members using third-party apps will be unblocked within seconds

Warning

The credit banner may only appear once. If the admin dismisses it without claiming, check the extra usage balance directly. If the balance is already positive, the credit may have been applied automatically. If it shows $0 and no banner appears, contact Anthropic support.

What to Do After Claiming the Credit

The starter credit is a one-time grant. Depending on your team size and how heavily everyone uses third-party tools, it can run out in days or even hours. Here is a quick plan:

Set up auto-reload (recommended)

In the same Usage settings page, look for the Auto-reload option. This automatically adds credits when your balance drops below a threshold you set.

| Team size | Suggested reload amount | Suggested threshold | |---|---|---| | 2 to 5 developers | $50 | $10 | | 6 to 15 developers | $100 | $25 | | 16 to 50 developers | $250 | $50 | | 50+ developers | $500+ | $100 |

These are starting points. Monitor actual usage for the first week and adjust.

Monitor usage per member

The Usage page shows a breakdown of extra usage credits consumed per workspace member. Check this weekly to spot outliers. A single developer running parallel Claude Code agents can burn through credits 10x faster than someone using Cursor for occasional autocomplete.

| Usage pattern | Approximate cost per developer per day | |---|---|---| | Light (autocomplete, occasional chat) | $1 to $5 | | Moderate (regular chat, some agent use) | $5 to $15 | | Heavy (agent mode, parallel runs, large context) | $15 to $50+ |

Set a spending limit

Under Usage settings, admins can set a monthly spending cap for the organization. This prevents surprise bills if usage spikes unexpectedly.

If You Are Not the Admin: What to Send Them

Copy this message and send it to your workspace admin via Slack, email, or however your team communicates:

Hey, our Claude third-party app usage (Cursor, Claude Code, etc.) is blocked
because Anthropic added a free credit to our organization that needs to be
claimed by a workspace admin.

Can you go to claude.ai/settings/usage and claim the credit? It takes about
30 seconds. After that, you might also want to set up auto-reload so we
don't hit this again.

More details: https://fazm.ai/blog/llm-request-rejected-organization-credit-workspace-admin

Individual Credit vs Organization Credit

If you have both a personal Pro account and a Team workspace, they are separate. Claiming your personal $20 credit does not help your team, and the organization credit does not affect your personal account.

| Scenario | Credit location | Who claims | |---|---|---| | Personal Pro account | Your own settings | You | | Team workspace member | Organization settings | Workspace admin | | Enterprise account | Organization settings | Workspace admin or IT | | Using your own API key | No credit (pay-per-token) | N/A |

If you are getting rejected on your personal account, see our guide to claiming the individual extra usage credit.

Common Pitfalls

  • Assuming the credit was auto-claimed. On individual accounts, the credit sometimes applies automatically. On organization accounts, it almost always requires an explicit admin action.
  • Claiming with the wrong account. If your admin has both a personal and work Claude account, they need to be signed in to the workspace account, not their personal one.
  • Forgetting to set up auto-reload. The starter credit buys time, not a permanent fix. Without auto-reload or manual top-ups, your team will hit the same wall again once the credit runs out.
  • Not checking the Members page. If you are not sure who the admin is, the Members page in Settings lists everyone with their role. Do not just guess or email IT.
  • Mixing up API keys and OAuth. If your team uses Claude through direct API keys (not through the workspace OAuth flow), this credit system does not apply. API key usage is billed separately through the Anthropic Console, not the workspace extra usage pool.

Quick Checklist for Workspace Admins

Go to claude.ai/settings/usage and claim the organization credit
Verify the extra usage balance shows a positive amount
Enable auto-reload with a reasonable threshold for your team size
Set a monthly spending cap to avoid surprise charges
Notify your team that third-party apps should work again
Bookmark the Usage page for weekly monitoring

Wrapping Up

The "ask your workspace admin to claim it" message means Anthropic gave your organization free credits to cover the billing transition, but someone with admin access needs to accept them. Once claimed, your whole team is unblocked. Set up auto-reload so you do not end up here again next week.

Fazm is an open source macOS AI agent. Open source on GitHub.

Related Posts