> ## Documentation Index
> Fetch the complete documentation index at: https://docs.citino.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Project settings

> Where a project’s scope is set: its brand and spellings, competitors, engines, segments, domains, objection questions, and archiving.

Project settings is where the scope every other screen states is actually set. A line at the top says the rule that governs all of it:

> Changing scope affects future runs only — history stays as it was collected.

The sections are listed down the side, in order: Brand, Competitors, Market & engines, Cadence, Segments, Domains, Objections (when it applies) and Danger zone.

## Saving

One **Save changes** in the toolbar saves Brand, Market & engines and Segments together, and **Discard** throws away unsaved edits. If a part is refused, the reason appears under its own section. Domains has its own **Save domains**. Other changes, such as an alias, a competitor or the objection switch, take effect when you make them.

## Brand

* **Project name**: used in prompts, alerts and exports.
* **Aliases**: spellings and misspellings we count as a mention of you. With none, only your exact brand name is counted, so add the spellings your buyers actually type: a missing one is a mention of you that nothing counts. A new alias is marked **in review** until Citino has checked it.
* **Re-scan history** re-runs alias matching over the stored answers, so past visibility reflects the list above. Re-scanning stored answers for an alias costs no engine calls and uses no prompts. The section shows while a re-scan is running, and when the last one finished.

## Competitors

The brands you compare yourself with. They are tracked on every screen and in your alerts, and set the rows of the league on [Brands](https://docs.citino.ai/guides/screens/brands.md). **Add competitor** tracks a brand by name; **Stop tracking** removes one. Brands that keep showing up without being tracked are suggested on Brands, where you can track them from the table.

## Market & engines

> The country we ask from and the AI engines we ask. Each engine is asked every question.

* **Market** was set when your prompts were created. Prompts run from this market’s location; a second market is a second project.
* **Engines**: a switch per engine. Turning off an engine stops future runs of your prompts against it. Its answers are kept, but figures count only the engines switched on, so its history leaves the charts while it is off. An engine your plan does not include says which plan carries it, or that it is not on your plan. See [Engines](https://docs.citino.ai/guides/account/engines.md).

## Cadence

> How often we ask your questions. Every question is asked once a day.

There is nothing to set: every prompt runs daily, on every plan.

## Segments

> Tick the segments you compete in. Your scores count only the questions in ticked segments.

Changing segments recomputes your scores over stored history. Nothing is re-run and no prompts are used. You must claim at least one segment, because every score is measured over the segments you claim. See [Scope and segments](https://docs.citino.ai/guides/scope-and-segments.md).

## Domains

Your site’s domain (filled in from onboarding, and marked so), and one optional domain for each competitor you track. They are used to check which AI crawlers can read these sites. They don’t change how sources are classified. A domain that cannot be used is flagged under its own field, and saving queues a check on [Crawlability](https://docs.citino.ai/guides/screens/crawlability.md).

## Objections

**Ask objection questions**, on by default: Citino asks five questions of its own about your brand each week on your engines, and they don’t count toward your plan. Turning them off pauses every one and stops their spend; what they found stays on [Objections](https://docs.citino.ai/guides/screens/objections.md). It is shown only for a project whose market can have them.

## Danger zone

**Archive project** stops all runs and alerts immediately. Everything collected stays readable, and its prompts go back to your plan’s limit. You confirm by typing the project’s name. Afterwards you land on your next project, or on onboarding if it was the last.

## Who can do what

| Role | What they can do here |
| - | - |
| Owner, admin | Everything, including turning on an engine that is an opt-in, the objection switch, and archiving the project. |
| Editor | Change the brand, aliases, competitors, engines, segments and domains, and run a re-scan. An editor can keep or turn off an opt-in engine, but only an owner or admin turns one on. |
| Viewer | Read every setting. One line says who can change them, and every control is shown muted with that reason. |

## Related

> [card] [Scope and segments](https://docs.citino.ai/guides/scope-and-segments.md)
>
> What claiming a segment changes.

> [card] [Engines](https://docs.citino.ai/guides/account/engines.md)
>
> The default engines and the opt-ins.

> [card] [Workspace settings](https://docs.citino.ai/guides/account/workspace-settings.md)
>
> Members, roles and the workspace.

> [card] [Crawlability](https://docs.citino.ai/guides/screens/crawlability.md)
>
> What the domains are used for.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.