# Usage Statistics Generated: 2026-11-02T05:40:11.612Z Source build: local Canonical docs: https://teammately.ai/docs --- id: admin-console.usage title: Usage Statistics summary: Read recorded workspace measurements, date filtering, processing state, and ledger context without interpreting quantities as charges. kind: reference product_area: admin_console status: stable updated: 2026-10-30 canonical: /docs/admin-console/usage --- # Usage Statistics ## Definition Open **Admin → Insights → Usage Statistics** to inspect recorded workspace consumption. Read measurement quantities, processing status and credit information according to their own displayed meanings. ## Fields, states, or lifecycle rules - Date filtering uses local calendar boundaries while timestamps are transported in UTC. - Different measurements retain their own units. - Recorded quantities are not charges. - Processing status covers the workspace independently of the selected date range. - A failed processing-status read does not remove the recorded quantity summary. - Missing observations do not become zero use. ## Read the summary Choose the intended date range and compare like measurements. Tokens, execution time and other quantities cannot be added into one meaningful total simply because they share a table. A recorded usage summary describes what has been ingested by that point. Pending or provisional processing can explain why more information may arrive. It is not proof that every provider event has already settled. ## Inspect the ledger Use available ledger details to connect a quantity or credit entry to its recorded activity and unit. Retain the actual currency and unit identities when exporting or explaining a value. Credit displays have their own status and context. They do not turn a usage quantity into an invoice or establish a new spending guarantee. Follow your agreement for contractual billing questions. ## Resolve unavailable information Read the visible summary and processing state independently. A failed status request can coexist with a valid quantity summary. Use the provided refresh control for an unavailable read while preserving the selected date range. Do not infer a charge, free execution or completed processing from an absent field. The screen reports recorded values and their availability. ## Related task pages {% related-card-grid title="Related task pages" %} - [Admin Console](/docs/admin-console) - [Run Details and Metadata](/docs/benchmark-evaluations/run-details) - [Fieldloop](/docs/fieldloop) {% /related-card-grid %} --- id: admin-console.overview title: Admin Console summary: Use Admin in the main app to manage workspace access, integrations, API keys, Lemon instructions, and usage. kind: reference product_area: admin_console status: stable updated: 2026-10-30 canonical: /docs/admin-console --- # Admin Console Open **Admin** in the main Teammately app for workspace administration. Project Settings manages project-specific configuration; Benchmark workspaces own datasets, Contributions, evaluation and improvement. ## Definition Admin groups controls into Directory, Security, Insights, Organization Settings and Integrations. Current destinations include Members, Domain Control, IP Address Control, Private connectivity, Audit Log, Usage Statistics, Lemon instructions, Profile, Support Settings, Integrations and API Keys. ## Fields, states, or lifecycle rules - Workspace membership and project access are separate boundaries. - Project membership and an expert's assigned Contribution are separate. - API-key scope does not make an internal endpoint a supported external contract. - A connected provider account does not by itself authorize every training or inference operation. - Recorded usage quantities, processing health and charges have different meanings. ## Choose the owning control Use Members and the relevant security controls for workspace participation and allowed access. Use Project Settings → Project Members for grants to one Project. Use Lemon instructions for workspace-level activity guidance. Project overrides take precedence where configured, and change history is automatic. Use Integrations for messaging, repository, trace-store and training connections. Each service has its own authorization, configuration and operational result. A successful connection check is different from delivery or a completed provider job. Use API Keys to create a credential for the intended capability. Current types include Full Access, Read Only and Fieldloop Submission. Copy a newly issued value only into the approved secret mechanism. ## Inspect usage Usage Statistics shows recorded measurements for the chosen date range and workspace processing state. Quantities are not charges. A processing-status failure does not erase already recorded quantities. Follow the usage guide before interpreting pending processing, credit information or a ledger entry. This surface does not create an invoice or a new retention/compliance guarantee. ## Private connectivity Private connectivity is available as part of your Teammately deployment. In the main Teammately app, open **Admin → Security → Private connectivity** to learn about AWS PrivateLink, Azure Private Link, or equivalent connectivity for your environment. Private networking can cover: - **Your network to Teammately:** private access for sending data, including Fieldloop logs, to Teammately. - **Teammately to your model endpoint:** private access for model requests and responses. Private connectivity is arranged as part of your overall Teammately setup. [Ask us](https://teammately.ai/contact) about your deployment. ## Access and authority Read each permission from its owning surface. A role name used in an orientation page describes responsibility; it is not an exhaustive permission matrix. Approval authority over Policies, Rubrics or Contribution decisions remains with the corresponding workflow. ## Related task pages {% related-card-grid title="Related task pages" %} - [API Keys and Delegated Access](/docs/admin-console/api-keys) - [Workspace Integrations](/docs/admin-console/integrations) - [Usage Statistics](/docs/admin-console/usage) - [Project Members](/docs/project-settings/project-members) - [Lemon Instructions](/docs/project-settings/lemon-instructions) {% /related-card-grid %} --- id: project-settings.run-metadata title: Run Details and Metadata summary: Inspect the identity, recorded settings, source, telemetry, and status that explain an evaluation Run. kind: reference product_area: benchmark_evaluations status: stable updated: 2026-10-30 canonical: /docs/benchmark-evaluations/run-details --- # Run Details and Metadata ## Definition A Run's details explain which candidate was measured, against which Benchmark Version, under which execution conditions. Read the recorded Run rather than today's project defaults. ## Fields, states, or lifecycle rules - Managed Runs identify a saved Harness Version and captured runtime. - Imported Runs identify the external submission and its exact Cases. - Planned Trials, machine allocation and evaluation settings describe the recorded execution. - Status distinguishes output progress from rubric evaluation progress. - Labels and descriptive metadata help interpretation but do not replace issued identities. - Tokens, latency and cost are nullable measurements. Missing capture remains unknown. ## Run history and score use Use Run history to inspect independent executions of the same candidate. **Used for score** identifies the reference selected before outcomes were known. **Run evaluation** reopens matching work; **Run again** deliberately adds an independent Run. A later label or metadata change does not make two different execution populations identical. Retain the exact Run and Trial links when recording a comparison or asking an expert about a response. ## Settings versus observations Machine allocation and planned Trial count are accepted execution commitments. Measured latency, token use and actual responses are observations produced afterward. Keep both when explaining an operational difference. Historical descriptive fields remain attached to their Runs. They do not imply that there is a current project-level Run Metadata configuration tab or that editing today's settings changes accepted history. ## Using details in follow-up work Link an expert to the relevant response and criterion rather than only an aggregate. When copying an External Agents task, confirm whether its optional reference Run represents the code the agent will change. When starting Lemon Goal, inspect the selected starting candidate and available measurements. Never put credentials in labels, metadata or Case content. Grant secrets through the owning settings and Harness controls. ## Related task pages {% related-card-grid title="Related task pages" %} - [Run a Benchmark Evaluation](/docs/benchmark-evaluations/run-evaluation) - [Inspect Evaluation Results](/docs/benchmark-evaluations/inspect-results) - [Work with External Agents](/docs/improve/external-agents) {% /related-card-grid %} --- id: fieldloop.overview title: Fieldloop summary: Connect captured application activity to source-grounded Threads and explicit coverage or expert follow-up. kind: concept product_area: fieldloop status: stable updated: 2026-10-30 canonical: /docs/fieldloop --- # Fieldloop Fieldloop connects captured application activity to questions about correctness and input coverage. Open **Fieldloop → Logs** to inspect captured records and **Threads** to read the resulting inquiries. ## Definition A source describes where logs come from and how they may be processed. A log preserves captured input, output, messages, trajectories, actions, context or feedback. A Thread presents an inquiry grounded in selected source records and the relevant project context. A captured log is not an approved standard. A report can identify an issue worth investigating without establishing that a candidate violated an applicable Policy or that every production request was represented. ## Decision checkpoint | Need | Open | Boundary | | --- | --- | --- | | Inspect what was captured | Logs | Original content and source identity | | Manage a source or inspect intake | Source controls in Logs | Destination and processing permission | | Read an inquiry | Threads | Report, cited sources and history | | Act on a missing input situation | Coverage Design → Inbox | Separate adoption decision | | Ask a specialist to resolve meaning | Expert Contributions | Explicit request and expert judgment | ## Processing and source access Capture and durable intake precede analysis. Automatic discovery uses the source's explicit processing permission and the selected pipeline. Revoking processing permission stops further screening; it does not convert old reports into different historical facts. The backend owns model routing. Source settings and task data do not authorize a provider switch or override platform model selection. ## Read Threads Inspect cited source records, relevant Cases and retrieved standards. A report can retain uncertainty, contrary examples and unresolved questions. Read the exact published material behind a citation rather than interpreting fluent prose as approval. Coverage and Contribution handoffs remain explicit user choices. Fieldloop does not automatically contact experts, approve Policies or change benchmark membership. ## Preserve the source boundary Published logs and reports remain attributable to their original captured content. User-requested deletion and background staging cleanup are separate operations. Do not infer a general retention or erasure guarantee from a processing status. Use Fieldloop findings alongside deliberate benchmark construction. Capture volume alone does not prove production completeness, balanced coverage or correctness. ## Related reference pages {% related-card-grid title="Related reference pages" %} - [Capture and Inspect Logs](/docs/fieldloop/ingest-logs) - [Read Fieldloop Threads](/docs/fieldloop/threads) - [Input Coverage Inbox](/docs/coverage-design/inbox) - [API Keys and Delegated Access](/docs/admin-console/api-keys) - [Integrations](/docs/integrations) {% /related-card-grid %}