Governance

Governance covers the platform-level controls that keep usage compliant and accountable across all organizations. Operators enforce these controls in the Console; org admins inherit the resulting boundaries in the dashboard.

Roles and capabilities

The platform uses role-based access control with two distinct layers:

Platform roles are assigned to 4RGE staff or internal platform teams. Organization roles are assigned by each customer's admins and never grant Console access on their own.

Platform capability matrix

Audit

Sensitive actions across the platform are recorded as audit events with the actor, target, and timestamp:

Retrieve audit history via the provisioning API:

curl "https://api.4rged.ai/api/provisioning/audit?limit=50" \
  -H "Authorization: Bearer <platform-operator-session>"

Agent-scoped audit events are also available per organization through the agents API audit stream (included in the operations summary audit.events count).

Agent audit event schema

Cloud and automation actions write rows to x4rge_agent_audit_events with an actorKind of user, internal_user, github_webhook, worker, or system. Each event records action, targetKind, optional targetId, and JSON metadata — for example automation creation (POST /api/automations) logs the creator and repository scope. Org operators correlate these events with Sentinel's 24-hour summary; platform operators use GET /api/provisioning/audit on api.4rged.ai for cross-customer contract and provisioning changes (limit 1–500 rows per request).

Operator procedures

Monthly governance review

1. Export audit log

   Pull the last 30 days of platform audit events. Filter for contract changes and provisioning writes.

2. Reconcile with change tickets

   Every capacity update should map to an approved change request or renewal record.

3. Review platform user roster

   Remove platform roles from departed staff. Confirm support tier access matches current on-call rotation.

4. Spot-check org overrides

   Sample three active enterprise orgs — verify contract limits match signed agreements.

Incident: unauthorized capacity change

1. Identify the actor

   Find the audit event — note actorUserId, timestamp, and reason field.

2. Revert if needed

   Apply a corrective contract update with reason "Revert unauthorized change — ticket INC-123".

3. Notify the customer

   If the org's allowance was affected, inform their admin and confirm Usage reflects the correction.

4. Post-incident

   Review whether the actor still requires platform admin access.

Support session access

For customer issues requiring live debugging, operators can open a support session tied to an organization:

curl -X POST "https://api.4rged.ai/api/provisioning/support-sessions" \
  -H "Authorization: Bearer <platform-operator-session>" \
  -H "Content-Type: application/json" \
  -d '{
    "organizationId": "org_abc123",
    "reason": "Customer report — cloud runs failing setup"
  }'

Support sessions are time-bound and audited. Close them when the investigation completes.

Policy delivery

Governance extends beyond the Console UI — published policies flow to clients automatically:

Org admins can further restrict within entitlement; they cannot exceed contract limits set in Contracts & capacity.