Usage
Track AI credits, Agent Builder count, workflow runs, and monthly usage patterns.
Check which workspace behavior, access rule, credential, usage signal, or data-model surface the control changes.
What Usage is for
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 this page to identify what the control changes, which source context it uses, who owns the result, and where to verify it.
Use the page to identify the trigger, source data, owner, visible result, and review point before changing production behavior.
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.
Start with one workflow, message, record update, or Max task before expanding. The team should know what changed, who owns it, and how to pause or adjust it.
Troubleshooting
If the result is wrong, debug in this order: source data, permissions, connected tools, required fields, workflow logs, then any generated output used later.
When debugging, open the related CRM record, Max activity, workflow run, or integration log first. Fix the source data or rule before adding more automation.
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.