> For the complete documentation index, see [llms.txt](https://docs.3techagency.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.3techagency.com/documentation/reference-and-help/settings.md). # Settings reference Every Settings tab and section, each control, and its default. Open **WP AI Manager > Settings**. The section row has **Settings**, **External MCP**, **MCP log**, **Sandbox**, **Modules** and **Help and changelog**. The main **Settings** page has six tabs. ## AI Models | Control | Default | Notes | | ------------------------ | ----------- | ------------------------------------------------------------------------------------------- | | How the assistant works | - | Explains Best quality and Faster, lower cost; **Open Connectors** to change provider or key | | Best quality model | Recommended | Used by chat and planning | | Faster, lower cost model | Recommended | Used for per-item Task work | | Connection details | - | Each provider's readiness, models and problems; **Check again** | | Image models | - | The order image models are tried; photo models first | | Last image problem | - | Time, model, error and **Technical detail** | See [Connect AI and choose models](/documentation/start-here/connect-ai-and-choose-models.md). ## Access A grid of WordPress roles against **Chat**, **Approve writes**, **Run tasks** and **Woo-only**. Administrators always have full access; other roles have none until you tick and save. See [Access, privacy and safety](/documentation/work-safely/access-privacy-and-safety.md). ## Privacy **Delete conversations after** *N* days. Default 90; 0 keeps them forever. Task runs follow the same window. ## Advanced | Control | Default | What it does | | ------------------------- | ------------------------------------------ | --------------------------------------------------------------------------------------------------------- | | External MCP surface | Off | Exposes the MCP server and OAuth endpoints to outside AI clients | | Backups to keep | 5 (1 to 50) | Database archives kept; archives also expire after 7 days | | Model choice in chat | Off | Lets chat users pick any connected model | | AI can use advanced tools | Off | Unlocks Filesystem, Database, WP-CLI, Custom Code and User-write tools that are also on in Advanced tools | | Monthly token limit | 0 (no limit) | Soft ceiling: chat continues, scheduled runs skip. Shows tokens used in the last 30 days. | | Protected pages | Cart, checkout, my-account, privacy policy | Extra pages the AI can never write to | | Allow AI-written code | Off | Loads activated PHP snippets; each still needs manual activation in Sandbox | | Pause all scheduled runs | Off | Skips every recurring task; schedules are kept | If Action Scheduler is not installed, this tab warns that WP-Cron is in use and recommends a server cron calling `wp-cron.php` every 5 minutes. ## Onboarding The first-steps checklist: activate the license, connect a provider, pick models, run **Site health summary**, open AI Chat. **Hide the onboarding banner** when done. ## License Shows whether this site has an active license. Activation and renewal are handled by Freemius from the **Account** screen in the WP AI Manager menu. Without a license, Chat, Tasks and their REST routes are gated. ## Other sections * **External MCP**: server status, authentication, connected apps and client setup. See [External MCP connections](/documentation/reference-and-help/external-mcp.md). * **MCP log**: recent requests from external MCP clients. * **Sandbox**: AI-generated Elementor widgets and PHP snippets awaiting review. See [Sandbox](/documentation/reference-and-help/sandbox.md). * **Modules**: switch Redirects, SVG support, Image optimization, Prompts and Brand Kits on or off. * **Help and changelog**: release notes for the installed version. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.3techagency.com/documentation/reference-and-help/settings.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.