Dashboard
Portfolio monitoring, alerts, Risk Graph, Exit Overhang, reports, and The Wire for signed-in organizations.
The Philidor dashboard is the signed-in risk surface at philidor.io/dashboard. It is built for portfolio monitoring, routed alerts, graph-based decisioning, holder-overhang review, exportable reports, and organization-level settings.
Access Model
The dashboard uses session authentication through the backend dashboard API. The browser checks /dashboard/v1/auth/session and redirects unauthenticated users to login.
The session is scoped to an organization. Users can belong to more than one organization, switch the active organization, and carry either an admin or member role.
Product Areas
| Area | Product route | What it shows |
|---|---|---|
| Overall | /overview | Monitored addresses, deployed positions, idle assets, risk mix, portfolio grade, review queue, and risk inbox preview |
| Risk Inbox | /alerts | Position-relevant events, score changes, breach warnings, severity filters, unread state, and event detail |
| Markets | /market | Read-only market breach context used from the Risk Graph flow |
| Signals | /news | The Wire inside the dashboard, with market-wide and portfolio-scoped lenses |
| Graph | /risk-graph | Live portfolio graph, look-through reads, policy checks, and signed organization decisions |
| Exit Overhang | /overhang | Holder concentration translated into action bands for monitored vaults |
| Risk Reports | /reports | Memo, evidence JSON, position CSV, and alert history CSV exports |
| Wallets | /wallets | Read-only EVM addresses that define monitored exposure |
| Settings | /settings | Account, password, team, and alert delivery channels |
Organization Model
Portfolio data follows the active organization, not only the signed-in user. The sidebar shows the active organization, supports organization switching when multiple memberships exist, and exposes settings for team management.
Admins can invite colleagues, change member roles, revoke access, and configure notification channels. Members can view organization settings and depend on admins for channel changes.
Plan Gating
The dashboard reads feature access from the backend before showing gated surfaces. Exit Overhang checks /dashboard/v1/overhang/access and uses that access response before it adds the page to navigation or loads portfolio overhang data.
When Exit Overhang is not enabled, the product shows the current plan badge and explains that the surface is available on Decisioning. It does not show overhang data without access.