What Is the Monthly Per-User Credit Cap and Why Did I Get a Low Credit Warning?

Last updated: April 16, 2026

The monthly per-user credit cap is a spending limit set by your organization's admin through permission groups. When your usage drops below 20% of your cap, you'll receive a "Low Credit Warning" email. The cap resets automatically each billing cycle.


Before You Start


Symptoms

  • You received an email from no-reply@gumloopmail.com with the subject "Low Credit Warning - Permission Group Limit"

  • The email shows your remaining credits as a percentage of your cap (e.g., "3.0k / 15.0k (19.9%)")

  • Your agents or workflows stop running with a Credit Restriction Reached error once your personal balance hits zero

Cause

Your organization admin has set a monthly credit cap on your permission group. This is separate from your organization's total credit pool — even if the org has plenty of credits remaining, your individual cap limits how much you can use each month.

The low credit warning email fires when your personal balance drops below 20% of your cap. If your balance reaches zero, you'll be blocked from running agents and workflows until the cap resets or an admin increases your limit.

How the Monthly Reset Works

  1. Your credit cap resets on the same day each month, matching your organization's billing cycle anchor date (e.g., the 21st of every month).

  2. On reset day, your personal balance is restored to the full cap amount (e.g., back to 15,000).

  3. This happens automatically — no action is needed from you or your admin.


What You Can Do

If you're a user who hit the cap

  1. Wait for the automatic monthly reset on your organization's billing anchor date.

  2. If you need more credits before the reset, ask your organization admin to increase your cap or move you to a permission group with a higher limit.

If you're an organization admin adjusting the cap

  1. Go to Settings → Organization → Permission Groups.

  2. Select the permission group you want to modify.

  3. Update the User Monthly Credit Cap field to the new limit, or clear it to remove the cap entirely.

  4. The change takes effect immediately — all members of that group will have their limits recalculated.

Org Credits vs. Per-User Credit Cap

These are two different systems:

  • Organization credit pool — shared credits available to everyone in the org. Visible at Settings → Organization.

  • Per-user credit cap — an individual spending limit within a permission group. Acts as a guardrail so no single user can consume too large a share of the org's credits.

The per-user cap is a hard limit — it cannot be bypassed, even if the organization has credit overage enabled.

Still Need Help?

If this didn't resolve your issue, reach out to support at support@gumloop.com.

Related Docs