# incident.io: Help center

## Help center

### Getting started

- [What's incident.io?](https://docs.incident.io/getting-started/what-is-incident-io.md): The all-in-one platform for on-call, incident response, Investigations and status pages.

#### Slack

- [Installing incident.io in 30 seconds](https://docs.incident.io/getting-started/installing.md)
- [Creating a Slack admin for privileged Slack access](https://docs.incident.io/getting-started/slack-admin-setup.md)
- [Why does incident.io need a Slack Owner account?](https://docs.incident.io/getting-started/slack-owner-account.md)
- [What does incident.io need privileged Slack access for?](https://docs.incident.io/getting-started/slack-privileged-access.md)
- [Slack Enterprise Grid](https://docs.incident.io/getting-started/slack-enterprise-grid.md)
- [Slack Enterprise Grid migrations](https://docs.incident.io/getting-started/slack-enterprise-grid-migrations.md)

#### Microsoft Teams

- [Installing incident.io in Microsoft Teams](https://docs.incident.io/getting-started/installing-teams.md)
- [Microsoft's 'admin consent' flow](https://docs.incident.io/getting-started/microsoft-admin-consent-flow.md)
- [Permissions in Microsoft Teams](https://docs.incident.io/getting-started/teams-permissions.md)
- [Using private incidents in Microsoft Teams](https://docs.incident.io/getting-started/teams-private-incidents.md)
- [What to expect on Microsoft Teams](https://docs.incident.io/getting-started/teams-vs-slack.md): Compare what incident.io does on Microsoft Teams with what it does on Slack.
- [Why does incident.io require a communications platform?](https://docs.incident.io/getting-started/why-comms-platform.md)

### Alerts

- [Live call routing](https://docs.incident.io/on-call/live-call-routing.md)
- [Heartbeat monitoring](https://docs.incident.io/alerts/heartbeat-monitoring.md): Detect when a service fails silently

#### Getting started

- [Creating incidents automatically via alerts](https://docs.incident.io/alerts/getting-started.md)
- [Alerts and teams](https://docs.incident.io/alerts/team-routing.md): Route alerts to the right team, and control who can act on them
- [Alert timeline](https://docs.incident.io/alerts/alert-timeline.md)
- [Alert notes](https://docs.incident.io/alerts/alert-notes.md): Document investigations, hand over context, and record actions taken on alerts — without needing to create an incident.
- [Attributes and Priorities](https://docs.incident.io/alerts/attributes-and-priorities.md)
- [Extracting JSON alert data](https://docs.incident.io/alerts/json-alert-data.md)
- [Alert grouping](https://docs.incident.io/alerts/grouping-alerts.md): Group related alerts into an alert group so you can triage, escalate and attach them to incidents as one.
- [Alert attribute merge strategies](https://docs.incident.io/alerts/merge-strategies.md): Control how your alert data is captured and updated over time using attributes and merge strategies.
- [Customizing alert messages](https://docs.incident.io/alerts/message-customization.md): Control which information is displayed in alert messages sent to Slack or Teams channels.
- [Dynamically setting an escalation path](https://docs.incident.io/alerts/dynamic-escalation.md)
- [Creating escalations and incidents from alerts](https://docs.incident.io/alerts/escalations-from-alerts.md)
- [Incident templates](https://docs.incident.io/alerts/incident-templates.md): Reuse a single set of incident defaults across every alert route.
- [Priorities in Alerts and On-call](https://docs.incident.io/alerts/priorities.md)
- [Routing alerts by priority using alert source configs](https://docs.incident.io/alerts/priority-routing.md)
- [Routing private alerts to escalate and create incidents](https://docs.incident.io/alerts/private-incidents.md)
- [Sending alerts to Slack channels](https://docs.incident.io/alerts/slack-channels.md)
- [Maintenance windows](https://docs.incident.io/alerts/maintenance-windows.md)

#### Alert sources

- [What alert sources are supported?](https://docs.incident.io/alerts/alert-sources.md): Every monitoring, error tracking, and ticketing tool incident.io can turn into alerts.
- [Alert ingestion rate limits](https://docs.incident.io/alerts/rate-limits.md): How much alert traffic each source accepts, and how to give a busy source more headroom.

##### Set up guides

- [Adding BigPanda as an alert source](https://docs.incident.io/alerts/bigpanda.md): Turn BigPanda incidents into incident.io alerts, with two-way resolution
- [Adding Chronosphere as an alert source](https://docs.incident.io/alerts/chronosphere.md)
- [Adding ClickStack as an alert source](https://docs.incident.io/alerts/clickstack.md): Turn ClickStack observability alerts into pages and incidents in incident.io.
- [Crowdstrike Falcon](https://docs.incident.io/alerts/crowdstrike-falcon.md)
- [Adding Dash0 as an alert source](https://docs.incident.io/alerts/dash0.md): Turn Dash0 check rule notifications into pages and incidents in incident.io.
- [Custom HTTP alert sources](https://docs.incident.io/alerts/custom-http-sources.md)
- [Email alert sources](https://docs.incident.io/alerts/email-sources.md): Turn inbound emails into structured alerts, with optional JavaScript to extract the fields you need.
- [Adding Icinga 2 as an alert source](https://docs.incident.io/alerts/icinga2.md): Turn Icinga 2 host and service notifications into pages and incidents, and close them out on recovery.
- [Adding Monte Carlo as an alert source](https://docs.incident.io/alerts/monte-carlo.md)
- [Adding Nagios as an Alert Source](https://docs.incident.io/alerts/nagios.md)
- [Adding Panther as an Alert Source](https://docs.incident.io/alerts/panther.md)
- [Adding ServiceNow as an alert source](https://docs.incident.io/alerts/servicenow.md): Turn ServiceNow incidents into incident.io alerts using the ServiceNow app
- [Adding SolarWinds AppOptics as an alert source](https://docs.incident.io/alerts/solarwinds.md)
- [Adding Uptime.com as an alert source](https://docs.incident.io/alerts/uptime.md)

#### Alert deduplication

- [What is Alert Deduplication?](https://docs.incident.io/alerts/deduplication.md)
- [HTTP Alert Sources and Array Payloads](https://docs.incident.io/alerts/json-array-troubleshooting.md)
- [Why are some of my Datadog alerts not appearing in incident.io?](https://docs.incident.io/alerts/datadog-issues.md)
- [Why are my Prometheus Alertmanager alerts not appearing in incident.io?](https://docs.incident.io/alerts/prometheus-issues.md)
- [Why am I not receiving subsequent Sentry alert notifications?](https://docs.incident.io/alerts/sentry-dedup.md)
- [Why aren't my Grafana alerts appearing within incident.io?](https://docs.incident.io/alerts/why-isn-t-my-grafana-test-alert-triggering-multiple-times.md)

#### FAQs

- [Alert Insights](https://docs.incident.io/alerts/alert-insights.md)
- [Can I manually attach alerts to an existing incident?](https://docs.incident.io/alerts/attach-alerts.md)
- [Maintenance windows](https://docs.incident.io/alerts/maintenance-windows.md)
- [Why is an alert missing an attribute?](https://docs.incident.io/alerts/missing-attributes.md)
- [How do I map alert severities to incident.io alert priorities?](https://docs.incident.io/alerts/severity-mapping.md)

### On-call

- [On-call Readiness Insights](https://docs.incident.io/on-call/on-call-readiness-insights.md)
- [Create an on-call pay report](https://docs.incident.io/on-call/pay-report.md)

#### Getting started

- [Getting started with On-call](https://docs.incident.io/on-call/getting-started.md)
- [What's included in On-call](https://docs.incident.io/on-call/whats-included.md): Find the on-call feature you need, and the page that explains it.
- [Get started as an On-call responder](https://docs.incident.io/on-call/responder-guide.md)
- [Creating incidents manually](https://docs.incident.io/on-call/manual-incidents.md)
- [Using Catalog with On-call](https://docs.incident.io/on-call/catalog-integration.md)

#### Schedules

- [Building schedules](https://docs.incident.io/on-call/building-schedules.md)
- [Importing and duplicating schedules](https://docs.incident.io/on-call/importing-schedules.md)
- [Can I change the timezone of an on-call schedule?](https://docs.incident.io/on-call/change-timezone.md)
- [Sync on-call shifts to your calendar](https://docs.incident.io/on-call/shift-calendar-feeds.md): See your on-call shifts in Google Calendar, Outlook, or any calendar app that can subscribe to a feed
- [Can I sync or link multiple on-call schedules together?](https://docs.incident.io/on-call/link-schedules.md)
- [Mirroring schedules to PagerDuty](https://docs.incident.io/on-call/mirroring-schedules-to-pagerduty.md)
- [How do I remove someone from an on-call schedule rotation?](https://docs.incident.io/on-call/remove-from-rotation.md)
- [Rotation calculation in Schedules](https://docs.incident.io/on-call/rotation-calculation.md)
- [How do I set up Slack notifications for on-call schedule changes?](https://docs.incident.io/on-call/slack-schedule-notifications.md)
- [Syncing schedules to Slack user groups](https://docs.incident.io/on-call/sync-slack-groups.md): Keep Slack user groups in sync with your on-call schedules.

##### Holidays & PTO

- [Holidays in On-call schedules](https://docs.incident.io/on-call/holidays.md): See your team's holidays and time off on your On-call schedule, and arrange cover in advance
- [Public holidays](https://docs.incident.io/on-call/public-holidays.md): Subscribe to one or more countries' public holidays, per schedule
- [Import holidays with calendar feeds](https://docs.incident.io/on-call/calendar-feeds.md): Import your team's time-off from any calendar or HRIS that provides an iCal feed
- [Direct HRIS integrations](https://docs.incident.io/on-call/direct-hris-integrations.md): Connect Workday, HiBob, or BambooHR directly to bring in your team's time off
- [Acting on time off](https://docs.incident.io/on-call/acting-on-holidays.md): Arrange cover for a holiday with an override, or flag upcoming overlaps with a vacation policy
- [Connect Workday](https://docs.incident.io/on-call/hris-workday.md): Bring your team's time-off into On-call schedules from Workday
- [Connect HiBob](https://docs.incident.io/on-call/hris-hibob.md): Bring your team's time-off into On-call schedules from HiBob
- [Connect BambooHR](https://docs.incident.io/on-call/hris-bamboohr.md): Bring your team's time-off into On-call schedules from BambooHR

#### Escalation paths

- [Smart escalation paths](https://docs.incident.io/on-call/escalation-paths.md)
- [Escalation status definitions](https://docs.incident.io/on-call/escalation-statuses.md)
- [Escalations with On-call](https://docs.incident.io/on-call/escalations.md)
- [How do I escalate manually?](https://docs.incident.io/on-call/manual-escalation.md)
- [Delaying an out of hours escalation until working hours begin](https://docs.incident.io/on-call/out-of-hours.md)
- [Round Robin in Escalation paths](https://docs.incident.io/on-call/round-robin.md)
- [Snoozing escalations](https://docs.incident.io/on-call/snoozing-escalations.md): Temporarily snooze an escalation when you need more time before responding.
- [Repeating acknowledged escalations](https://docs.incident.io/on-call/repeating-acknowledged-escalations.md): Automatically repeat an acknowledged escalation while the associated alert is still firing.
- [Wait for investigation](https://docs.incident.io/on-call/wait-for-investigation.md): Hold an escalation while AI investigates, so responders are paged with context

##### Reassigning escalations

- [Reassigning escalations](https://docs.incident.io/on-call/reassignments.md): Move an escalation to different responders, either manually or automatically.
- [Reassigning escalations manually](https://docs.incident.io/on-call/reassigning-escalations.md): Move an escalation to a different path or set of people when the wrong team was paged.
- [Reassigning escalation paths](https://docs.incident.io/on-call/automatically-reassign-escalations.md): Hand an unacknowledged escalation to another path automatically.

#### Being on call

- [Setting up notifications on iOS and Android](https://docs.incident.io/on-call/mobile-notifications.md)
- [Setting up notifications on Android](https://docs.incident.io/on-call/android-notifications.md)
- [Setting up notifications on iOS](https://docs.incident.io/on-call/ios-notifications.md)
- [On-call notifications and preferences](https://docs.incident.io/on-call/notifications.md)
- [Test your on-call notifications](https://docs.incident.io/on-call/test-notifications.md): Prove a page will reach you before you get paged for real.
- [On-call notification policies](https://docs.incident.io/on-call/notification-policies.md): Ensure every on-call responder is properly set up to receive pages.
- [Bulk acknowledging escalations](https://docs.incident.io/on-call/bulk-acknowledge.md)
- [What determines if you're on call?](https://docs.incident.io/on-call/determining-on-call.md)
- [Cover me, overrides and schedules](https://docs.incident.io/on-call/overrides.md)
- [Swap shifts](https://docs.incident.io/on-call/shift-swaps.md): Swap an on-call shift with a teammate, or request cover and offer a swap in return.
- [Schedule coverage policies](https://docs.incident.io/on-call/coverage-policies.md): Check that your schedules have someone on call around the clock, and catch gaps before they turn into a missed page.
- [Adding contact methods for another user](https://docs.incident.io/on-call/contact-methods.md)
- [Supported countries for On-call notifications](https://docs.incident.io/on-call/supported-countries.md)

##### On-call in China

- [On-call in China](https://docs.incident.io/on-call/china-on-call.md): How on-call notifications work for responders in Mainland China.
- [Mobile app in China](https://docs.incident.io/on-call/china-mobile-app.md): Setting up the incident.io mobile app for responders in Mainland China.
- [SMS and voice in China](https://docs.incident.io/on-call/china-sms-and-voice.md): How SMS and voice notifications work for responders in Mainland China.

#### Migration

- [Tools to make migrating from PagerDuty easier](https://docs.incident.io/getting-started/migrate-from-pagerduty.md)
- [Tools to make migrating from Opsgenie easier](https://docs.incident.io/getting-started/migrate-from-opsgenie.md)
- [Importing schedules and escalation policies from PagerDuty and OpsGenie](https://docs.incident.io/on-call/import-pagerduty.md)
- [Migrating Datadog monitors to incident.io](https://docs.incident.io/getting-started/migrate-datadog-monitors.md)

#### Importing historical incidents

- [Importing historical incidents](https://docs.incident.io/getting-started/importing-historical-incidents.md): Bring your incident history into incident.io using the API, so your reporting and insights cover more than just the incidents you declare from now on.
- [Importing historical incidents from Blameless](https://docs.incident.io/getting-started/importing-historical-incidents-blameless.md): Bring your incident history from Blameless into incident.io, so your reporting and insights cover more than just the incidents you declare from now on.
- [Importing historical incidents from FireHydrant](https://docs.incident.io/getting-started/importing-historical-incidents-firehydrant.md): Bring your incident history from FireHydrant into incident.io, so your reporting and insights cover more than just the incidents you declare from now on.
- [Importing historical incidents from ServiceNow](https://docs.incident.io/getting-started/importing-historical-incidents-servicenow.md): Bring your incident history from ServiceNow into incident.io, so your reporting and insights cover more than just the incidents you declare from now on.
- [Importing historical incidents from Rootly](https://docs.incident.io/getting-started/importing-historical-incidents-rootly.md): Bring your incident history from Rootly into incident.io, so your reporting and insights cover more than just the incidents you declare from now on.

#### FAQs

- [How do escalation delays work when no one is on-call for a level?](https://docs.incident.io/on-call/escalation-delays.md)
- [Setting up the mobile app in a work profile in Android](https://docs.incident.io/on-call/android-work-profile.md)
- [Can I escalate to multiple levels if the same person is on consecutive escalation paths?](https://docs.incident.io/on-call/consecutive-escalation.md)
- [Can we change the date format in email notifications?](https://docs.incident.io/on-call/email-date-format.md)
- [Understanding priority, urgency, and severity](https://docs.incident.io/on-call/priority-urgency-severity.md)
- [How do I assign on-call roles from schedules to incident roles?](https://docs.incident.io/on-call/schedule-to-incident-roles.md)
- [On-call Shortcuts Cheatsheet](https://docs.incident.io/on-call/shortcuts.md)
- [Why can't I ack my page via SMS?](https://docs.incident.io/on-call/sms-ack-issues.md)
- [Why did verifying my WhatsApp number fail?](https://docs.incident.io/on-call/whatsapp-verification-issues.md): What to do if verifying a WhatsApp number for on-call notifications fails.
- [How do I unmanage a Terraform-controlled schedule in the dashboard?](https://docs.incident.io/on-call/unmanage-terraform-schedule.md)

### Incident response

- [Incident streams](https://docs.incident.io/incidents/streams.md)

#### Creating incidents

- [Declaring incidents](https://docs.incident.io/incidents/declaring.md)
- [Pre-filling 'declare incident' fields using URL parameters](https://docs.incident.io/incidents/url-parameters.md)
- [Decision Flows](https://docs.incident.io/incidents/decision-flows.md)
- [Incidents without channels](https://docs.incident.io/incidents/channelless-incidents.md)
- [Customizing your incident creation form using Custom Fields](https://docs.incident.io/incidents/custom-fields.md)
- [Incident Modes](https://docs.incident.io/incidents/incident-modes.md)
- [Incident Types](https://docs.incident.io/incidents/incident-types.md)
- [Inviting teammates to incidents](https://docs.incident.io/incidents/inviting-teammates.md)
- [Incident Lifecycle](https://docs.incident.io/incidents/lifecycle.md)
- [Triaging your incidents](https://docs.incident.io/incidents/triaging.md)

#### Managing incidents

- [Actions](https://docs.incident.io/incidents/actions.md)
- [Quick Actions](https://docs.incident.io/incidents/quick-actions.md)
- [Merging incidents](https://docs.incident.io/incidents/merging.md)
- [How do I add attachments to incidents?](https://docs.incident.io/incidents/attachments.md)
- [Creating custom incident roles](https://docs.incident.io/incidents/custom-roles.md)
- [Keeping your customers in the loop](https://docs.incident.io/incidents/customer-updates.md)
- [Escalating incidents](https://docs.incident.io/incidents/escalating.md)
- [Knowing who's in charge](https://docs.incident.io/incidents/incident-roles.md)
- [Pausing incidents](https://docs.incident.io/incidents/pausing.md)
- [Setting reminders and suggestions in incident.io](https://docs.incident.io/incidents/reminders.md)
- [Rule-based suggestions](https://docs.incident.io/incidents/rule-based-suggestions.md)
- [Shortcuts cheatsheet](https://docs.incident.io/incidents/shortcuts.md)
- [Sharing status updates with your team](https://docs.incident.io/incidents/status-updates.md)
- [Keeping track of who's doing what](https://docs.incident.io/incidents/task-tracking.md)
- [Updating an incident's status and details](https://docs.incident.io/incidents/updating-incidents.md)
- [Creating and linking video call URLs for digital 'war rooms'](https://docs.incident.io/incidents/video-calls.md)

#### Private incidents

- [Private incidents](https://docs.incident.io/incidents/private-incidents.md): Lock sensitive incidents down to the people and teams who need them.
- [Announcing private incidents](https://docs.incident.io/incidents/announcing-private-incidents.md): Announce private incidents to a controlled audience.
- [Private incident streams](https://docs.incident.io/incidents/private-streams.md)

#### FAQs

- [Alerts and automatic incident creation](https://docs.incident.io/incidents/auto-create.md)
- [Can we change where incidents get announced?](https://docs.incident.io/incidents/change-announcements.md)
- [How do I change a custom field from fixed list to user-defined options?](https://docs.incident.io/incidents/change-field-type.md)
- [Can we create conditional Custom Fields?](https://docs.incident.io/incidents/conditional-fields.md)
- [Using incident.io and Slack to convert public channels to private ones](https://docs.incident.io/incidents/convert-channels.md)
- [Can we create incidents or actions from an existing Slack message?](https://docs.incident.io/incidents/create-from-slack.md)
- [Can we create incidents from a Linear ticket?](https://docs.incident.io/incidents/create-from-tickets.md)
- [Can I delete or hide an incident?](https://docs.incident.io/incidents/delete-incidents.md)
- [How does the duplicate incident prevention feature work?](https://docs.incident.io/incidents/duplicate-prevention.md)
- [Can we edit the timeline?](https://docs.incident.io/incidents/edit-timeline.md)
- [How to use images in incidents](https://docs.incident.io/incidents/incident-images.md)
- [Importing existing incident channels to incident.io](https://docs.incident.io/incidents/import-channels.md)
- [How does the 'Rate this incident' feedback feature work?](https://docs.incident.io/incidents/incident-feedback.md)
- [Active Participants vs Observers](https://docs.incident.io/incidents/participants-vs-observers.md)
- [Workflows on private incidents](https://docs.incident.io/incidents/private-incident-workflows.md): Automate response on private incidents, including granting team access and announcing them.
- [How do I convert a private Slack incident channel to public?](https://docs.incident.io/incidents/private-to-public.md)
- [Can I rename an incident?](https://docs.incident.io/incidents/rename-incidents.md)
- [Can I reopen an incident?](https://docs.incident.io/incidents/reopen-incidents.md)
- [Can I create retrospective incidents?](https://docs.incident.io/incidents/retrospective-incidents.md)
- [Why can't I see all my team in the drop-down of incident roles?](https://docs.incident.io/incidents/role-dropdown.md)
- [Test incidents](https://docs.incident.io/incidents/test-incidents.md): Run practice incidents without affecting your real data or notifying the whole company.
- [What's happened to my Slack bookmarks?](https://docs.incident.io/incidents/slack-bookmarks.md)
- [Can I set a custom field directly from Slack using a command?](https://docs.incident.io/incidents/slack-custom-fields.md)
- [Can multi-channel slack guest users interact with the incident.io bot?](https://docs.incident.io/incidents/slack-guest-users.md)
- [Subscribing to Incidents](https://docs.incident.io/incidents/subscribing.md)
- [Why are my incidents not being announced?](https://docs.incident.io/incidents/test-incident-announcements.md)

### Post-incident

- [Define your post-incident process using the Post-incident Flow](https://docs.incident.io/post-incident/post-incident-flow.md)
- [Setting due dates and reminders for your post-incident tasks](https://docs.incident.io/post-incident/due-dates.md)
- [Setting a default assignee for your post-incident tasks](https://docs.incident.io/post-incident/default-assignees.md)
- [Generating your incident timeline](https://docs.incident.io/post-incident/timeline.md)
- [What is a debrief?](https://docs.incident.io/post-incident/debriefs.md)
- [Shoutouts](https://docs.incident.io/post-incident/shoutouts.md)

#### Post-mortems

- [Post-mortems](https://docs.incident.io/post-incident/postmortems-overview.md): Turn incidents into learnings with collaborative, AI-native post-mortem documents.
- [Writing & editing post-mortems](https://docs.incident.io/post-incident/writing-and-editing.md): A collaborative editor with deep access to your incident data, catalog, and integrations.
- [Post-mortem templates](https://docs.incident.io/post-incident/postmortem-templates.md): Define the structure of your post-mortems with configurable sections, help text, and AI instructions.
- [AI-native writing](https://docs.incident.io/post-incident/postmortem-ai.md): Generate first drafts, get inline review suggestions, and redraft sections with AI.
- [Scribe for post-mortems](https://docs.incident.io/post-incident/postmortem-scribe.md): AI note-taker that joins your debrief call and feeds the transcript into your post-mortem.
- [Sharing & exporting post-mortems](https://docs.incident.io/post-incident/postmortem-sharing-and-exporting.md): Share your post-mortem via Slack and export it to Google Docs, Notion, Confluence, or SharePoint.
- [Managing your post-mortems](https://docs.incident.io/post-incident/postmortem-management.md): Track post-mortem completion across your org with list views, the post-incident flow, and policies.
- [Automating post-mortems with workflows](https://docs.incident.io/post-incident/postmortem-workflows.md): Use workflows to automate sharing, exporting, and other post-mortem tasks.
- [Post-mortem API](https://docs.incident.io/post-incident/postmortem-api.md): Programmatic access to your post-mortem documents, metadata, and status changes.
- [External post-mortem documents](https://docs.incident.io/post-incident/external-postmortems.md): Write your post-mortems in Google Docs, Confluence, Notion, or SharePoint.

#### Follow-ups

- [Follow-ups](https://docs.incident.io/post-incident/follow-ups.md)
- [Syncing follow-ups with your issue tracker](https://docs.incident.io/post-incident/follow-up-issue-tracker-sync.md): Track follow-ups in the tool your engineers already work in, without anyone updating two systems.
- [Assigning a Priority to Follow-ups](https://docs.incident.io/post-incident/follow-up-priorities.md)
- [Enforcing follow-ups are completed based on priority (policies)](https://docs.incident.io/post-incident/follow-up-policies.md)
- [Follow-ups API](https://docs.incident.io/post-incident/follow-ups-api.md): Programmatic access to your follow-ups, with pagination and filters built for syncing them into your own tools.

### Status pages

- [Introduction to status pages](https://docs.incident.io/status-pages/overview.md)
- [Getting started with customer status pages](https://docs.incident.io/status-pages/customer-overview.md)

#### Public status pages

- [Getting your status page ready to go 'live'](https://docs.incident.io/status-pages/going-live.md)
- [Go-live checklist for your new status page](https://docs.incident.io/status-pages/go-live-checklist.md)
- [How to publish an incident to your status page](https://docs.incident.io/status-pages/publishing-incidents.md)
- [Automatically publishing to your status page](https://docs.incident.io/status-pages/auto-publishing.md)
- [Status page APIs](https://docs.incident.io/status-pages/api.md): Automate status page incidents, maintenance windows, and embed status data in your product.
- [Status Pages incident severity](https://docs.incident.io/status-pages/severity.md)
- [Ordering status page components](https://docs.incident.io/status-pages/component-ordering.md)
- [Status Pages sub-pages](https://docs.incident.io/status-pages/sub-pages.md)
- [Setting up sub-pages](https://docs.incident.io/status-pages/sub-page-setup.md)
- [Status page subscriptions](https://docs.incident.io/status-pages/subscriptions.md)
- [Status Pages maintenance automation](https://docs.incident.io/status-pages/maintenance.md)
- [Control who can publish to your status page](https://docs.incident.io/status-pages/publish-permissions.md)
- [High page view alerts](https://docs.incident.io/status-pages/high-page-views.md)
- [Status Pages: How we calculate uptime](https://docs.incident.io/status-pages/uptime-calculation.md)
- [Backfill uptime history on a new status page](https://docs.incident.io/status-pages/uptime-backfill.md): Remove the empty 'no data' bars on a new status page by backfilling operational history.
- [Displaying metrics on your status page](https://docs.incident.io/status-pages/system-metrics.md): Show visitors real performance data, like response times and uptime, on your public status page.
- [Migrating from Atlassian Statuspage](https://docs.incident.io/status-pages/migrate-from-statuspage.md)

#### Internal status pages

- [Getting started with internal status pages](https://docs.incident.io/status-pages/internal-overview.md)
- [Creating an internal status page](https://docs.incident.io/status-pages/create-internal.md)
- [How to publish an incident to your internal status page](https://docs.incident.io/status-pages/internal-publishing.md)
- [Control who can publish to your internal status page](https://docs.incident.io/status-pages/internal-permissions.md)

#### FAQs

- [Can I customize the appearance of my status page?](https://docs.incident.io/status-pages/customization.md)
- [Can I customize the email sender address for status page email notifications?](https://docs.incident.io/status-pages/email-sender.md)
- [How do I add Google Analytics to my status page?](https://docs.incident.io/status-pages/google-analytics.md)
- [How do I import subscribers from another status page provider?](https://docs.incident.io/status-pages/import-subscribers.md)
- [How do internal status page subscriptions differ from public status page subscriptions?](https://docs.incident.io/status-pages/internal-vs-public-subscriptions.md)
- [Can I create status pages in multiple languages?](https://docs.incident.io/status-pages/multiple-languages.md)
- [Who on our team can create, manage or post to status pages?](https://docs.incident.io/status-pages/permissions.md)
- [How do I remove subscriptions from a status page?](https://docs.incident.io/status-pages/remove-subscriptions.md)
- [What happens to status page incidents when removing components?](https://docs.incident.io/status-pages/removing-components.md)
- [How are subscribers migrated when switching from Atlassian StatusPage?](https://docs.incident.io/status-pages/statuspage-subscriber-migration.md)
- [Is there a limit on the number of Status Page subscribers?](https://docs.incident.io/status-pages/subscriber-limits.md)
- [Can I manage status pages using Terraform or automation?](https://docs.incident.io/status-pages/terraform.md)
- [Can I integrate third-party status pages into my status page?](https://docs.incident.io/status-pages/third-party-integration.md)
- [Can I adjust the time window on the status page?](https://docs.incident.io/status-pages/time-window.md)
- [Does incident.io integrate with WhatsApp or SMS for sending status page updates?](https://docs.incident.io/status-pages/whatsapp.md)

### Nexus

- [Nexus](https://docs.incident.io/nexus/overview.md): Built from your catalog, your incidents, your code, and your telemetry, and sharper with every incident.
- [Catalog](https://docs.incident.io/nexus/catalog.md): Your catalog gives Nexus the map of your systems, services, and ownership.
- [Past incidents](https://docs.incident.io/nexus/past-incidents.md): Find similar incidents and reuse the fixes that worked before.
- [Slack channels](https://docs.incident.io/nexus/slack.md): Give Nexus the real-time context that lives in your Slack.
- [Change events](https://docs.incident.io/nexus/change-events.md): Turn your deploy and change notifications into evidence Nexus can use.
- [Documentation](https://docs.incident.io/nexus/documentation.md): Give Nexus your runbooks and reference docs, so your team can search them from the agent.

#### Code

- [Code](https://docs.incident.io/nexus/code/overview.md): Give Nexus your repositories, so it can find the change that caused an issue, read your code, and draft the fix.
- [Making code changes](https://docs.incident.io/nexus/code/making-code-changes.md): Ask @incident to fix what an investigation found, as a pull request grounded in the investigation.
- [Delegating agents](https://docs.incident.io/nexus/code/delegating-agents.md): Hand code changes to your team's own coding agent instead of incident.io's built-in one.

#### Telemetry

- [Telemetry](https://docs.incident.io/nexus/telemetry/overview.md): Give Nexus the logs, metrics, traces, and dashboards your team relies on.
- [How telemetry works](https://docs.incident.io/nexus/telemetry/how-it-works.md): How Nexus queries your observability stack like an engineer who knows it.
- [Memory](https://docs.incident.io/nexus/telemetry/memory.md): Nexus gets better at querying your telemetry the more it's used.
- [Telemetry access controls](https://docs.incident.io/nexus/telemetry/access-controls.md): Control which teams can manage each telemetry data source, and who can query it.
- [Troubleshooting](https://docs.incident.io/nexus/telemetry/troubleshooting.md): Diagnose a data source that's failing, returning nothing, or asking to be reconnected.
- [AWS](https://docs.incident.io/nexus/telemetry/aws.md): Connect AWS once to give Nexus CloudWatch, EKS, OpenSearch, and your RDS databases.
- [ClickHouse](https://docs.incident.io/nexus/telemetry/clickhouse.md): Query the logs, traces, and metrics your OpenTelemetry pipeline writes into ClickHouse.
- [CloudWatch](https://docs.incident.io/nexus/telemetry/cloudwatch.md): Query your CloudWatch metrics and logs to see how your AWS services behaved during an incident.
- [Coralogix](https://docs.incident.io/nexus/telemetry/coralogix.md): Query your Coralogix logs, metrics, and traces to see what your systems were doing during an incident.
- [CrowdStrike Falcon LogScale](https://docs.incident.io/nexus/telemetry/logscale.md): Query your LogScale logs to see what your systems were doing during an incident.
- [Datadog](https://docs.incident.io/nexus/telemetry/datadog.md): Query your Datadog logs, metrics, traces, and error tracking to see what your systems were doing during an incident.
- [Elasticsearch](https://docs.incident.io/nexus/telemetry/elasticsearch.md): Search your Elasticsearch log indices to see what your services recorded during an incident.
- [Grafana](https://docs.incident.io/nexus/telemetry/grafana.md): Connect Grafana to give Nexus your dashboards and the data sources behind it.
- [Honeycomb](https://docs.incident.io/nexus/telemetry/honeycomb.md): Query your Honeycomb traces and events to see how requests moved through your services during an incident.
- [Kubernetes](https://docs.incident.io/nexus/telemetry/kubernetes.md): See the state of your cluster during an incident: what was running, what was failing, and why.
- [Logz.io](https://docs.incident.io/nexus/telemetry/logzio.md): Search your Logz.io logs and query your metrics to see what your services were doing during an incident.
- [Loki](https://docs.incident.io/nexus/telemetry/loki.md): Query your Loki logs to see what your services were saying during an incident.
- [MySQL](https://docs.incident.io/nexus/telemetry/mysql.md): Query your MySQL database during an investigation to confirm what the data actually shows.
- [New Relic](https://docs.incident.io/nexus/telemetry/new-relic.md): Query your New Relic logs, metrics, and APM traces to see what your systems were doing during an incident.
- [OpenSearch](https://docs.incident.io/nexus/telemetry/opensearch.md): Search your OpenSearch log indices to see what your services recorded during an incident.
- [PostgreSQL](https://docs.incident.io/nexus/telemetry/postgresql.md): Query your PostgreSQL database during an investigation to confirm what the data actually shows.
- [Prometheus](https://docs.incident.io/nexus/telemetry/prometheus.md): Query your Prometheus metrics to see how your services behaved during an incident.
- [Pyroscope](https://docs.incident.io/nexus/telemetry/pyroscope.md): See which code paths burned CPU or allocated memory when an incident hit.
- [Splunk (Enterprise and Cloud Platform)](https://docs.incident.io/nexus/telemetry/splunk.md): Query your Splunk logs and metrics to see what your systems were doing during an incident.
- [Splunk Observability Cloud](https://docs.incident.io/nexus/telemetry/splunk-observability-cloud.md): Query your Splunk Observability Cloud metrics and dashboards to see what your systems were doing during an incident.
- [Sumo Logic](https://docs.incident.io/nexus/telemetry/sumo-logic.md): Query your Sumo Logic logs and metrics to see what your systems were doing during an incident.
- [Tempo](https://docs.incident.io/nexus/telemetry/tempo.md): Query your Tempo traces to see how a request moved through your services during an incident.

##### Google Cloud

- [Google Cloud](https://docs.incident.io/nexus/telemetry/google-cloud.md): Connect Google Cloud once to give Nexus your logs, metrics, traces, and the workloads behind them.
- [Google Cloud Logging](https://docs.incident.io/nexus/telemetry/google-cloud-logging.md): Read what your Google Cloud services logged around the time of an incident.
- [Google Cloud Monitoring](https://docs.incident.io/nexus/telemetry/google-cloud-monitoring.md): Graph what your Google Cloud infrastructure was doing around the time of an incident.
- [Google Cloud Trace](https://docs.incident.io/nexus/telemetry/google-cloud-trace.md): Follow a request across your Google Cloud services to see where it broke.

### Investigations

- [Investigations](https://docs.incident.io/investigations/overview.md): Find the root cause of incidents faster, with evidence you can trust.
- [Getting started](https://docs.incident.io/investigations/getting-started.md): Connect your sources and run your first investigation.
- [How investigations work](https://docs.incident.io/investigations/how-investigations-work.md): From the first alert to a root cause backed by evidence.
- [What investigations can see](https://docs.incident.io/investigations/what-we-can-see.md): The context an investigation reads from inside your incident: the conversation, the call, shared files, and the incident's own details.
- [Third-party dependencies](https://docs.incident.io/investigations/third-party-dependencies.md): Investigations automatically check whether a provider outage explains your incident.
- [Incident channel experience](https://docs.incident.io/investigations/incident-channel-experience.md): What an investigation looks like in your incident channel, and how to talk to it.
- [Measuring accuracy](https://docs.incident.io/investigations/measuring-accuracy.md): How we grade investigations against what really caused your incidents, and use those scores to make them better.
- [Measuring engagement](https://docs.incident.io/investigations/measuring-engagement.md): How we measure the way responders use an investigation: reading it, steering it, and acting on what it finds.
- [Measuring autonomy](https://docs.incident.io/investigations/measuring-diagnosis.md): How much of each incident's diagnosis Investigations drove on its own, and how much faster incidents reach a diagnosis when it leads.
- [Trust and safety](https://docs.incident.io/investigations/trust-and-safety.md): How investigations stay under your control, keep a full record of their work, and stay honest about what they know.
- [Triggering investigations](https://docs.incident.io/investigations/triggering.md): Decide when investigations run, automatically, by condition, or on demand.

### AI features

- [Using @incident](https://docs.incident.io/ai/at-incident.md)
- [macOS app](https://docs.incident.io/ai/desktop-app.md): Download the incident.io desktop app for macOS to respond to incidents from the notch.
- [Remote MCP server](https://docs.incident.io/ai/remote-mcp.md): Ask your AI assistant about incidents, alerts, and on-call without opening the dashboard
- [Slack assistant](https://docs.incident.io/ai/slack-assistant.md): Chat with incident.io's AI agent from anywhere in Slack using the assistant sidebar

#### Suggestions

- [Suggestions](https://docs.incident.io/ai/suggestions.md)
- [AI feature: Suggested summaries](https://docs.incident.io/ai/summaries.md)
- [AI feature: Suggested follow-ups](https://docs.incident.io/ai/follow-ups.md)

#### Scribe & calls

- [Scribe: AI-powered transcription and summarization for incident calls](https://docs.incident.io/ai/scribe.md)
- [Scribe and incident calls](https://docs.incident.io/ai/scribe-overview.md)
- [Manually adding and removing Scribe from your incident calls](https://docs.incident.io/ai/managing-scribe.md)
- [Deleting call notes](https://docs.incident.io/ai/deleting-notes.md)
- [Google Meet: diagnosing common issues](https://docs.incident.io/ai/meet-issues.md)
- [Microsoft Teams calls: diagnosing common issues](https://docs.incident.io/ai/teams-call-issues.md)
- [Zoom: diagnosing common issues](https://docs.incident.io/ai/zoom-issues.md)

### Catalog

- [Using the Catalog](https://docs.incident.io/catalog/catalog-setup.md)

#### Getting started

- [What data should I bring into Catalog?](https://docs.incident.io/catalog/what-data.md)
- [How do I get data into Catalog?](https://docs.incident.io/catalog/importing-data.md)
- [How to re-sync Catalog data](https://docs.incident.io/catalog/resync-data.md)
- [Managing Catalog Types in GitHub](https://docs.incident.io/catalog/github-managed-types.md)
- [Automatically setting custom fields](https://docs.incident.io/catalog/auto-custom-fields.md)
- [Filter custom fields based on another custom field](https://docs.incident.io/catalog/filter-custom-fields.md)

#### Teams

- [Setting up teams](https://docs.incident.io/catalog/teams.md)
- [Team structure](https://docs.incident.io/catalog/team-structure.md): Organize teams into parent and sub-teams to see everything in one place.
- [Team resources](https://docs.incident.io/catalog/team-resources.md): See which resources can be owned by a team, and what that ownership controls
- [Using SCIM to create a Team catalog type](https://docs.incident.io/catalog/scim-teams.md)
- [Teams in Catalog: Migrating from SlackUsers to Users](https://docs.incident.io/catalog/migrate-team-users.md)
- [Teams in incident.io](https://docs.incident.io/catalog/teams-faq.md)
- [Teams in Insights: Troubleshooting](https://docs.incident.io/catalog/teams-insights.md)

#### Integrations

- [Backstage](https://docs.incident.io/catalog/backstage.md)
- [Adding connected users to Catalog](https://docs.incident.io/catalog/connected-users.md)
- [Cortex](https://docs.incident.io/catalog/cortex.md)
- [Datadog](https://docs.incident.io/catalog/datadog.md)
- [Sync Notion databases into Catalog](https://docs.incident.io/catalog/notion.md): Use attributes your teams already keep in Notion, like owners and RTOs, during incidents without exporting by hand.
- [Opslevel](https://docs.incident.io/catalog/opslevel.md)
- [Linking Salesforce Accounts and Opportunities in Catalog](https://docs.incident.io/catalog/salesforce.md)

#### FAQs

- [How do you use enums in the Catalog Importer?](https://docs.incident.io/catalog/enum-imports.md)
- [Managing team memberships outside of incident.io](https://docs.incident.io/catalog/external-memberships.md)

### Workflows

- [Getting started with Workflows](https://docs.incident.io/workflows/getting-started.md)
- [Workflow triggers](https://docs.incident.io/workflows/triggers.md): Find the event that should start your automation, from an incident change to a recurring daily schedule.
- [How to use Workflow Expressions](https://docs.incident.io/workflows/expressions.md)
- [Using loops in Workflows](https://docs.incident.io/workflows/loops.md)
- [Sending a Webhook from a Workflow](https://docs.incident.io/workflows/webhooks.md)
- [Managing workflows in Terraform](https://docs.incident.io/workflows/terraform.md)
- [Advanced settings](https://docs.incident.io/workflows/advanced.md): Covers advanced settings, including how to prevent duplicate workflow runs by controlling how often a workflow fires for the same incident, user, or other resource.

#### FAQs

- [How do I set up a workflow trigger for Slack emoji reactions?](https://docs.incident.io/workflows/emoji-triggers.md)
- [How do I mention the Incident Lead in a message or suggestion?](https://docs.incident.io/workflows/mention-lead.md)
- [How do I tag a Slack user using their Slack username in a workflow?](https://docs.incident.io/workflows/slack-user-tags.md)

### Insights

- [Using Insights](https://docs.incident.io/insights/overview.md)
- [Core dashboards](https://docs.incident.io/insights/core-dashboards.md): Answer pager load, out-of-hours paging, response time and follow-up questions from the dashboards Insights ships with.
- [Supported measures](https://docs.incident.io/insights/supported-measures.md): Every measure you can chart in an Insights panel, including incident volume, MTTR/MTTA duration metrics, alerts, pager load, follow-ups and time spent
- [Insights: Custom Dashboards](https://docs.incident.io/insights/custom-dashboards.md)
- [Saved Views](https://docs.incident.io/insights/saved-views.md)
- [Insights scheduled reports](https://docs.incident.io/insights/scheduled-reports.md)
- [Workload metric calculations](https://docs.incident.io/insights/workload-metrics.md)

### Integrations

- [Using the incident.io CLI](https://docs.incident.io/integrations/cli.md): Manage incidents, alerts, schedules, and more from your terminal with inc, the official incident.io command-line interface.

#### Setup & configuration

- [Using a bot account for integrations](https://docs.incident.io/integrations/bot-account.md): Keep integrations working even after the person who set them up leaves your organization.
- [Using a service account to integrate with Google](https://docs.incident.io/integrations/google-service-account.md): Keep calendar invites, meetings, and documents from being tied to any one person's Google account.
- [Using a service account to integrate with Microsoft Outlook, Teams and SharePoint](https://docs.incident.io/integrations/microsoft-service-account.md): Keep Outlook, Teams, and SharePoint integrations working even after the person who connected them moves on.
- [Allowlisting IP addresses for VCS/on-premise integrations](https://docs.incident.io/integrations/ip-allowlist.md): Give incident.io access to on-premise or IP-restricted systems without opening them up to the wider internet.
- [Webhooks](https://docs.incident.io/integrations/webhooks.md): Get notified the moment something changes in incident.io, so your other tools never fall out of sync.

#### Monitoring

- [Datadog](https://docs.incident.io/integrations/datadog.md): See the Datadog monitor behind an incident without leaving Slack.
- [Using the Grafana Integration](https://docs.incident.io/integrations/grafana.md): Turn Grafana alerts into incidents automatically, with dashboard context on hand when you need it.
- [Sentry](https://docs.incident.io/integrations/sentry.md): Keep error tracking and incident response in sync by linking Sentry issues directly to incidents.

#### Communication

- [Scheduling an event in a specific calendar](https://docs.incident.io/integrations/calendar-events.md): Fix the permission and subscription issues that stop you scheduling events in a shared calendar.
- [Scheduling debriefs in a specific calendar](https://docs.incident.io/integrations/debrief-calendar.md): Keep debriefs landing in the same shared calendar every time, instead of whoever's happens to be scheduling it.
- [Customising your debrief invitees](https://docs.incident.io/integrations/debrief-invitees.md): Automatically invite the right people to every debrief, without hunting down email addresses each time.
- [Debrief placeholders](https://docs.incident.io/integrations/debrief-placeholders.md): Save responders the hassle of hunting for a free slot by pre-booking regular debrief time on everyone's calendar.
- [Google Calendar](https://docs.incident.io/integrations/google-calendar.md): Keep meetings connected to the right incident automatically, without anyone pasting in a link.
- [Debriefs: Google Calendar Permissions](https://docs.incident.io/integrations/google-calendar-debrief-permissions.md): Fix calendar permission errors that stop incident.io detecting or scheduling your debriefs.
- [Google Meet](https://docs.incident.io/integrations/google-meet.md): Give responders an instant call to join the moment an incident is declared, with no manual setup.
- [Intercom app for status pages](https://docs.incident.io/integrations/intercom.md): Let customers check your service status from inside Intercom, cutting down repetitive support questions.
- [Outlook Calendar](https://docs.incident.io/integrations/outlook-calendar.md): Attach Outlook meetings to incidents automatically, and schedule debriefs in a single click.
- [Statuspage](https://docs.incident.io/integrations/statuspage.md): Update customers automatically, without relying on one person to remember to log into Statuspage.
- [Microsoft Teams Online Meetings](https://docs.incident.io/integrations/teams-meetings.md): Give every incident a dedicated Microsoft Teams call, created automatically the moment it's declared.
- [Webex](https://docs.incident.io/integrations/webex.md): Automatically create Webex meetings for incidents and enable Scribe transcription
- [Zendesk](https://docs.incident.io/integrations/zendesk.md): Keep support agents and responders in sync, without anyone switching between tools.
- [Using Pylon with incident.io for incident management](https://docs.incident.io/integrations/pylon.md): Route urgent customer escalations straight to your on-call engineer, and keep support tickets linked to the incidents they caused.
- [Zoom](https://docs.incident.io/integrations/zoom.md): Save responders the extra step of creating a Zoom call by hand for every incident.

#### Task and issue tracking

- [Asana](https://docs.incident.io/integrations/asana.md): Send incident follow-ups to Asana and keep their status updated automatically.
- [Auto-exporting follow-ups](https://docs.incident.io/integrations/auto-export-follow-ups.md): Send follow-ups to the right project automatically, based on the details of each incident.
- [Azure DevOps](https://docs.incident.io/integrations/azure-devops.md): Keep incidents and their follow-ups tracked in Azure DevOps, without anyone updating them by hand.
- [ClickUp](https://docs.incident.io/integrations/clickup.md): Keep task tracking in ClickUp without manually copying incident follow-ups back and forth.
- [Freshservice](https://docs.incident.io/integrations/freshservice.md): Keep Freshservice tickets in step with incidents and follow-ups
- [GitHub](https://docs.incident.io/integrations/github.md): Link pull requests to incidents and keep follow-ups moving, without leaving GitHub.
- [GitLab](https://docs.incident.io/integrations/gitlab.md): Keep follow-ups, merge requests, and incident updates in sync with GitLab.
- [Setting up a GitLab Group Hook](https://docs.incident.io/integrations/gitlab-group-hook.md): Keep GitLab and incident.io in sync in real time, not just once a day.
- [Create and sync incident tickets](https://docs.incident.io/integrations/incident-tickets.md): Keep incidents connected to the issue trackers where your teams plan their work.
- [Jira](https://docs.incident.io/integrations/jira.md): Keep incident tickets and follow-ups in step with your planned work in Jira.
- [How to export follow-ups to Jira Cloud](https://docs.incident.io/integrations/jira-follow-ups.md): Turn incident follow-ups into Jira tickets your team can track through to completion.
- [Jira required permissions](https://docs.incident.io/integrations/jira-permissions.md): Know exactly what access Jira needs before you connect it to incident.io.
- [Jira Server and Data Center](https://docs.incident.io/integrations/jira-server.md): Keep incident tickets and follow-ups in step with your planned work in self-hosted Jira.
- [Setting up a webhook in Jira Server](https://docs.incident.io/integrations/jira-server-webhook.md): Get status changes in Jira Server back into incident.io in real time, not on a delay.
- [Linear](https://docs.incident.io/integrations/linear.md): Route follow-ups and on-call triage straight into Linear, assigned to the right person automatically.
- [Export follow-ups to Notion](https://docs.incident.io/integrations/notion-follow-ups.md): Turn incident follow-ups into Notion database pages, with status, assignee, and priority sync back to incident.io.
- [Salesforce Service Cloud](https://docs.incident.io/integrations/salesforce-service-cloud.md): Link Salesforce cases to incidents and keep support agents in the loop.
- [ServiceNow](https://docs.incident.io/integrations/servicenow.md): Bridge fast incident response with the structured record-keeping your ServiceNow processes rely on.
- [Shortcut (formerly Clubhouse)](https://docs.incident.io/integrations/shortcut.md): Keep task tracking in Shortcut without manually copying incident follow-ups back and forth.

#### Collaboration

- [Confluence](https://docs.incident.io/integrations/confluence.md): Export post-mortems to Confluence, with support for routing different teams to different destinations.
- [Confluence required permissions](https://docs.incident.io/integrations/confluence-permissions.md): Grant incident.io just the Confluence access it needs to publish your post-mortems automatically.
- [Google Docs](https://docs.incident.io/integrations/google-docs.md): Export post-mortems to Google Docs, keeping write-ups where the rest of your team already works.
- [Notion](https://docs.incident.io/integrations/notion.md): Export post-mortems, track follow-ups, and sync Notion databases into Catalog.
- [SharePoint](https://docs.incident.io/integrations/sharepoint.md): Export post-mortems to SharePoint, keeping write-ups inside your Microsoft 365 environment.

#### Other on-call solutions

- [Opsgenie](https://docs.incident.io/integrations/opsgenie.md): Page the right people through Opsgenie without ever leaving Slack.
- [PagerDuty](https://docs.incident.io/integrations/pagerduty.md): Page the right people through PagerDuty without ever leaving Slack.
- [Pagerduty sample incident import script](https://docs.incident.io/integrations/pagerduty-import.md): Bring your historical PagerDuty incidents into incident.io with a sample import script.
- [Splunk Integrations](https://docs.incident.io/integrations/splunk.md): Connect Splunk for on-call escalations or to stream audit logs, however your team works.
- [Splunk On-Call (VictorOps)](https://docs.incident.io/integrations/splunk-on-call.md): Escalate incidents and page on-call teams through Splunk On-Call.

#### API

- [Our API](https://docs.incident.io/integrations/api-overview.md): Trigger incidents from anywhere in your stack, and pull your incident data into the tools you already use.
- [Creating your first incident using the API](https://docs.incident.io/integrations/api-create-incident.md): Trigger incidents directly from your monitoring or ticketing tools instead of starting them by hand.
- [Closing incidents via the API](https://docs.incident.io/integrations/api-close-incidents.md): Automatically close incidents once follow-up work wraps up in your own systems, without waiting on manual review.
- [Exporting your data using a Singer tap](https://docs.incident.io/integrations/singer-tap.md): Get your incident data into your data warehouse without building and maintaining your own export pipeline.

#### Other integrations

- [Requesting Additional GitHub Permissions](https://docs.incident.io/integrations/investigations-github-permissions.md): Give Investigations the GitHub access it needs to help pinpoint the code change behind an incident.
- [Proxy](https://docs.incident.io/integrations/proxy.md): Securely reach the tools running inside your private networks.
- [Salesforce integration](https://docs.incident.io/integrations/salesforce.md): Bring customer and account context from Salesforce into every incident.
- [Building a Salesforce Integration to view and create incidents](https://docs.incident.io/integrations/salesforce-integration.md): Build a custom Salesforce integration for declaring and tracking incidents your way.
- [Vanta](https://docs.incident.io/integrations/vanta.md): Give your Vanta auditor automatic evidence of access reviews and incident follow-ups.
- [Using Zapier](https://docs.incident.io/integrations/zapier.md): Trigger incidents automatically from any app you connect through Zapier.

### Administration

#### Configuration

- [Incident forms](https://docs.incident.io/admin/incident-forms.md): Control which fields appear on declare, accept, update, resolve, and escalate forms
- [Policies](https://docs.incident.io/admin/policies.md): Define rules and reminders for on-call setup, debriefs, follow-ups, and post-mortems
- [Announcements](https://docs.incident.io/admin/announcements.md): Control what your incident announcement posts look like with templates, and where they get posted with rules
- [Channel bookmarks](https://docs.incident.io/admin/channel-bookmarks.md): Add custom bookmarks to incident channels for quick access to key information and links
- [Incident timestamps](https://docs.incident.io/admin/incident-timestamps.md): Validate timestamp ordering to prevent incorrect durations and confusing timelines
- [Default timezone](https://docs.incident.io/admin/default-timezone.md): Set a default timezone for consistent timestamps across your organization
- [Instance name, URL, and icon](https://docs.incident.io/admin/instance-customization.md): Change your incident.io instance name, URL, or icon
- [Sandbox environments](https://docs.incident.io/admin/sandbox-environments.md): Set up a separate incident.io environment to test configuration.
- [Manage your account with Terraform](https://docs.incident.io/admin/terraform.md): Manage incident.io configuration as code with our official Terraform provider

#### Users & permissions

- [User management](https://docs.incident.io/admin/user-management.md): How users are added to incident.io and how to manage them
- [User roles and permissions](https://docs.incident.io/admin/user-permissions.md): Control user access with base roles and custom permissions
- [API keys](https://docs.incident.io/admin/api-keys.md): Control API access with account-level and team-scoped permissions.
- [Role restrictions](https://docs.incident.io/admin/role-restrictions.md): Control who can be assigned to incident roles and what they can do
- [SCIM (Automatic user provisioning)](https://docs.incident.io/admin/scim.md): Sync users, roles, and permissions from your identity provider
- [Okta SCIM group setup](https://docs.incident.io/admin/okta-scim.md): Step-by-step guide to connecting Okta SCIM with incident.io
- [Duplicate user errors](https://docs.incident.io/admin/duplicate-users.md): Resolve duplicate SAML account errors when logging in
- [Deleting users](https://docs.incident.io/admin/delete-users.md): How user accounts are managed and removed in incident.io

#### Team permissions

- [Team roles](https://docs.incident.io/admin/team-roles.md): Give teams control over their own workflows, escalation paths, schedules, incident types, announcements, and more
- [Alerts and escalations](https://docs.incident.io/admin/restrict-escalation-response.md): Keep responding to a team's alerts and escalations within that team
- [Announcements](https://docs.incident.io/admin/restrict-announcement-management.md): Let teams manage their own announcement rules and post templates
- [Catalog types and entries](https://docs.incident.io/admin/restrict-catalog-management.md): Let teams manage their own catalog types and entries
- [Incident types and lifecycles](https://docs.incident.io/admin/restrict-incident-type-management.md): Let teams manage their own incident types and lifecycles
- [Workflows](https://docs.incident.io/admin/restrict-workflow-management.md): Let teams manage their own workflows

#### Security

- [SAML SSO](https://docs.incident.io/admin/saml-sso.md): Manage access to the incident.io dashboard via your identity provider
- [Sign in with email](https://docs.incident.io/admin/sign-in-with-email.md): Let users access incident.io with a one-time code sent to their email address.
- [Mobile access restrictions](https://docs.incident.io/admin/mobile-access-restrictions.md): Restrict what can be seen on the mobile app from unmanaged devices.
- [Audit logs](https://docs.incident.io/admin/audit-logs.md): Track configuration changes and permission updates across your account
- [IP allowlists](https://docs.incident.io/admin/ip-allowlists.md): Restrict access to your incident.io workspace by IP address
- [Webhook IP addresses](https://docs.incident.io/admin/webhook-ips.md): IP addresses used by incident.io webhooks
- [Slack permissions](https://docs.incident.io/admin/slack-scopes.md): Slack permissions and access scopes required by incident.io
- [AI data handling](https://docs.incident.io/admin/ai-usage.md): How incident.io uses AI and handles AI data
- [AI governance](https://docs.incident.io/admin/ai-governance.md): The controls you can apply to AI usage, where each one lives, and what it affects.
- [Managing sensitive data](https://docs.incident.io/admin/managing-sensitive-data.md): Remove or redact sensitive information from alerts, escalations, incidents, and AI features.
- [Security FAQs](https://docs.incident.io/admin/security-faqs.md): Frequently asked questions about security and data handling.

#### Billing & plans

- [Seat types and Viewers with incident.io](https://docs.incident.io/admin/seat-types.md)
- [Managing seats](https://docs.incident.io/admin/managing-seats.md): How to add, remove, and change seats on your incident.io account
- [Billing methods and mechanics](https://docs.incident.io/admin/billing.md): How billing works for monthly and annual plans
- [Changing plans](https://docs.incident.io/admin/change-plan.md): How to upgrade or downgrade your incident.io subscription
- [Deleting your organization](https://docs.incident.io/admin/delete-account.md): How to delete your incident.io organization

### Need more help?

- [Contact us](https://docs.incident.io/help/contact.md)