Settings
The Settings area holds organization-wide configuration and account controls that apply across desktop, CLI, cloud, and dashboard. Most pages require admin or super admin; a few controls (profile, personal sessions) are available to all members.
Organization
Manage your organization's identity and high-level policy from Settings → Organization.
Some controls (SAML, SCIM, domain enforcement) appear when identity plumbing is connected — reserved until SSO is configured.
Admin procedure: tighten access for a new enterprise customer
Enable require project assignment
Turn on Require project assignment so new members cannot run agents until explicitly added to a project.
Disable personal API keys initially
Leave Allow personal API keys off until CI secrets workflow is approved; enable per team when pipelines are ready.
Set integration approval
Enable Integration approval required so GitHub and other connectors need admin sign-off.
Set budget with hard stop
Configure Manage budget with a conservative monthly cap and hard stop after pilot week, relax to warn if needed.
Sessions
Settings → Sessions (or Security) lists active desktop sessions for the org or user context, depending on role.
Review active sessions
Inspect device, last active, and surface. Unknown devices may indicate a lost laptop or stale login.
Revoke a session
Click Revoke on a row. The device is signed out immediately; in-flight local runs may fail on next policy or credential check.
Audit
Session revocation is written to the org audit log with actor and target session.
Org admins revoking another user's sessions may require elevated capability — follow your org's security runbook for compromised accounts (revoke sessions → remove member → rotate API keys).
Teams
Group members into teams with a name, optional description, and team lead drawn from org members. Teams help larger orgs assign ownership, allocate budgets, and apply model policy overrides.
Create a team
Settings → Teams → New team. Name squads by function (Platform, Payments, Mobile) or product line.
Add members and team admin
Assign team admin for day-to-day membership changes; team member for contributors; team viewer for read-only stakeholders.
Link projects and repos
Connect teams to projects and repository visibility so effective policy resolves correctly.
Optional team budget
When enterprise budgets are enabled, allocate a team USD slice from the org cap on the team budget panel.
Team role matrix
Integrations and API keys
Integration connectors (GitHub, Slack, Linear, etc.) are managed from the Integrations module; Settings may surface shortcuts. User API keys for CLI and automation live under Integrations — creation respects Allow personal API keys in Organization settings.
# After admin enables API keys — developer verifies headless auth
export X4RGE_API_KEY="x4rge_live_..."
4rged whoamiRotate keys after offboarding by revoking in Integrations and updating CI secrets.
Session revocation API
Admins revoking another member's desktop session call the platform API at
api.4rged.ai/api/provisioning/organizations/{organizationId}/sessions/{sessionId} with
DELETE. The handler invokes provisioningRevokeRuntimeSession and signs the device out
immediately — in-flight local runs may fail on the next policy or credential check. Session
revocation is always written to the org audit log with actor and target session id.
Ownership and destructive actions
Deleting an organization or revoking sessions cannot be undone from the UI. Double-check before confirming deletion — export audit and usage reports first if compliance requires retention.
Settings governs customer org behavior. Platform operators change contracts, global model catalog rollout, and unlimited capacity in the Console — not here.