Analytics And Reporting
The Analytics page provides usage and cost visibility for generation workflows.
What Analytics Includes
Section titled “What Analytics Includes”Analytics surfaces:
- Volume and activity trends
- Success/failure distribution
- Asset type breakdown
- Model cost breakdown
- Cost totals by day, week, and month
Model attribution now prefers request-level usage events, so spend by model reflects the exact generation requests that were recorded instead of an even split across every model attached to an artifact.
Older artifacts are backfilled into the ledger automatically during startup when the platform can reconstruct their historical cost data from stored summaries and tracked storyboard activity.
For admins, additional scoped filters and breakdowns are available:
- User scope filters
- Team scope filters
- User and team cost breakdowns
- Threshold progress from model access policies
Common Review Workflow
Section titled “Common Review Workflow”- Open Analytics.
- Select scope filters if you are an admin.
- Review activity, quality, and spend metrics.
- Use results to tune policy thresholds and generation guidance.
Related Guides
Section titled “Related Guides”Operational Playbook
Section titled “Operational Playbook”Use this playbook for repeatable administration:
- Review metrics and policy thresholds on a regular schedule.
- Apply the smallest viable permission or policy change first, then observe impact.
- Communicate policy changes to affected teams before enforcement windows.
Troubleshooting
Section titled “Troubleshooting”If governance controls are not behaving as expected:
- Confirm scope (global vs team vs user) and precedence rules.
- Validate that users are assigned to the correct teams and role groups.
- Re-check policy thresholds and effective dates when behavior appears delayed.
- If a small set of legacy artifacts still appears under fallback attribution, their stored summary likely does not contain enough detail for an automatic backfill.
Frequently Asked Questions
Section titled “Frequently Asked Questions”Why are users still blocked after a policy change?
Section titled “Why are users still blocked after a policy change?”They may be affected by a stricter scope layer or stale session context.
How do we avoid over-permissioning?
Section titled “How do we avoid over-permissioning?”Use role-based defaults and grant temporary exceptions with explicit review dates.
What should we monitor weekly?
Section titled “What should we monitor weekly?”Spend trends, failure rates, exception volume, and policy-threshold pressure by team.