Some Harmonic products are costly to provide. While all user logins come with generous free limits, admins can opt into consumption-based pricing if they want to let their users go above that.
If you do, we want to provide you clarity and control over how your team spends.
How to access
Click your avatar in the bottom left of the main menu, and click "Settings"
Under the Scout section, all users will see "Usage", and admins will see additional pages for managing spend.
What users see
By default, users can see their daily / weekly / monthly limits. Every Console user includes complimentary usage credits as part of your existing license - see credit limits per user.
Once consumption-based pricing is enabled, users will see the monthly complimentary usage 'free usage', and paid usage which can be set by admins.
When you enable consumption-based pricing, complimentary usage is only limited monthly (not daily or weekly).
What admins can do
Admins can see current spend across surfaces and users
The Company spend page is where you can total monthly spend broken down by surface. Use it to understand where consumption is coming and set top level limits.
Admins can set a monthly spend limit for the org
This is the top-level cap on what your company spends on Scout in a month. Once you hit it, using scout past the complimentary amounts is blocked across the company until you raise the limit or the month resets. Set this to whatever you're comfortable spending.
Admins can set monthly spend limits per surface: API vs. Console
Scout via API and Console usage tends to look very different. API is typically programmatic – a couple people running automations for many team members. Console is in-product use, spread across everyone who logs in. Setting separate limits lets you cap each independently, so a heavy API workflow doesn't eat into the budget your team needs in-product.
Console licenses come with complimentary usage credits for every user. You only use credits if users go past their complimentary allocation – see credit limits per user.
Admins can set a default per-user spend limit, with individual overrides for specific users
The individual spend limit is the default monthly cap for any single user. Most teams want a sensible default that applies to everyone. For users who need more, you can override on a per-user basis from the Individual spend table.
When a limit is hit
Scout checks usage against all of your limits – per user, per surface, and across the company. If you've set paid limits, these notifications track the combination the user's paid and complimentary usage.
At 80% of the user's limits, we show a warning so you have time to adjust before you're blocked.
At 100%, Scout returns an error and stops responding until the limit resets or an admin raises it.
