> 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/operations.md).

# Operations

The **Operations** group in the sidebar holds the screens that every workspace relies on: the quality standards that assessments are judged against, the scheduled work that collects and assesses applications, and the updates IZ Suite sends to you. Each screen shows only what your roles allow.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FkWnpLgq9STz1ycPqLB8l%2Fv2-ops-sidebar.png?alt=media&amp;token=2051489a-17a7-4046-af58-3228a68926f9" alt="Operations group in the sidebar with Quality Control, Schedules and Notifications"><figcaption></figcaption></figure>

| Menu                                                                                                                       | What it is for                                                                                                                           |
| -------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| [Quality Control](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations/quality-control.md) | Quality gates, AI review profiles, customer requirements, quality and metric profiles, quality and metric rules, and security standards. |
| [Schedules](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations/schedules.md)             | Recurring and one-time work, platform scan schedules, and the execution history of every run.                                            |
| [Notifications](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations/notifications.md)     | Your updates, the delivery log, your subscriptions and every subscription in the organization.                                           |

## Next Steps

* [Quality Control](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations/quality-control.md): set the standards an application must meet.
* [Schedules](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations/schedules.md): keep collection and assessment running on time.
* [Notifications](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations/notifications.md): choose which updates reach you.


---

# 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/operations.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.
