Usage and limits
Review usage meters, apply overrides, and browse the usage ledger.
Monitor consumption against plan limits, apply lower overrides, and review the usage ledger by meter.
Quick start
- Open
Settings→ Usage & limits (/settings/usage). Church admins only. - Review Current usage summary cards — each meter shows used, reserved, limit, and reset date.
- To cap spend below your plan, enter an Optional lower church limit and click Save lower limit.
- Scroll to Usage ledger and filter by meter if needed.
- Click Load more to page through older entries.
You should see threshold indicators (50%, 80%, 100%) on meters approaching their limits.
Deep dive
What this page shows
Usage & limits is the church-wide consumption dashboard. It tracks metered activity such as:
| Meter | Examples |
|---|---|
| AI tokens / AI cost | Media AI analysis |
| Storage | Uploaded files and media |
| Parsing / OCR | Document ingestion |
| Image processing / Video frame processing | Media pipelines |
| Connector requests | Integration API calls |
| Email recipients | Ministry email sends |
Each card labels whether usage is Product quota or Billing-related usage.
Summary cards
Each meter card displays:
- Used + reserved of limit — current consumption and in-flight reservations
- Percentage used with color thresholds:
- Below 50%
- 50% threshold reached
- 80% threshold reached
- 100% limit reached
- Resets {date} — when the meter period rolls over (when applicable)
- No configured limit — unlimited meters show this instead of a cap
Reserved units are work already committed but not yet finalized (for example, a queued AI job).
Optional lower church limit
Admins can set a lower override below the plan limit — useful for internal budgeting without changing your subscription.
- Enter a whole number in Optional lower church limit
- Click Save lower limit
Rules:
- Must be a non-negative integer
- Cannot exceed the plan limit shown in the help text
- Click Restore plan limit to remove the override and use the full plan allowance
No purchase is made automatically from this page.
Usage ledger
The ledger is an audit trail of metering events. Columns:
| Column | Meaning |
|---|---|
| Meter | Which usage type was charged |
| Date | When the event occurred |
| Estimated / actual | Preliminary estimate vs finalized amount |
| Status | Settlement state of the entry |
| Source operation | Sanitized operation ID for support lookup |
Ledger entries contain metering metadata — not church content (sermon text, member data, etc.).
Use Filter by meter to narrow the table. Load more paginates 25 entries at a time.
When limits block work
When a meter hits 100%, related features may pause until reset or upgrade:
- AI analysis stops when AI cost or token limits are exhausted
- Connector requests may fail when integration quota is full
- Email sends may be blocked at recipient limits
To raise plan limits or add credits, see Billing and subscription. To lower AI spend proactively, adjust Media AI settings.
Operation IDs in the ledger
Copy a Source operation ID when contacting support or using Support to inspect a specific job.
Tips
- Review usage after your first month with Media AI auto-analyze enabled.
- Set lower overrides before large bulk uploads or email blasts.
- Watch reserved counts during heavy integration sync days.
- Filter the ledger by AI cost when debugging unexpected spend.
- Pair this page with Billing before changing plans.
[!note] Lower overrides reduce your effective limit immediately. They do not change your WorshipDeck subscription — only how much the church allows itself to consume.
Troubleshooting
Usage details could not be loaded
- Refresh the page.
- Confirm you are an active church Admin.
- Try again later if the service is temporarily unavailable.
Cannot save lower limit
- Value must be a whole number between 0 and the plan limit.
- Use Restore plan limit if a previous override is stuck.
Meter shows 100% but features still work
- Some meters reset on a schedule — check Resets {date}.
- Reserved units may still be processing; wait for jobs to finish.
Unexpected ledger entries
- Note the Source operation ID and date.
- Open Support to trace the operation timeline.
- Check Operations for stuck background jobs.
AI spend higher than expected
- Review Media AI auto-analyze settings.
- Lower the monthly cap or disable auto-analyze for large backfills.