Glean usage controls are the administrator tools that make a consumption-based licence manageable. Under Enterprise Flex, AI features consume pooled FlexCredits, and under Core Suite they draw Model Hub Usage, so a software asset manager needs a way to see who is consuming, to alert before a pool is exhausted and to stop use at a chosen limit. The Glean admin console provides a Usage dashboard and a limits and alerts function for those purposes.[1][2] Pricing is described in Glean Enterprise Flex, Core Suite and FlexCredits, and the overview is Glean licensing.
Editions
The controls differ by plan.
| Plan | Usage dashboard | Unit shown | Limits and alerts |
|---|---|---|---|
| Enterprise Flex | Usage dashboard: Enterprise Flex | FlexCredits | Total usage alerts across the contract period, plus monthly organisation, user and agent limits[1][2] |
| Glean Core Suite and Model Hub | Usage dashboard: Glean Core Suite and Model Hub | Dollars of Model Hub Usage cost | Monthly organisation, user and agent limits[3][2] |
| Legacy Glean Enterprise | A notice says the dashboard is no longer available, because it measures Enterprise Flex pricing | Not applicable | Not supported for users and agents[1][2] |
Glean notes that the notice on a legacy plan does not affect access to Glean or the current agreement, and it points customers to LLM insights and to Glean customer event logs for custom reporting.[1]
Metrics
The dashboards count the units that the pricing pages define: FlexCredits on Enterprise Flex and dollars of Model Hub Usage on Core Suite.[2] Consumption is attributed to the User who triggered it and to the agent that ran, and one Glean Agent Run is one execution of an agent. Departments are groups of users taken from the customer’s identity provider or organisation chart. A department appears in the dashboard only if its members have department information, and users without department metadata are not attributed to a department.[1] Because departments change, moving a user between departments changes how their usage is attributed.[1]
Counting / floors
The Usage dashboard
To open the Usage dashboard, a person needs the Super Admin or Admin role, or the Billing Moderator role where it is enabled in the deployment.[1] The Enterprise Flex dashboard lets the administrator filter by time period, view trends, break consumption down by feature and surface, and view tabs by users, departments, models and agents. The By users tab shows each user’s month-to-date FlexCredits and usage limit, and the table is available for any single-month selection from July 2026 onward, not for the All time view.[1] Tables export as CSV files for adoption analysis, budgeting, chargeback and showback.[1] Agents with non-billable usage do not appear in the agent table.[1]
Limits and alerts
Administrators can manage limits and alerts for the whole organisation, users, teams (departments or identity provider groups) and agents from the Usage dashboard. Usage limits reset at the start of each calendar month. By default Glean sends alert emails to Super Admins, Admins and Billing Moderators.[2] On Enterprise Flex, which tracks a pool of credits across the contract period, total usage alerts can be set at 50, 75, 90 or 100 percent of the available credits, with additional recipients if wanted.[2]
Three monthly limits can be switched on: a total monthly limit for the organisation, a default monthly limit for each user and a default monthly limit for each agent. Each can alert at chosen thresholds and, if the administrator selects “Block usage until the next month”, can stop usage when the limit is reached. If the box is left unchecked Glean sends alerts but does not block usage.[2] An administrator can override the default for an individual user from the By users tab.[2]
Department and team limits are not shared budgets. A 100 dollar limit for a department gives every member an individual 100 dollar limit, not 100 dollars shared across the team. Where more than one limit could apply to a user, Glean enforces the most specific in this order: the individual user limit, then the department limit, then the organisation-wide default user limit.[2] A workspace uses either departments or identity provider groups as its team source, and switching to groups discards existing department-level defaults, which cannot be recovered by switching back.[2]
How enforcement works
Glean enforces limits in near real time. If a query or agent run crosses the threshold while it is running, Glean lets the in-flight action finish and then blocks later billable usage for the rest of the calendar month, so a small overage may occur.[2] For rollout, the documentation suggests starting with alert-only limits to observe each department’s consumption before enforcing hard caps, and revisiting limits after reorganisations.[2] The limits control consumption within the commercial entitlement. They do not change what the customer owes under the Order Form, and they are a budgeting tool and not a billing guarantee.
Connectors and indexing limits
Connected Applications are third-party enterprise applications licensed independently by or for the customer, and Glean reports more than 275 out-of-the-box connectors.[4] The connector crawler enforces size limits when indexing. If a content item is larger than 64 MB, the crawler does not download its content and indexes only metadata and permissions, although the item remains searchable by metadata. Below that size, the crawler converts content to text and stores up to 16.875 MB of it, cutting the rest from indexing. Optical character recognition can be switched on for certain connectors to extract text from media, but the 64 MB limit still applies.[5] Content that is not indexed cannot be summarised and does not show the Summarize button in search results.[5] For a customer whose repositories hold large files, the practical effect is partial coverage that does not appear as a licence shortfall but reduces the value obtained from each seat.
Connectors are included in the seat fee under Core Suite, and connection, tools and indexing usage is licensed and governed by Assistant, Agents and API limits under Enterprise Flex.[6][7]
Agent execution limits
Glean agents run within guardrails. Every execution has a hard cap on the number of tool calls it can make in a single run, tool results are bounded in size and truncated when they exceed the limit, and scheduled agent runs have a maximum end-to-end execution time of approximately 30 minutes, after which Glean terminates the run. Scheduled runs can execute only write tools that administrators have permitted to run without user confirmation.[8] Glean Chat also enforces a maximum token size on each chat turn.[8] Agent runs consume FlexCredits at a variable rate that depends on how many connectors an agent searches, how many steps it takes, how much memory it keeps, how many tools it runs and the model used for each step, so a poorly designed agent costs more credits as well as hitting these limits.[7]
Virtualization & partitioning
Not applicable. The practical partitions are the department, the identity provider group and the agent, each of which can have its own monthly limit.[2]
Cloud / BYOL
Customer-hosted and Customer Key deployments are covered by the same admin console. LLM insights, shown to organisations that bring their own LLM key and to those on a Glean key with the LLM gateway enabled, monitor model capacity and reliability and complement the Usage dashboard.[1]
Programs
- Usage limits and alerts. Monthly limits by organisation, user, department, team and agent, with optional blocking.[2]
- Usage dashboards. Admin console views for Enterprise Flex and Core Suite, with CSV export.[1][3]
Out of scope
- Per-capability FlexCredit consumption beyond the typical figures on the rate card.
- Glean customer event log schemas and query examples.
- The security and permissions models of individual connectors.