Xavier can answer from project data, run research, and write into a project when your role allows it. The control panel lets you decide which of those abilities Xavier is allowed to use for you by default, and whether a specific project should use tighter rules.
Voice input is separate: it changes how you ask. Skill controls change what Xavier may do after it understands the request.
Using voice input
Open Xavier anywhere in the app and press the microphone button beside the message box. Speak normally. When the browser finishes a phrase, Xavier adds the transcript to the draft message. You can edit the draft before sending it.
Press the microphone again to stop listening.
If you do not see the microphone button, that browser does not support the Web Speech API. Type your question instead, or use a browser that supports speech recognition.
If the browser asks for microphone permission, allow it for PageOptimized. If you block it, Xavier shows a microphone access message and voice input stays off until you change the browser permission.
Where the controls live
Open:
Project settings -> Xavier
There are two layers.
Your Xavier defaults apply to you across projects. Use this for your normal comfort level: for example, allow Xavier to read data and diagnose issues, but not create tasks or add tracked prompts.
This project can either follow your defaults or use its own controls. Turn off "Follow my default Xavier permissions" when one project needs different rules.
Allow all vs choose skills
Allow all means Xavier can use every skill group your account role already permits. It does not override your workspace or project role.
Choose skills lets you select specific skill groups. Anything unchecked is blocked server-side. Xavier may still answer with the tools that remain allowed, but it cannot quietly run the disabled workflow.
What each skill group allows
Product help — answer questions about PageOptimized, your account context, and help articles.
Website reading — map and read pages from the project site, competitors, or reference URLs.
Project admin — list projects and create a new project from Xavier.
Keyword and market research — research keywords, SERPs, competitors, local results, and domain opportunities.
Planning and trackers — save keywords, update keyword plans, add rank-tracking keywords, and manage tracked AI prompts.
Analytics and diagnosis — read Search Console, GA4, insights, work queues, and traffic or content diagnoses.
Audits and monitoring — run audits, inspect URLs, read audit results, site speed, timelines, and content changes.
Backlinks and outreach — review backlink profiles, assess prospects, and create or update outreach queues.
Content workflow and brand — read, create, and update content tasks, plus review or draft brand records.
What happens when a skill is blocked
Xavier receives a tool-level block and is told not to retry that tool. It should continue with allowed tools or tell you that a project admin can change the setting in Project settings -> Xavier.
The block is recorded in the project activity log as a Xavier event, so admins can see what was attempted and why it did not run.
What these controls do not change
They do not replace user roles. A viewer cannot make Xavier write into a project just by enabling a skill.
They do not change credit budgets. If an allowed skill spends credits, the normal estimates, budgets, and usage ledger still apply.
They do not make Xavier browse the open web. Website reading is limited to the page-reading tools Xavier actually has.
Good setups
Solo owner — leave defaults on Allow all, then use project overrides only for sensitive clients.
Agency specialist — allow analytics, diagnosis, audit reading, keyword research, and website reading. Disable project admin and writing-heavy workflow groups unless you want Xavier changing plans and queues.
Client-facing workspace — keep the project override strict: product help, analytics, audit reading, and website reading are usually enough for Q&A without letting Xavier create work.
Contractor project — use the contractor's project role for access, then use Xavier controls to limit which workflows their Xavier can run inside that project.
Related
- What Xavier can and cannot do
- People and access
- Credit budgets