> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/ai-and-automation.md).

# AI & Automation

AI & Automation reviews your applications with an AI model, using the findings, metrics, configuration and, where allowed, the source code that IZ Suite already collected. It also holds the workspace-wide AI settings: the provider and model, the monthly budgets, the audit trail and which applications AI may see.

Open it from **Workspaces** → **AI & Automation** in the sidebar. Every AI & Automation screen has the same tabs at the top: **AI coverage & findings**, **Usage & budgets**, **Activity & audit** and **AI access**.

{% hint style="info" %}
AI is not licensed separately. Three checks decide whether AI runs:

1. **AI is turned on** for your workspace, with a provider, model and budget (see **Usage & budgets**, or **Turn on AI** in Setup).
2. **AI access** allows it for the organization, environment or application.
3. An enabled **AI review profile** in **Operations** → **Quality Control** applies to the application. Enabled AI profiles run after the assessment, within your budget.
   {% endhint %}

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fyt3OVPrlpEqEHSCX2zzr%2Fv2-ai-review.png?alt=media&amp;token=038d89f3-79b8-48e3-a34c-cc5f09a2c5be" alt="A completed AI review showing what needs your attention"><figcaption></figcaption></figure>

## Screens in AI & Automation

| Page                                                                                                                                                         | What you do there                                                                                             |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------- |
| [AI Coverage & Findings](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/ai-and-automation/ai-coverage-and-findings.md) | See which assets have an AI review, read the results and prepare a new review.                                |
| [Usage & Budgets](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/ai-and-automation/usage-and-budgets.md)               | Choose the AI provider and model, set monthly budgets and per-action limits, and manage provider connections. |
| [Activity & Audit](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/ai-and-automation/activity-and-audit.md)             | See what AI reviews cost and how long they took, and search every recorded AI event.                          |
| [AI Access](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/ai-and-automation/ai-access.md)                             | Choose what applications get by default and add exceptions per organization, environment or application.      |

## How an AI Review Is Decided

1. AI must be turned on for the workspace in [Usage & Budgets](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/ai-and-automation/usage-and-budgets.md).
2. [AI Access](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/ai-and-automation/ai-access.md) decides whether an application may be reviewed and whether its source code may be sent.
3. A review runs only when an [AI review profile](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations/quality-control/ai-review-profiles.md) applies to the asset: a global, platform or asset-level profile.
4. Every model call is reserved against the budget before it is sent and settled afterwards.

{% hint style="warning" %}
You need a role that can view or run AI insights to open these screens. Changing the provider, budgets and AI access needs a role that can edit global settings.
{% endhint %}

## Next Steps

* [Usage & Budgets](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/ai-and-automation/usage-and-budgets.md): turn AI on and set the budget.
* [AI Access](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/ai-and-automation/ai-access.md): decide where AI is used.
* [AI Review Profiles](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations/quality-control/ai-review-profiles.md): define what an AI review checks.


---

# 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://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/workspaces/ai-and-automation.md?ask=<question>&goal=<user_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.
