Overview
Use the workspace overview as a plan-aware readiness board for cost, governance, integrations, alerts, and technical setup.
What this menu is for
Overview is the workspace readiness board. It summarizes whether the workspace is ready for the plan and capabilities you actually have, not for every Kadryn feature in the product.
Use it when you want a quick answer to: is usage flowing, are costs understandable, are the relevant controls configured, and what should we fix next?
What Overview should show
Overview focuses on plan-relevant readiness:
- Usage ingestion and gateway activity when those capabilities are enabled.
- Cost overview, forecast, allocation, reporting, unit economics, or data health only when the plan includes those surfaces.
- Guardrails, alerts, Slack, developer diagnostics, recommendations, and savings proof only when the plan grants access.
- Actions that point to the menu that owns the fix.
What Overview should not do
Overview should not penalize a workspace for features that were not purchased. A Free workspace should not look unhealthy because Business-only report scheduling, advanced alert routing, or unit economics are unavailable.
It should also avoid becoming the place where users perform every action. It is a triage and readiness surface. The owning menu should still handle configuration, mutation, and detailed investigation.
Primary workflows
- Check the workspace status and the next recommended action.
- Confirm whether usage and cost data are present.
- Review plan-relevant readiness signals.
- Open the owning menu for a fix.
- Return to Overview to confirm the state improved.
Best practices
- Treat Overview as the executive and admin front door.
- Use it before enabling enforcement so missing data is visible early.
- Keep metadata and project ownership clean because many readiness signals depend on allocation quality.
- Use the plan-aware locked states as product guidance, not as operational failures.
Related menus
Use Command Center for prioritized cross-menu signals. Use Costs for detailed cost analysis. Use Developers for ingestion, gateway and diagnostics. Use Guardrails for enforcement readiness.