> For the complete documentation index, see [llms.txt](https://docs.itoc360.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itoc360.com/mobile-applications/getting-started-with-the-itoc360-mobile-app.md). # Getting started with the ITOC360 mobile app With the ITOC360 mobile app, you can stay on top of incident response wherever you are. View your dashboard at a glance, track incoming incidents, acknowledge or silence alerts, and follow each incident's escalation timeline — all from your phone. Push notifications keep you informed in real time, and critical alerts can break through Do Not Disturb so an urgent incident never goes unnoticed. ### Download the app for iOS Download the ITOC360 app from the App Store. 1. Open the **App Store** on your device. 2. Search for ITOC360 and tap **Get**. 3. Wait for the installation to finish. > App Store link: [ITOC360 on the App Store](https://apps.apple.com/app/itoc360/id6775279282) ### Download the app for Android Install the ITOC360 app from the Google Play Store. 1. Open the **Play Store** on your device. 2. Search for ITOC360 and tap **Install**. 3. Launch the app once the download completes. > Play Store link: [ITOC360 on Google Play](https://play.google.com/store/apps/details?id=com.itoc360.app) ### Login Sign in to your ITOC360 account: 1. Enter your **email** and **password**. 2. Tap **Sign In**. If you don't have an ITOC360 account yet, ask your team administrator for an invitation, or create one from the ITOC360 web application.
### Two-factor authentication If two-factor authentication is enabled on your account, you'll be asked to verify after entering your password. 1. Enter the **6-digit verification code**. 2. Tap **Continue**.
### Enable push notifications Push notifications make sure you're alerted the moment an incident is assigned to you. The first time you open the app, ITOC360 automatically registers your device for push notifications — just tap **Allow** when your device asks for notification permission. Once registered, your device appears as a confirmed **Push** channel under **Settings → Channels**, so there's nothing else to set up. > If you tapped **Don't Allow** by mistake, enable notifications for itoc360 in your device's system settings, then reopen the app. ### Dashboard After signing in, the dashboard gives you an at-a-glance overview of your environment: * **Total Alerts**, **Total Incidents**, **Total Users**, and **Total Sources**, each with a recent activity trend. * **Open incidents** — a quick count of currently open incidents, with a **View** shortcut. * **Recent Incidents** — the latest incidents with their status and source. Tap **See All** to open the full list.
### View incidents Tap **Incidents** in the bottom navigation bar to see all incidents. Each entry shows the incident ID, the source that triggered it, the source type (for example Zabbix), the current status, and when it was last updated. Use the filter icon in the top-right corner to narrow the list. Tap any incident to open its details.
### Respond to an incident Opening an incident shows its ID, title, originating source, and current status. From here you can: * **Acknowledge** — let your team know you're on it and pause further escalation. * **Silence Alert** — temporarily suppress notifications for the alert (see below). The **Activities** tab shows the incident's full history: created, triggered, escalated, and closed events with timestamps.
### Follow the escalation timeline Open the **Timeline** tab inside an incident to see how it escalated, level by level. Each escalation level shows its scheduled, started, and completed times, along with every notification that was sent — including the recipient and the channel used (email, SMS, or phone).
### Silence an alert Silencing lets you temporarily stop notifications for an alert without closing the incident. While silenced, the alert still appears, but the incident cannot be opened and no one receives a notification. 1. Open the incident and tap **Silence Alert**. 2. Choose a **duration**: 15m, 1h, 4h, 24h, or **Custom**. 3. Optionally add a **description** explaining why you're silencing it. 4. Tap **Silence**.
### Manage notification channels Notification channels are the addresses and devices ITOC360 uses to reach you. Open **Settings → Channels** to see your channels. Each one shows its type (push, phone, SMS, or email), its value, and its confirmation status. #### Add a channel 1. On the **Channels** screen, tap the **+** button. 2. Choose a **Type**: Email, Phone, SMS, or Push. 3. Enter a **Label** and the **Value** (for example, an email address or phone number). 4. Select a **Locale** (English or Turkish). 5. Tap **Add channel**.
### Settings The **Settings** tab gives you access to your account and preferences: * **Channels** — manage your notification channels. * **One-Time Password (OTP)** — manage two-factor authentication. * **Dark mode** — switch between light and dark appearance. * **Documentations**, **Terms of Service**, and **Privacy Policy** under Helpful Resources.
--- # 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.itoc360.com/mobile-applications/getting-started-with-the-itoc360-mobile-app.md?ask=&goal= ``` `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.