Project settings
Every field on a project and what changing it does: the brand, the domain, the scope, the market, the cadence and the project model keys.
Updated October 20, 2026
Settings is where a project's identity lives. Some of these fields change how runs are scored, which makes them worth getting right before the first week rather than after it.
Fields that change how runs are read
| Field | What it decides |
|---|---|
| Brand name | What counts as you in an answer. |
| Name variants | The other spellings that also count as you. Comma separated. |
| Website domain | Which cited URLs count as yours. Bare domain, no scheme and no path. |
| URL scope | For a multi-division site, which paths are yours rather than a sibling's. |
Editing any of these applies from the next run. Everything already measured keeps the attribution it was scored with: re-scoring history would make old charts change shape under you, which is worse than a visible seam.
The first two are better managed visually in Name matching, where you can see every name models have actually used and map each one. Settings is the quick path; Name matching is the real one. See brand and competitors.
Fields that describe the market
Vertical, city or metro, service, market country and language. They tune parsing and prompt suggestions rather than scoring, so they are safe to change at any time. See market, language and vertical.
Tracking cadence
The project default for how often prompts run. Individual prompts follow it unless set otherwise. Shown beside the projected cost by engine, because changing it changes your model spend the same day.
Model keys
OpenAI key for ChatGPT probes, OpenRouter key for Claude, Gemini and Perplexity. Both are optional here: with neither, the project uses the account keys. With one set, it overrides the account key for this project only.
Keys are stored encrypted and shown only as their last four characters once saved. Replacing one takes effect on the next run. See keys and spend.
Industry benchmarks
With a vertical set, the project can be read against category benchmarks. Good context for the first conversation about whether a number is healthy; never a target.
Pausing and cancelling
Both stop new runs and neither deletes anything. A paused project stops counting against your plan's active project limit, which is how an agency keeps a finished engagement's history without paying for it.
Cancelling is the same from a data point of view: the prompts, the runs, the sources and the scores all stay. Nothing in Omnipresence hard-deletes a member's history.
Questions about project settings
- Will editing a field change my past numbers?
- No. Past runs keep the configuration they were scored with, so a change shows as a seam in the data rather than silently rewriting history.
- Where are the model keys, on the account or the project?
- Both exist. A project key overrides the account key for that project, which is how an agency puts a client's run cost on the client's own provider bill.
- What happens when I pause a project?
- New runs stop. Nothing is deleted, the project stops counting against your plan's active limit, and resuming picks up with a visible gap in the trend.