Dashboard overview
The dashboard is your organization's control center on X4RGE. Admins use it to manage people, models, usage, and settings. Members use it to see their work and start agents within policy.
The overview page is the landing view — a quick pulse on agent activity, projects, and recent changes — without opening every module. Day-to-day coding stays in the IDE, CLI, or Agents workspace; the dashboard is for org health and policy, not writing code.
Platform operators manage contracts and capacity separately in the Console.
What this page is for
Overview is the health check at a glance. Members, Model control, Usage, and Settings are where you make changes. If you only need to invite someone or set a budget, go straight to that module — you don't have to start on overview every time.
Who can see and change what
What appears in the sidebar depends on your role and what your org enabled. Access is enforced on the server — members cannot change org policy by guessing URLs.
Why dashboard overview matters
Review overview weekly during rollout, then use dedicated modules when you need to change something.
How the dashboard fits together
Typical admin rhythm: glance at overview → drill into the module that matches the issue.
What you see on overview
The overview is optimized for admins and leads who want a health check in one glance.
When the org is new, cards may show zeros until the team starts using agents — that's normal.
If metrics are zero but people say they use agents, check that runs happen under this org and that they are on the right projects. See Troubleshooting if access looks wrong.
Admin areas
Invite, remove, and manage org roles; track pending invitations.
Enable providers and models; set per-surface defaults.
Included vs on-demand spend; org budget policies.
Org identity, teams, sessions, and destructive controls.
Additional modules (teams, projects, repositories, audit, analytics) use the same dashboard shell. What you can open depends on your role and what your org enabled.
In practice
First week setup
Confirm your plan
In Settings or Organization, check plan name, included allowance, and renewal — what your agreement includes sets the ceiling admins work within. Mismatch? See Contracts & capacity.
Invite the team
From Members, invite admins and contributors. Default new people to member unless they need dashboard access.
Curate models
In Model control, enable providers your plan includes, turn off costly models you won't use, and set defaults for CLI, desktop, and cloud.
Set a budget
On Usage, configure a monthly cap and whether to warn, soft stop, or hard stop when the org approaches the limit.
Connect integrations
Install GitHub (and others as needed), link repositories to projects, then enable cloud agents or automations when ready.
Prove value on a small group and one repository before org-wide defaults and automations. Expand model catalog and cloud scope after Usage looks healthy for a week.
Dashboard vs Console
The UI shows different modules by role, but access is enforced on the server — members cannot change org policy by guessing URLs.
Budget, model, membership, and ownership changes are recorded in the org audit log. When something "worked yesterday," filter by who changed what before re-applying policy. See Governance for audit context.