Notification Preferences - apviso [APVISO](/)Product

Resources

Developers

Company

[Pricing](/#pricing)[Partners](/partners)[Enterprise](/enterprise)

[Login](/login)[Start free pentest](/register?intent=free-local-pentest)

[Login](/login)[Start free](/register?intent=free-local-pentest)

[Home](/)[Knowledge Base](/docs)Notification PreferencesAccount &amp; SecurityNotification Preferences
========================

Configure how and when APVISO notifies you — via email, Slack, webhooks, or in-app notifications.

Notification Channels
---------------------

APVISO supports multiple notification channels. You can enable or disable each independently and configure which events trigger notifications on each channel.

### Email Notifications

Email is enabled by default for all accounts. Notifications are sent to the email address associated with your APVISO account.

### Slack Webhook

Connect a Slack incoming webhook to receive notifications in a Slack channel. This is separate from the full Slack integration — it is a lightweight option that does not require OAuth.

1. Create an incoming webhook in your Slack workspace.
2. Paste the webhook URL in **Settings → Notifications → Slack Webhook**.
3. Click **Save**.

### Webhook Notifications

Route notifications to any HTTPS endpoint. This uses the same webhook format described in the Webhook Integration article but is scoped to your personal notification preferences rather than organization-wide events.

### In-App Notifications

Notifications appear as a bell icon badge in the dashboard header. Click the bell to see recent notifications. In-app notifications are always enabled and cannot be disabled.

Configurable Events
-------------------

You can choose which events generate notifications on each channel:

- **Pentest completed** — a pentest has finished (includes finding summary).
- **Pentest failed** — a pentest encountered an error.
- **Critical finding discovered** — a critical-severity vulnerability was found during a pentest.
- **High finding discovered** — a high-severity vulnerability was found.
- **Retest completed** — a retest has finished with results.
- **Scheduled pentest skipped** — a scheduled pentest was skipped due to unavailable runner capacity.
- **Runner capacity warning** — runner health or concurrency needs attention.
- **Subscription renewal** — your subscription renewed successfully.
- **Payment failed** — a payment could not be processed.

Configuring Preferences
-----------------------

1. Go to **Settings → Notifications**.
2. For each notification channel, toggle the events you want to receive.
3. Click **Save Preferences**.

Changes take effect immediately.

Testing Notifications
---------------------

Each channel has a **Send Test** button that delivers a sample notification so you can verify the channel is working correctly.

Quiet Hours
-----------

Optionally configure quiet hours to suppress non-critical notifications during specific time windows (e.g., nights and weekends). Critical and high-severity finding notifications are always delivered regardless of quiet hours.

1. Toggle **Enable Quiet Hours** in notification settings.
2. Set the start and end time (in your local timezone).
3. Select which days quiet hours apply.

Team Notifications
------------------

On **Enterprise** tiers, team administrators can configure organization-wide notification policies that apply to all team members. Individual members can add additional notifications but cannot disable organization-level ones.

### Related Articles

[Two-Factor Authentication

Secure your account with TOTP-based two-factor authentication and recovery codes.](/docs/two-factor-authentication)[Integrations Overview

An overview of APVISO's 40+ integration options, supported event types, and tier availability.](/docs/integrations-overview)[Webhook Integration

Set up custom webhooks to receive APVISO events at any HTTPS endpoint with signed payloads and automatic retries.](/docs/webhook-integration)[Scheduled Pentests

Set up recurring pentests on a daily, weekly, biweekly, or monthly schedule to maintain continuous security coverage.](/docs/scheduled-scans)

[Back to Knowledge Base](/docs)

[APVISO](/)Autonomous AI-powered penetration testing for modern web applications.

Subscribe

[](https://github.com/apviso)[](https://x.com/Apviso_com)[](https://www.linkedin.com/company/apviso/)

[![Featured on Good AI Tools](https://goodaitools.com/assets/images/badge.png)](https://goodaitools.com/ai/apviso)

Product

- [Features](/#features)
- [Pricing](/pricing)
- [Integrations](/integrations)
- [Benchmarks](/#compare)
- [Affiliate Program](/affiliate)
- [Partners](/partners)
- [Enterprise](/enterprise)

Resources

- [Blog](/blog)
- [Use Cases](/use-cases)
- [Glossary](/glossary)
- [Comparisons](/comparisons)
- [Alternatives](/alternatives)
- [Compliance](/compliance)
- [Vulnerabilities](/vulnerabilities)
- [Industries](/industries)
- [OWASP APTS](/trust/apts)

Developers

- [Knowledge Base](/docs)
- [API Reference](/docs/api)
- [MCP Server](/docs/mcp)

Company

- [About](/about)
- [Contact](/contact)
- [Status](https://status.apviso.com)
- [Privacy Policy](/legal/privacy)
- [Terms of Service](/legal/terms)

© 2026 APVISO. All rights reserved.
