Spending

The Spending tab, titled Spending caps on the page, sets ceilings on what your organization spends on work Nuvelics pays for. Spend on your own vendor credentials is never counted and never stopped.

Who can use itCopy Anchor Link

Owners and admins (spend-cap:manage). There is no read-only view: the tab is missing for Members and Viewers. To read the figures without changing caps, owners and admins can use Usage. Why caps exist and what counts toward them is explained in Spend caps and usage.

Set the capsCopy Anchor Link

1. Open Spending.
2. Enter a dollar amount in Daily cap, Weekly cap or Monthly cap. Leave a field empty for no cap on that window. Each window is checked on its own, and the first cap reached stops spending.
3. Under When a cap resets, choose Resume automatically or Wait for someone to resume.
4. Choose Save.

You see Spending caps updated.

What the fields mean:

• The daily cap covers a UTC calendar day, the weekly cap an ISO week starting Monday 00:00 UTC, and the monthly cap a UTC calendar month. All reset at 00:00 UTC.
• A cap of $0 pauses all paid work.
• Resume automatically restarts work as soon as every window is back under its cap. Wait for someone to resume keeps work stopped past the reset until an owner or admin resumes it here.
• A datasource running on your organization's own credential keeps working even while spending is stopped.

Amounts are in dollars, with up to six decimal places. Things you may hit:

• Enter a valid dollar amount: the field holds something other than a plain amount such as 50 or 0.10; a negative number, a currency symbol, spaces and exponent notation are refused.
• Amount is too large.
• Can't be more than the weekly cap or Can't be more than the monthly cap: the daily cap may not exceed the weekly or monthly cap you have set, since a day is part of its week and month.
• "These spending caps changed since you loaded them — reload and try again." means someone saved first.

See what a cap would have doneCopy Anchor Link

When history is available, each cap sits beside the past complete periods of Nuvelics-paid spend for that window, with the typical and busiest period (for example Typical day and Busiest day) and what you have spent so far in the current one. As you type, a sentence tells you how often that cap would have paused work, such as "At $5, work would never have paused in the last 30 days." The history counts complete windows only, and it is a floor, not a forecast: spend grows as you add datasources and newsdesks.

Resume work after a stopCopy Anchor Link

When a cap is reached, spending stops until the window ends. For new work to start, spending must be running. The tab offers the matching control:

• Resume spending appears when every cap is back under its limit and the policy held work at awaiting a resume. Choose it, and you see Spending resumed.
• Save and resume appears when the policy is Wait for someone to resume and spending is not running. It saves your caps and resumes in one step. If a cap is still exceeded you are told Cannot resume while a cap is still exceeded; raise the cap or wait for the reset.

While spending is stopped, other pages say so: members see that new pitches, enrichment and checks are paused until the cap resets or an owner or admin resumes.

Other ways to manage capsCopy Anchor Link

• CLI: nuvelics spend-caps with get, set and resume.
• API: Spend caps.