> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/product-guides-and-integrations/product-guides/ai-features/ai-features-control-center.md).

# AI Features Control Center

Manage every AI feature on your workspace from one page. Turn Bug Grouping, Opportunities, and Survey AI features on or off, with role-based access.

## Overview

The **AI Features Control Center** is a single page inside your workspace settings where owners and admins turn Luciq's AI features on or off. Bug Grouping, Opportunities, and Survey AI features each have their own section on the page, so you no longer opt in from a different corner of the product for each one.

The page replaces the old per-product opt-in flows. In-product banners still exist and still ask for consent, but every banner now redirects to this page.

## Where to find it

**Settings → Workspace → AI Features Control Center.**

The page opens with three sections, one per AI feature currently governed:

* **Bug Grouping**, including the sub-toggles for Network logs and User Steps.
* **Opportunities**.
* **Survey AI features**, covering AI Summary for survey responses and free-text response groups.

Other squads adding new AI features to Luciq add a section to this page rather than a new banner elsewhere.

## Who can enable or disable AI features

Only **Owners** and **Admins** on the workspace can toggle AI features from this page. **Members** and **Viewers** see the page as read-only, so they can check which AI features are on without being able to change the setting.

## Consent and data handling

Each section carries the same consent language and data-handling notes it did before, unchanged. Turning an AI feature on from this page is functionally identical to turning it on from the old in-product settings. Nothing about how Luciq processes data changed with this rename, only where the toggle lives.

## Enabling an AI feature

1. Sign in as an **Owner** or **Admin**.
2. Open **Settings** in the top-right, then **Workspace**, then **AI Features Control Center**.
3. Expand the section for the feature you want to enable and toggle it on. Review the consent notice inline.
4. If a feature has sub-toggles (for example, Bug Grouping's Network logs and User Steps), configure those in the same section.

Enabling **Opportunities** also enables Survey AI features by default, because Opportunities reads survey responses. You can turn Survey AI features off separately from this page if you do not want the AI summary or free-text response groups to run.

## Related pages

* [Bug Grouping](/product-guides-and-integrations/product-guides/bug-reporting/bug-grouping.md)
* [Opportunities](/product-guides-and-integrations/product-guides/inbox/opportunities.md)
* [In-app Surveys](/product-guides-and-integrations/product-guides/in-app-surveys.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.luciq.ai/product-guides-and-integrations/product-guides/ai-features/ai-features-control-center.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.