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 stays highlighted until you click Save Changes, and Discard drops unsaved edits. Each page keeps its own edits, so switching pages loses nothing.

Saving checks every value. A number outside its range doesn’t save, and the error names the range it has to fall in.

A Modified badge means this org overrides the shipped default. Click the undo arrow to stage the default as an unsaved edit, then Save Changes. That removes the override, so the setting follows future shipped defaults instead of pinning a copy of today’s.

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 reach	fallback	Whether holding another domain takes the default away. fallback gives the default only to people who have no other domain — and they cannot ask for it by name either — 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 standing 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. Org-wide: Info is the per-domain layer above it, and turning this off silences that too
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

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	Allow record creation	off	The global create switch, and independent of Allow writes — an org may let agents log a task without letting them edit anything, or the reverse. Off, no agent surface can add a record whatever any entity or domain declares — see Create access
Writes	Max records per write call	10	How many records one call may address (max 25), counted across the whole call — Update Records and Create Records share this cap. 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

What’s next

• Levels
• Usage