Usage
Track AI credits, Agent Builder count, workflow runs, and monthly usage patterns.
Use this settings state to understand which workspace behavior, access rule, credential, usage signal, or data-model surface the control changes.
Learn the system by following the product states.
Use the screenshots as the primary map: start with the full context, trace the connected workflow, inspect the focused UI, then compare against the completed operating state.
Visible controlAccess or policyOperational effectUse this settings state to understand which workspace behavior, access rule, credential, usage signal, or data-model surface the control changes.
Summary
Track AI credits, Agent Builder count, workflow runs, and monthly usage patterns.
Concepts covered
Step breakdown
- Open UsageStart in the Usage section of the Admin control center.
- Inspect the real controlsIdentify the visible fields, buttons, switches, tables, and menus before changing configuration.
- Connect the setting to operationsUnderstand which user access, customer memory, developer access, usage, billing, or data-model behavior this setting affects.
What this screen does
Usage shows how the account is consuming Frontline resources. The captured dashboard includes AI Credits, Agent Builder, Workflow Runs, and a monthly usage chart.
This is the admin evidence layer for scale. It tells operators whether AI activity, agent creation, and workflow execution are growing as expected.
What each control shows
AI Credits shows monthly AI consumption. Agent Builder shows how many agents have been created against the account allowance. Workflow Runs shows automation volume. The chart shows usage across the selected month.
Use this page after launching agents or workflows to confirm the system is being used and to catch unexpected spikes early.
Operational outcome
Usage makes adoption measurable. Teams can connect product configuration to real execution volume instead of guessing whether the system is active.
Operational playbook
Use Usage as part of the Frontline Admin Usage operating loop: inspect the current product state, confirm the source context, and decide what should happen next.
The goal is not to memorize screens. The goal is to understand how the product surface supports repeatable work, AI assistance, and accountable handoff.
Best practices
Start with the operational job before changing configuration. Name the owner, define the trigger or source context, and decide how the result should be reviewed.
Prefer narrow, inspectable setups over broad automation. Teammates should be able to explain why the system took an action from the visible product state.
Troubleshooting
If the result does not match expectation, check the source context first, then permissions, connected integrations, required fields, workflow logs, and any AI-generated output used by downstream steps.
When in doubt, compare the latest product state with the related record, activity, or workflow execution so debugging starts from evidence rather than guesswork.
FAQs
What does Usage control?
Track AI credits, Agent Builder count, workflow runs, and monthly usage patterns.
Who should use this page?
Workspace admins, implementation owners, and operators responsible for configuring access, account behavior, developer integrations, or the data model.
How should this page fit into onboarding?
Use it to understand the product surface, inspect real UI states, and connect the concept to daily operating workflows before configuring production behavior.
What should I verify before using this in production?
Verify ownership, permissions, source context, failure behavior, and the handoff path so teammates can trust what the system does next.