Settings
Settings is where organization admins configure how your org behaves on X4RGE — name and invites, access rules, budgets, teams, active sessions, and who owns the org.
This is not where you write code or start agent runs. It is the policy and account hygiene hub that works alongside Members, Model control, and Usage. Everyone can manage their own profile and personal sessions; most org-wide controls need admin or super admin.
What this page is for
Settings governs your organization on X4RGE. Included plan allowance and commercial limits are set in the Console by operators — not here. See Contracts & capacity if Usage does not match your agreement.
Who can change what
If you cannot see a Settings page, your role may be member only — ask an admin to adjust access in Members.
Why settings matter
Settings works with Members, Model control, and Usage & billing — configure people and caps here, then tune models and spend in those modules.
How settings fits together
Think of Settings as the outer boundary; other dashboard modules fill in the details:
Changes in Settings often appear in the org audit log — useful when policy "worked yesterday" and does not today.
In practice
Match your goal to the right Settings area or linked module.
Organization settings
Open Settings → Organization for org-wide controls. These apply to everyone in the org unless a team-specific override exists.
Identity and membership
When your plan includes SSO (SAML, SCIM, domain enforcement), extra identity options appear here after your identity provider is connected.
Access and governance
Many admins start with: require project assignment on, integration approval on, personal API keys off until CI is ready, and budget on warn before hard stop.
Sessions
Settings → Sessions (or Security) lists active desktop sign-ins — device, last active, and surface. Use this when offboarding someone or investigating an unknown device.
Review active sessions
Look for unknown devices or logins that should have expired (lost laptop, contractor offboarded).
Revoke if needed
Choose Revoke on a row. That device signs out immediately. A local run in progress may fail on the next credential check.
Follow your security runbook
For compromised accounts: revoke sessions, remove the member in Members, and rotate API keys in Integrations.
Revocations are recorded in the org audit log.
Teams
Teams group members for larger orgs — useful for budgets, model policy, and project ownership. Smaller orgs may skip teams and use one flat org until squads need separate caps or model rules.
Create a team
Settings → Teams → New team. Name by function (Platform, Payments) or product line.
Add members and a lead
Assign a team admin for membership; members contribute; viewers get read-only visibility where your plan allows.
Link projects
Connect teams to projects so policy and usage roll up correctly.
Optional team budget
On plans with team budgets, allocate a slice of the org cap on the team panel.
Teams are the operating unit inside your org; Organization settings are the outer boundary that applies to everyone.
Integrations and keys
GitHub, Slack, Linear, and other connectors live in the Integrations module — Settings links here for org-wide rules that affect connectors.
User API keys (for CLI and automation) respect Allow personal API keys in Organization settings. When enabled, members create keys in Integrations; admins rotate after offboarding by revoking keys and updating CI secrets.
See Headless CLI for CI authentication patterns and GitHub for the primary production integration today.
Ownership and destructive actions
Deleting an organization or revoking sessions cannot be undone from the UI. Before deleting, export audit and usage reports if compliance requires retention.