Dashboard
Overview
Section titled “Overview”The Dashboard tab is the operational home of OrgGuard. It rolls up the metrics that auth-asset owners and admins need to glance at daily: how many critical findings are open, which certificates expire soonest, what the discovery coverage looks like, and what just happened in the org. The dashboard auto-refreshes every 10 minutes, and every widget pulls live data from the same Apex controller that powers Findings, Inventory, and Coverage.
What you’ll see
Section titled “What you’ll see”The Dashboard is composed of nine widgets in three rows plus a full-width activity feed. Empty states render when there’s no data to show — they’re not errors.
| Region | Widget | Shows |
|---|---|---|
| Header | Dashboard Header | Greeting, last-scan timestamp, org context pill (current org name; clicking shows a “Coming soon” toast — multi-org switching not yet available), and a Run scan button that triggers a manual discovery scan |
| Banner | Alert Banner | Inline banner shown only when there are critical findings (expired certs, severe ownership gaps, etc.) — hidden when org is clean |
| KPI cards | KPI Cards | Four scorecards: Assets monitored (total tracked + composition bar), Critical findings (count of critical-severity open findings, with Triage all link), Ownership coverage (% of assets with assigned owner), Scheduled jobs · 7 day (job-health % over the rolling 7-day window) |
| Row 2 (left, wider) | Cert Timeline | Bar chart of certificate counts per day across the next ~90 days, color-coded by severity band (Critical / Warning / Watch). Each bar’s hover tooltip lists the certificates expiring on that day |
| Row 2 (right) | Findings List | Top N most-recent unresolved findings, with severity, finding type, and source asset |
| Row 3 (three equal cells) | Category Bars | ”Assets by category” — asset counts by asset type (Certificate / Connected App / Auth Provider / Named Credential / etc.), with each row’s stacked bar segments color-coded by finding severity present in that category |
| Row 3 | Findings Trend | Line chart of new + resolved findings over the rolling 30-day window |
| Row 3 | Coverage Gauge | Ring (donut) chart showing the percentage of org auth assets OrgGuard can discover (Cert + Connected App + Auth Provider + Named Cred …) |
| Bottom | Activity Feed | Last 7 days of scan-run events, policy evaluations, and notification deliveries — up to 20 most-recent events displayed |
Header, banner, and KPI cards render immediately on tab load. The four chart widgets and the activity feed render after the KPI cards’ wire resolves (so the spinner clears once the org-wide totals are in). The whole page auto-refreshes every 10 minutes via a setInterval on the parent component.
Common tasks
Section titled “Common tasks”Task: Drill into a finding from the Dashboard
Section titled “Task: Drill into a finding from the Dashboard”Who can do this: OrgGuard Admin, User, or Auditor (read access to Finding__c).
Prerequisites: at least one finding exists in the org. If the Findings List widget is empty, your org has no open findings — nothing to drill into.
- Open the Dashboard tab in the OrgGuard app.
- Scroll to the Findings List widget (right side of row 2).
- Click the finding row.
- Expected result: the finding’s record page opens with full details — severity, type, source asset, current status, and any acknowledgment notes.
To act on the finding (acknowledge, suppress, or resolve), use the buttons on the record page itself; the dashboard is read-only.
Task: Spot certificates about to expire
Section titled “Task: Spot certificates about to expire”Who can do this: OrgGuard Admin, User, or Auditor.
- Open the Dashboard tab.
- Look at the Cert Timeline widget (left side of row 2).
- Hover over a bar to see a browser tooltip in the form
Day N: CertName1, CertName2. Bars representing days with no expiring certificates show no tooltip. Bar color indicates the band: red (≤7 days), orange (8–30 days), or blue (31–90 days). The hover tooltip relies on the SVG<title>element, which is desktop-browser only — Safari and Salesforce mobile may suppress it or require a long-press. - Click View all {N} in the widget footer to open the full Certificates list filtered to the discovered certs.
- Expected result: you can see, in one glance, every certificate within 90 days of expiry without leaving the Dashboard tab. For per-cert details (expiration date, owner, dependencies), use the Certificates tab.
Task: Confirm a recent scan completed
Section titled “Task: Confirm a recent scan completed”Who can do this: any persona.
- Open the Dashboard tab.
- Read the timestamp in the Dashboard Header.
- Expected result: the timestamp matches your most recent scheduled or manual scan. If it’s hours stale, see Troubleshooting below.
Task: Trigger an immediate scan
Section titled “Task: Trigger an immediate scan”Who can do this: OrgGuard Admin (Run scan requires write access).
- Click Run scan in the Dashboard Header.
- The discovery scan kicks off in the background. Widget data updates when the scan completes — typically within 1–5 minutes for orgs with fewer than 500 assets.
- Expected result: the Dashboard Header timestamp advances and the Activity Feed picks up the new scan-run event on the next 10-minute auto-refresh (or after you navigate away and back).
There is no manual per-widget refresh button. The 10-minute setInterval on the page handles routine refresh; Run scan is for when you need newly-discovered assets, not just refreshed data.
Status / lifecycle reference
Section titled “Status / lifecycle reference”KPI cards and Findings List severity colors
Section titled “KPI cards and Findings List severity colors”| Severity | Color | Typical trigger |
|---|---|---|
| Critical | Red | Expired certificate, expired Connected App secret, or any finding whose policy mapped the window to “Critical” |
| High | Orange | Within 7 days of expiry, missing-owner on a high-value asset, or policy-mapped to “High” |
| Medium | Yellow | Within 30–60 days of expiry, or policy-mapped to “Medium” |
| Low | Blue | Within 60–90 days of expiry, or policy-mapped to “Low” |
Severity is determined by the Policy’s Severity Mapping field. Different policies can map the same window to different severities — see Policies.
Cert Timeline color bands
Section titled “Cert Timeline color bands”The Cert Timeline uses a simpler three-band scale specific to expiration windows:
| Band | Color | Range |
|---|---|---|
| Critical | Red | ≤ 7 days to expiry |
| Warning | Orange | 8–30 days to expiry |
| Watch | Blue | 31–90 days to expiry |
Coverage gauge brackets
Section titled “Coverage gauge brackets”| Range | Reading |
|---|---|
| 80–100% | Healthy — OrgGuard sees the majority of auth assets in the org (green ring) |
| 50–79% | Acceptable — investigate which providers have gaps (orange ring) |
| Below 50% | Critical — major discovery gap; see the Coverage tab for per-provider detail (red ring) |
Troubleshooting
Section titled “Troubleshooting”| Symptom | Likely cause | Fix |
|---|---|---|
| Dashboard tab loads but every widget shows “Insufficient Privileges” | Permission set assigned but Apex class access not granted. The OrgGuard package ships with OrgGuardDashboardController access in all three permsets — if you’ve cloned a permset and forgotten to re-grant the class, this is the cause. | Re-assign the OrgGuard permset (Admin / User / Auditor). If you’re using a cloned permset, add OrgGuardDashboardController to its Apex Class Access list. |
| Header timestamp is hours stale | The scheduled scan didn’t run, or the Scheduled Job Health poller is unscheduled. | Open the Scans tab and check the most recent Scan Run record. If it’s old, click Run scan in the Dashboard Header. If the scheduled jobs show as unscheduled, follow the scheduled-jobs admin guide. |
| Coverage gauge stuck at 0% | OrgGuard hasn’t completed an initial discovery scan, or the running user lacks read access to one or more discovery sources (Certificate, ConnectedApplication, etc.). | Run the Setup wizard from the Setup tab — it kicks off the initial discovery. If discovery has run but coverage stays at 0%, confirm the running user has the OrgGuard_Admin permset (some discovery providers need elevated read access on standard objects). |
| Findings List empty on a brand-new install | This is normal — no policies have evaluated yet. Findings are created by policy evaluation, not by discovery alone. | Run the Setup wizard’s “Apply default policies” step. After the first scheduled job fires, findings will populate. |
| Activity Feed empty | No scan runs, policy evaluations, or notifications have happened yet. | Same as above — run a scan, let policies evaluate, and the feed will start populating. |
Q: How often does the dashboard refresh? A: Automatically every 10 minutes. The parent component fires a refresh cycle on every child widget at that cadence, so widgets update without you having to touch the page. To pull data sooner, click Run scan in the Dashboard Header (which kicks off a new discovery scan and propagates results when complete) or navigate away from the Dashboard tab and back.
Q: Can I add or remove widgets? A: Not directly. The dashboard is a packaged Lightning App page. Customers can clone the FlexiPage in Lightning App Builder and customize the clone, but the OrgGuard-shipped page itself is fixed.
Q: Why does the Coverage Gauge sometimes drop after a release? A: New providers (e.g. when we ship discovery for a new auth-asset type) initially appear at 0% coverage in your org until OrgGuard runs its first discovery scan against them. After the first scan, the gauge re-stabilizes. Don’t be alarmed by a temporary dip post-upgrade.
Q: I see findings in the Findings tab that aren’t in the Findings List widget — bug? A: No. The widget shows the top N most recent unresolved findings, not all of them. Use the Findings tab for the full list and filtering.
Q: Can my User-tier accounts see the Dashboard? A: Yes. OrgGuard Admin, User, and Auditor permsets all grant tab visibility for the Dashboard tab. Auditor sees it as a read-only compliance summary; the underlying record-level access still respects the permset’s CRUD/FLS configuration.
Q: The dashboard URL changed after upgrading from a beta — old bookmarks are broken. A: The Dashboard tab moved to a packageable app page in a recent beta. Bookmark the new location: OrgGuard app → Dashboard tab. The previous home-page variant is retained for backward compatibility but is no longer linked from the navigation.
Related
Section titled “Related”- Policies — configure which findings drive which dashboard widgets
- Findings — full-list view of what the Findings List widget summarizes
- Coverage Summary — drill into the per-provider gap behind the Coverage Gauge
- Asset Inventory — see every tracked asset, including those not surfaced by any widget
- Setup Wizard — first-time setup of the policies and schedules that power the dashboard
- Permission Sets — Admin / User / Auditor tier mapping