Browse documentation

Limits & Quotas

See what your organization can use each month and each hour, how much it has used, and what happens at a limit.

Your organization's use of NGT's capacity (models, web searches, document extraction, workflow runs) and of storage is held to limits. They are counted across all of the organization's workspaces, not per workspace. The Limits & Quotas page shows each limit, how much of it is used, and when it resets.

Open Limits & Quotas

Open Settings, then Limits & Quotas under Organisation. Any member can open it.

The page lists one row per limit, grouped by what it is for. Each row says how much is used and when it resets, with a bar showing the share used. Until every limit applies, the line under the page header says from which date monthly limits apply. To ask for more, the Request increase button at the top right opens the Support page.

Limits & QuotasWhat your organization can use each month and each hour, and how much it has used. Monthly limits apply from 1December 2026.Request increaseMembersSeats18 of 30 seats60% usedAgentsNGT tokens per monthResets on 1 Dec34% usedNGT tokens per hourResets at 15:002% usedGoogle web searches per hour12 of 100 searches · Resets at 15:0012% usedDataDocument extraction with OCR per hour4 of 50 extractions · Resets at 15:008% usedDocument extraction per hour12 of 50 extractions · Resets at 15:0024% usedStorage8.4 GB of 50 GB (3.5 GB archived)17% usedWorkflowsWorkflow runs per month1,240 of 5,000 runs · Resets on 1 Dec25% usedWorkflow runs per hour18 of 1,000 runs · Resets at 15:002% used
Limits & Quotas: one row per limit, with how much is used and when it resets.

The limits

SectionRowWhat it countsWindow
MembersSeatsPeople with access to at least one workspace, plus invitations not yet acceptedAt any moment
AgentsNGT tokens per monthTokens agents use on NGT's models, in threads and in Ask Agent workflow stepsCalendar month
AgentsNGT tokens per hourThe same, over the current hourClock hour
AgentsGoogle web searches per hourWeb searches agents make with Google's ways (Web Search); Tavily, on the workspace's own key, counts nothingClock hour
DataDocument extraction with OCR per hourFile extractions that read scans with OCRClock hour
DataDocument extraction per hourFile extractions without OCRClock hour
DataStorageRecords and files together, across every workspaceAt any moment
WorkflowsWorkflow runs per monthWorkflow runs started, whatever started themCalendar month
WorkflowsWorkflow runs per hourThe same, over the current hourClock hour

A few details:

  • Monthly limits count the calendar month in UTC and reset on the 1st. Hourly limits reset at the start of the next hour. Seats and Storage are capacities: they never reset, they free up when you remove people or data.
  • The NGT token rows show only the bar and when they reset, not the token counts.
  • The Storage row says how much of it archived data objects hold, for example 8.4 GB of 50 GB (3.5 GB archived). An archived data object keeps its records until it is deleted for good, so deleting it is what frees that space. A deleted file frees its space at the next daily snapshot.
  • Tokens used on a model provider key your workspace brings itself are not NGT tokens and don't count here. See Hosting & data regions.

Plans and what they allow

The values come from your organization's plan, and NGT can set a different value for your organization alone. Whatever the plan, hourly limits on workflow runs and document extractions protect the shared capacity.

Your exact limits are the ones on your Limits & Quotas page, which reads your organization's own values. If you need more, click Request increase; NGT's support team raises limits.

When a limit is reached

  • Hourly limits and the Seats and Storage capacities apply at once.
  • Monthly limits apply from a date NGT sets. Until then, they are counted and shown but nothing is refused, and the line under the page header says from which date they apply, for example Monthly limits apply from 1 December 2026.

When something you do would pass a limit, SPARK refuses it and says why in a Limit reached message, with when to try again and a Contact support link. For example:

  • A full Seats limit stops new invitations, and resending an expired one.
  • A full Storage limit stops new records and new uploads.
  • The Workflow runs limits stop new runs, including scheduled ones.
  • The NGT tokens limits end an agent's turn once the allowance is used.
  • The Google web searches limit stops an agent's searches with Google's ways until the next hour; the agent says so in its answer.

Limits on the Monitoring pages

The Monitoring pages read the same organization limits: Workflow Usage shows the month's runs against the organization's monthly runs limit, and Data Usage shows the workspace's storage against the organization's storage. Because the limits are shared, a workspace's own use is only part of the total. See Monitoring.

Where to go next