Manage Statbot access

Enable Statbot for a project, configure project and role MCP permissions, and resolve blocked project-data or write requests.

Early Access

This feature is in Early Access. During this time, aspects of the functionality may still be developed, and this documentation may not always be up to date. If you have any questions, contact Statsig Support.

Project administrators control whether members can open Statbot and which MCP access the project permits. Role permissions further restrict what each member can read or change. Enabling Statbot doesn't grant permission to read project data or edit configurations.

You need project administrator permissions to change the settings described on this page. If you aren't an administrator, share the blocked request with your project administrator.

Enable or disable Statbot

Open Settings > AI Features in the Statsig Console.
Find Statbot (AI).
Turn the setting on to enable the assistant or off to disable it for the project.

Some projects display the older label Statsig AI Assistant. Other AI advisor settings control their respective features separately. The All Advisors control includes the assistant along with the advisors shown on the settings page.

Configure project data access

Statbot uses Statsig MCP to access project resources. Statbot's effective access is the more restrictive of the project's maximum MCP scope and the user's role MCP access. Resource permissions and review requirements also apply.

Open Settings > Roles.
Edit Default Project MCP Scope and choose the maximum access permitted for the project.
Review the affected member's role MCP access and set it to the access that role needs.
Verify that the role also permits the requested action on the resource type.
Ask the member to request the action again in Statbot.

Effective MCP access	What Statbot can do
No access	Answer documentation questions without reading project resources through MCP.
Read only	Read permitted project resources, with no create or edit actions.
Read and write	Read resources and propose permitted changes for confirmation.

Both project and role MCP settings must allow read and write for Statbot to propose executable write actions. A role with no create or edit permission for a resource still can't perform that action, even when its MCP setting permits writes. For role configuration, go to Project Access Management.

Statbot uses your signed-in identity for project actions. You don't paste an API key into the chat or configure an external MCP client to use Statbot in the Console.

Resolve a permission-blocked request

If Statbot can't read project data, check that the project and role MCP settings allow at least read access. The member also needs permission to read the resource.

If Statbot can't create or edit, check that the project and role MCP settings allow read and write. The member also needs the required resource permissions. A blocked draft records the request but doesn't validate or apply a change.

After changing permissions, ask Statbot to try again. A write request needs a new proposal and confirmation. Statbot rechecks permissions when it applies the proposal.

Keep review requirements

MCP write access doesn't bypass your project's review policies. A confirmed Statbot action can submit a review request. The change still needs reviewer approval and a commit before it takes effect. Follow Create and edit with Statbot for that workflow.

AI controls and privacy

Turning off Statbot controls the in-Console assistant for the project. It doesn't establish a data-retention policy or replace the controls for other AI features.

For Statsig's AI data-handling, model-training, and subprocessor policies, go to AI Governance, Security & Privacy. Contact your Statsig account team about broader AI opt-out requirements or data-handling questions specific to your organization.

Was this helpful?