Settings
Admin › Settings is three pages in the rail: Behavior, Limits, and Governance. Changes apply on the next request — no restart, no redeploy.
Change a setting
Edit the value in its row. The row highlights until you click Save Changes; Discard drops unsaved edits. Each page saves its own edits, so switching pages loses nothing.
Values are validated on save — a number outside its range is rejected with the allowed range named.
A Modified badge means the org overrides the shipped default. Click the undo arrow to stage the default; saving then removes the override, so the setting tracks future shipped defaults instead of pinning a copy.
Behavior
What a caller gets, and what an author may build.
| Setting | Default | What it controls |
|---|---|---|
| Default detail level | detailed | Level served when a call names none and the entity pins none |
| Unconfigured objects | refuse | What agents get for objects with no entity: refuse and name what is configured, or serve identity only (Id and Name) |
| Default domain mode | fallback | How the default domain applies. fallback gives it only to people who have no other domain, so one grant limits someone with nothing to revoke. additive gives it alongside every other domain they hold. See Domain access |
| Computed context line | on | The computed line every payload carries — today’s date, the fiscal quarter and its boundaries, the data as-of time. Computed from org fiscal settings, never authored; about 50 tokens |
| Scope basis | role | How Find Records team/rollup scopes walk the hierarchy when an entity doesn’t say: role, manager, or territory. Plain hierarchy walks — no forecasting awareness. Entities can override per object |
| Brief types | business, brand, glossary, policy | The brief types offered in the editor and enforced at save, comma-separated — extend it with your own vocabulary. An admin can also coin one in place from a brief’s type picker, which appends it here. Removing a type doesn’t touch briefs already carrying it, but they won’t re-validate until retyped |
Limits
Every ceiling the engine enforces, grouped by what it bounds. Each row shows its default and allowed range.
| Section | Setting | Default | What it controls |
|---|---|---|---|
| Payload | Max payload tokens | 8,000 | Payload ceiling; over budget, related-list rows are trimmed and the payload notes it |
| Entity fields | Max fields — list / standard / detailed | 10 / 20 / 30 | Field cap per level |
| Entity fields | Max relationship depth | 1 | How many hops field expansion follows into related objects |
| Related lists | Default / max rows per related list | 10 / 50 | Rows a related list returns |
| Find Records | Default / max page size | 20 / 50 | Page size for Find/Query calls |
| Find Records | Max groups per aggregate | 10 | Most groups one aggregated call returns — largest first by the measure; truncation is stated and totals still cover the full set |
| Find Records | Max sampled groups | 5 | Most groups that get sample records per aggregated call. Each sampled group costs its own query — this cap is load protection |
| Get Records | Max records per call (standard / detailed) | 10 / 5 | Record caps for multi-record loads |
| Briefs | Max brief characters | 8,000 | Combined character cap across a brief’s content slots, enforced at save and activation. A brief is small, stable framing — a document that needs searching belongs in retrieval |
| Briefs | Max briefs per call | 10 | How many briefs one Get Briefs call may name |
NOTE
Very high Get Records caps can exhaust the platform’s per-request query limit mid-call — each record is a full assembly. Raise them gradually.
Governance
The switches with consequences.
| Section | Setting | Default | What it controls |
|---|---|---|---|
| Writes | Allow writes | off | The global write switch. Off, no agent surface can update records whatever any entity or domain declares — see Write access |
| Writes | Max records per write call | 10 | How many records one Update Records call may address (max 25), counted across the whole call. Your triggers and flows run for every record in it. Over the cap the call is refused whole — nothing previewed, nothing saved — and Get Catalog publishes the number so agents size their calls |
| Administration | Delegated administration | on | Domain management on or off |
| Telemetry | Track per-user usage | on | Per-user rollups on the Usage page — aggregates only, never payload content |