Settings inherit from the level above. A Project setting overrides Client; Client overrides Organization; Organization overrides Platform defaults. You can always reset a setting to inherit from the parent — and the inherited value will show up automatically.
Platform — AI model defaults, signup gates (Platform Admin only)
Project Settings page with tab strip across the top: General, Profile, Locations, Data Retention, Defect Routing.
3
Change a value
Click into any field and type. You’ll see a small spinner next to the field, then a green check when it’s saved.
A settings field mid-edit with a 'Saving…' spinner; another field below shows the 'Saved' checkmark.
No Save button. That’s intentional — every change commits automatically. If you navigate away mid-edit, the last typed value is saved.
4
If a field shows 'Inherited from parent'
The value comes from the parent scope (Org, Client). You see a small badge: “Inherited from Client: Acme”.To override at this scope, just type a new value. The badge changes to “Set at this scope.”To go back to inherited, click the Reset to inherited button next to the field.
Two fields side by side: one with 'Inherited from Acme' badge, one with 'Set at this scope' and a Reset button.
That’s the whole settings experience. Type, see check, move on. The complex inheritance and concurrency handling is all invisible.
How long TestFactors keeps your data. Each retention setting has sensible defaults you usually don’t need to change.
Setting
Default
Range
What it means
Workbooks
365 days
30–3650
How long uploaded workbooks (and parsed data) are kept
Test cycles
730 days
30–3650
How long completed cycles (with executions, defects, scripts) are kept
Test run artifacts
90 days
7–3650
How long screenshots, recordings, and logs attached to executions are kept
Reducing retention deletes data. A change from 365 to 30 days will trigger cleanup of anything older than 30 days within 24 hours. There’s no undo — if you have audit requirements, never reduce without checking first.
Org Acme uploads its corporate logo at Org Profile
Every Client under Acme inherits the Acme logo
Client Acme Q2 Project uploads its own logo → that Client now shows its own
Projects under Acme Q2 Project still inherit Acme Q2’s logo (not Acme corporate’s)
If a specific Project wants the corporate Acme logo back: open that Project’s Profile, click Reset to inherited on the logo — it falls back to Acme Q2 Project’s logo (the immediate parent). If you want to skip a level entirely, you have to upload it explicitly at the desired level.
You don’t have admin authority at this scope. Either:
Ask someone with the right role to make the change
Ask to be promoted (Project Manager for project settings, Client Manager for client settings, etc.)
I saved a value but it didn't take effect
Three checks:
Did the checkmark appear? If you saw a red error, the value failed validation — read the error.
Are you sure you’re looking at the right scope? A Client override shadows an Org value; you may be seeing the override.
Refresh the page. Sometimes the in-memory cache lags by a few seconds.
A teammate saved while I was editing — what happens?
TestFactors handles concurrent edits gracefully. If you and a teammate both edit different fields, both saves succeed. If you both edit the same field, the later save wins with a small toast: “Another user just updated this — your value was applied last.”
My logo crop looks wrong after upload
Upload again — you can re-crop in the same upload dialog. Each new upload replaces the previous one atomically. Old logo is deleted automatically.
The Reset to inherited button is missing
Either:
The value isn’t inherited (it’s set at this scope and there’s no parent value to fall back to)
You don’t have permission to change it
Hover over the field; the tooltip will explain.
I see 'Saving paused…'
You’ve hit the autosave rate limit (60 changes per minute per user). Pause for a moment; saves will resume automatically. Usually only seen when a script is accidentally typing into a field repeatedly.
I see a deprecated setting
Some old settings get marked deprecated and read-only with a "use [new-key]" hint. Open the suggested replacement and configure it instead. The deprecated one stays visible for context but won’t accept writes.
