> ## Documentation Index > Fetch the complete documentation index at: https://docs.usestealth.dev/llms.txt > Use this file to discover all available pages before exploring further. # Control Center > Choose which networks and clients Stealth monitors, follow each network's status and set the organization's alert rules. The **Control Center** is where you decide what Stealth watches and what becomes an alert. It has three tabs: **Networks**, **Clients** (with the **Defaults** above the client list) and **Alerts**. The page opens on **Networks**, and the address keeps the open tab, so a link or the back button returns to it. Everyone in the organization can open it, but only **Owners** and **Administrators** can change it. Members see **On** and **Off** instead of switches. ## How it works * A client is monitored when **its network is on and the client is on**. * Monitoring decides whether new incidents can open. Data collection never stops, so the history has no gaps when you turn something back on. * When you turn a network or client off, its open incidents keep being followed until they are resolved. Their updates still reach the bell and webhooks, but no longer email. * Each client belongs to a category, and each category has a default: **Brazil** is on, **Global** and **Apps** are off. A client you switch by hand keeps your choice when the default changes. ## What you see ### Networks The summary shows how many networks are monitored and how many have a problem, and the time of the **Last check**. While networks are loading, it counts them instead: how many are ready, how many are loading and how many the connected Google account cannot see, with a bar of the networks ready and either about how much time is left or when the next networks start loading. Right after you connect Google Ad Manager, reconnect an account, add another Google account or save the network selection, a line at the top says what happened and how many networks Stealth is reading. Close it with the **X**. **Check now** asks for a new check outside the hourly schedule. While a check is in progress, the button reads **Checking…** and stays off. It starts within 5 minutes. A new request is refused while a check is in progress or if one was requested in the last 10 minutes. A requested check refreshes the data and can run the daily rules. The hourly rules run only in the regular hourly check. Each network shows its name and code (which opens it in Google Ad Manager), an on/off switch, how many of its clients are monitored and its stage: | Stage | Meaning | | - | - | | **Preparing** | Waiting for the first check, with its time. It starts within 5 minutes after you choose the network. During the check, the tile says which report is running. | | **Loading history** | Loading the last 28 days, with the progress in days and, from the second day loaded, about how much time is left. | | **Monitoring** | Working normally, with the time of the latest data. | | **No recent data** | Stealth could not read the network's Google Ad Manager reports for more than 3 hours. | | **Check failed** | The last check failed. It runs again in the next check. | | **No access from this Google account** | The connected Google account cannot see the network. Choose **Stop reading** to take it out of the selection (its history is kept), or **Connect another Google account** to add an account that has access (the network then moves to it). The tile also says how to fix it: an admin of the network adds the connected account in **Admin > Access & authorization > Users** in Google Ad Manager. | | **Connection revoked** | The Google permission was removed. Choose **Reconnect**. | When a network is off, none of its clients is monitored. When it is on again, each client returns to its own setting. Each network also shows the state of its hourly refresh: | Line | Meaning | | - | - | | **Updating now** | Stealth is reading the network's reports right now. | | **Updated at 12:20** | The time the last refresh finished. | | **Delayed, next try at 13:20** | In amber: the last refresh failed, or the expected one did not happen on time. Stealth tries again at the time shown. A network still waiting for its first check never shows it. | The progress and the refresh state update on their own, within about 30 seconds, without reloading the page. **Not monitored** lists the networks the Google account can access that you left out of the selection. Stealth does not read them. **Choose networks** opens the selection, where you can add them. See [Connect Google Ad Manager](https://docs.usestealth.dev/en/getting-started/connect-google-ad-manager.md#choose-the-networks). ### Defaults | Default | Clients it covers | | - | - | | **Monitor clients in Brazil** | Clients that are neither apps nor from the Global team. On by default. | | **Monitor Global team clients** | Clients whose ad units sit under a Global team seller ID in Google Ad Manager. Off by default. | | **Monitor apps** | Clients whose ad units are mostly mobile apps (at least 80% of them). Off by default. | A default applies to every client in the category, except those set by hand. ### Clients The list of clients, 25 per page, with search, filters (**Category**, **Monitoring**, **Network**) and the columns **Client**, **Network**, **Category**, **Setting** and **Monitored**. **Setting** says **Category default**, **Set by hand** (with who and when) or **Network off**. Select several clients to **Monitor**, **Stop monitoring** or **Reset to default**. Resetting removes the hand-set mark and applies the current default. ### Alerts **Organization Default** sets what becomes an alert for everyone: | Setting | Options | Default | | - | - | - | | Events | **New drop**, **Drop got worse**, **Back to normal** | All three on | | **Minimum severity** | **Critical**, **Attention** or **Light** | **Light** | | **Mandatory** | **None**, **Critical only**, **Critical and Attention** | **Critical only** | Members cannot turn off mandatory alerts. They only choose the channel. **Exceptions** replace the default for one network, client, format or ad unit. Each exception either mutes alerts (**Mute**) or sets another **Minimum severity**, with a **Duration** of **No expiry**, **24 hours**, **7 days** or **Until a date**. When more than one exception matches, the most specific one wins: ad unit, then format, then client, then network. See [Alerts and notifications](https://docs.usestealth.dev/en/alerts/overview.md) for how these rules combine with each person's preferences. The rules above apply to revenue drops. Below them, **Health and Opportunities** has one switch for each: * **Health alerts** (on by default): critical problems by email right away, the rest in the morning summary at 9 AM. Light ones stay on the **Health** screen. A **Mute** exception on a network, client or ad unit also mutes its Health findings. The minimum severity and the format exceptions do not apply to Health. See [Health](https://docs.usestealth.dev/en/screens/health.md). * **Opportunities alerts** (off by default): on Mondays after the weekly calculation, only new items with high or medium confidence. Nothing is sent when there are none. Turning a switch off stops that area's emails and bell items for everyone in the organization. Each person then chooses the channels in **Settings > Notifications**. ## FAQ > [accordion] Why are Global and app clients off by default? > > So that the first alerts focus on the sites your team manages directly. Turn the category on in **Defaults**, or turn on single clients in **Clients**, if they matter to you. > [accordion] Does turning a client off delete its data? > > No. Data collection continues. Only new incidents stop opening. > [accordion] Should I mute or turn off monitoring? > > Mute when you want the incidents but not the alerts, for example during a planned change. Turn monitoring off when the client should not be followed at all. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.