Console overview
The Console is X4RGE's platform operator workspace — where your X4RGE vendor or internal platform team manages customer organizations, plans, and platform-wide governance.
If you are an organization admin, you almost always work in the dashboard instead: members, models, budgets, and integrations. Console defines what your plan includes; the dashboard defines how your org uses it inside that plan.
Most customers never sign in to Console — and that is normal. This page explains what happens on the platform side so you know who to ask when allowance, access, or entitlement looks wrong.
What this page is for
Day-to-day admin — invites, Model control, Usage, GitHub — lives in the dashboard overview, not Console.
Who uses the Console
Most X4RGE customers never sign in to Console — they only need the dashboard. Read this page when you need to know who sets your included allowance or why you cannot change a plan limit yourself.
How Console affects your org
Even if you never open Console, its settings shape what you see in the product:
If Included does not match your agreement, contact your operator or Help & support — org admins cannot edit contracts in the dashboard.
Console vs dashboard
Org admins narrow models and spend in the dashboard; they cannot exceed what Console entitlement allows.
What operators do here
Platform operators use Console for commercial and cross-customer work. Customer admins use the linked dashboard pages for day-to-day org management.
What each organization is entitled to — plan, allowance, and limits.
Platform users, support sessions, and audit across customers.
Clients (organizations)
Each client is a customer organization on the platform. Operators use Console to:
- See org status, plan, and usage against entitlement
- Adjust capacity when agreements change
- Support customer admins during rollout or incidents
- Manage platform-level people records tied to the org
Plans and platform controls
Operators align commercial plans with what org admins see in Settings and Usage. Org admins then choose models and budgets inside that ceiling via Model control and Usage.
In practice
Pick the row that matches your role.
For organization admins
You do not need Console access for normal work. After your org is provisioned, focus on the dashboard:
Confirm Included on Usage
Open Usage and verify Included matches your agreement after onboarding.
Invite your team
Add members and roles in Members.
Connect GitHub
GitHub is required for cloud runs and automations.
Set internal policy
Model control and Usage budgets — at or below plan entitlement.
If entitlement looks wrong
Contact your operator or Help & support — do not expect a Console login.
See Dashboard overview for the full first-week checklist.
Onboard a new organization
Platform operators only — customers receive access through the dashboard after this handoff.
Operators follow a simple pattern; customer admins finish setup in the dashboard.
Create the organization
Add the customer as a client in Console with the right org record.
Set plan and capacity
Define plan, included monthly allowance, and limits (including cloud and automation where applicable). See Contracts & capacity.
Invite the customer admin
Add the customer's primary admin so they can sign in to the dashboard.
Verify entitlement
Confirm the org's Usage page shows the correct Included bucket and cloud runs are not blocked by entitlement.
Hand off to the customer
Direct the admin to connect GitHub, configure cloud agent setup, and complete first-week dashboard setup.
Operators set the ceiling in Console; customer admins tune policy inside it. Start with one team and one repo on GitHub before org-wide automations.
Who has access
Console requires a platform operator role. Most organization admins only see the dashboard. After sign-in, users with platform access go to the operator console; everyone else goes to the dashboard.
Dashboard Settings governs your org. Console governs entitlement and platform operations — not day-to-day member invites or model pickers.