Admin Dashboard
Admin Dashboard
Section titled “Admin Dashboard”Use the admin dashboard when you need the fastest view of workspace health, access posture, and adoption signals. The dashboard should help you decide whether you need to open deeper pages for identity, permissions, networking, or reporting.
Before you rely on it
Section titled “Before you rely on it”- Confirm which signals come directly from the dashboard and which ones still require feature-specific pages.
- Decide how often admins will review the dashboard during rollout, steady state, and incident response.
- Treat the dashboard as an index into action, not the only place where every control lives.
Best uses
Section titled “Best uses”- Review member growth, identity posture, and access risk.
- Check whether meeting adoption and recap workflows are behaving as expected.
- Route into deeper policy pages when a dashboard signal needs action.
Recommended review pattern
Section titled “Recommended review pattern”- Start with workspace-wide health and unresolved warnings.
- Open identity, permissions, or networking pages when a signal suggests a real policy or reliability issue.
- Capture repeated trends for the admin analytics and reporting flow instead of reacting only one meeting at a time.
What the dashboard should not replace
Section titled “What the dashboard should not replace”- Some controls still live in organization settings, networking docs, or artifact permission pages.
- It is not a substitute for role reviews, detailed network diagnostics, or per-artifact permission checks.
Troubleshooting
Section titled “Troubleshooting”The dashboard shows a problem but not the cause
Section titled “The dashboard shows a problem but not the cause”- Follow the linked policy, analytics, or networking page before changing defaults.
- Check whether the signal reflects one noisy meeting or a repeated pattern across teams.
- Capture the date range and affected workflows before escalating to support or engineering.