> ## Documentation Index > Fetch the complete documentation index at: https://docs.pharussecurity.com/llms.txt > Use this file to discover all available pages before exploring further. # Weekly digest > What the Monday exposure digest contains, who gets it, and how to preview it, test it or switch it off. **Plans:** Every plan. Not sent while the workspace is read-only. **Who:** owners and admins get it by default; members get it when they switch it on. The weekly exposure digest is an email that sums up the past week: new exploited vulnerabilities in your products, other new matches, the incidents and deadlines that are running, and what needs attention. Pharus sends it every Monday from 07:00 Oslo time. ## When it arrives The digest goes out on Mondays from 07:00 Oslo time, once per week, and covers the week before (Monday to Sunday). All times in it are Oslo time. The heading names the company, the week number and the dates, for example "Week 41 · 5 Oct – 11 Oct 2026". The subject says what matters most: * "Pharus weekly: 2 new exploited vulnerabilities in Gateway G3", or "Pharus weekly: no new exploited vulnerabilities"; * with ", 1 overdue report" added when a report is past its deadline. ## What it contains Sections without anything to say are left out. | Section | What it shows | | - | - | | **New exploited vulnerabilities** | Vulnerabilities known to be exploited that matched your components this week, with the **Component**, where it is **Listed in** (CISA KEV, EUVD) and the **Incident**. Name-only matches are marked "Confirm the match": their version isn't verified, and confirming one opens an incident. | | **This week** | Other new matches that aren't known to be exploited, per product family, and the number of incidents opened and closed, reports submitted and new disclosure reports | | **Open incidents** | Each open incident with its **Next report** and when it is **Due**, and a warning when a report is overdue | | **Waiting for approval** | Determinations recorded but not yet approved, with who recorded them and who they wait for | | **Disclosure reports** | New reports this week, and reports not acknowledged within the business days your disclosure policy promises | | **Housekeeping** | Product families without a new SBOM in 30 days, a vulnerability feed that hasn't synced in 24 hours, and release lines whose security support ends within 90 days or ended in the last 30 | | **What Pharus checked** | How many components in how many product families Pharus checked, and when CISA KEV, EUVD and OSV last synced | Most sections link to the page in Pharus where you act on them, such as **Open vulnerabilities**, **View incidents** or **Open the inbox**. ## Who receives it | Role | Default | | - | - | | Owner | On | | Admin | On | | Member | Off | Each member chooses for themselves. The digest comes in the member's language, or the company's default language if they haven't chosen one. Owners and admins can see who gets it in the **Who gets what** table under **Settings → Notifications**. ## Switch it on or off Go to **Settings → Notifications**, or select **Change what you receive** at the bottom of a digest. Turn **Weekly digest** on or off. The change is saved as you switch. Once you have changed it, the page says "You changed this from the default." Select **Use the default** to go back to the default for your role. ## Preview and test it **Settings → Notifications** shows a **Digest preview**: this week so far, as the email will look. Select **Send me a test digest** to get it by email now. A test digest has "\[Test] " before the subject and covers the week so far; the real one covers the whole week. While the workspace is read-only (Free, or closed), monitoring is paused and no digests go out. See [billing](/workspace/billing). ## Related This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.