SyntropyLabsSettings and organization
Plan, usage and locks
What a lock in the nav means, the fourteen feature keys and what each unlocks, the plan limits, usage per Environment, upgrade requests, and why locked docs pages preview instead of hide.
After this page you know why an item is locked, which feature would unlock it, how close the organization is to its limits, and how to ask for more — and what happens to your data when a limit is met (nothing).
What a lock means
Every plan-gated item stays in the left nav on every plan, with a lock when the organization’s plan lacks its feature; hovering says which plans include it. Clicking a locked item, a locked button or a deep link to a gated route opens an upgrade panel in place — one line on what the feature does, what it includes, Request upgrade and See pricing — and never redirects, so Back to where I was returns you to the same page and filters. The plan badge in the shell shows this organization’s plan; your effective features are the best across every organization you belong to, which is why the badge and a lock can seem to disagree.
The fourteen feature keys
| Key | Unlocks |
|---|---|
datasets | Datasets: CSV and JSONL import, rows from traces, snapshots, synthesis, auto-add rules |
evaluators | Evaluators (library, custom judges, code, assertions, collections), runs, playground grids, prompts |
trace-evaluation | Evaluate on traces, online rules, calibration |
trace-optimization | Optimize on a trace, topics and patterns |
simulations | Agents, scenario sets, simulation runs, scoring, red team |
cost-calculator | Estimate a workload |
project-text | Text generation surfaces: generate outputs, the Playground |
project-image | the Image tab of the Playground |
project-video | the Video tab of the Playground |
voice-eval | Voice datasets, the Voice tab, voice evaluation jobs |
chat-playground | the Playground chat, compare and prompts |
rl-labeling | Annotate: score types, review queues, labels, RL datasets |
alerts | Alerts and monitors |
benchmark | the public model benchmark board |
Keys have hard dependencies the platform enforces: evaluators needs datasets; trace-evaluation, voice-eval and simulations need evaluators; project-text needs datasets. Traces, Cost, Settings, the notification bell, comments and end-user feedback need no key. Docs pages about a gated feature carry the same lock in this sidebar and show their summary rather than their content until the plan includes the feature.
Limits and usage
Organization settings → Plan & usage (sidebar footer → Settings → Organization → Plan & usage, or Upgrade beside the plan in the same footer) shows the feature matrix with the same lock icons as the nav, the three limits — Environments (traceProjectLimit, −1 for unlimited), retention days, and the monthly span soft cap — and usage: spans this month per Environment, summed in the browser for the organization. The soft cap is tracked, never enforced: ingestion continues past it, a banner on Traces and Home says so at 80%, and the organization owner is emailed once at 80% and once at 100% per Environment per month. Hitting the Environment limit locks New environment and opens the same panel with “1 of 1” wording.
Request an upgrade
Request upgrade records a request (the plan wanted, your name and a note) and emails the platform team; it appears as pending on this page. There is no self-serve billing: a platform admin changes the plan, and the nav unlocks on your next page load (the plan cache refreshes within a minute). Owners and Admins get a plan changed notification. A platform admin can also set a retention hold so an organization’s traces stop expiring.