Contact and admin operations

Organization administration

Organization owners and admins manage members, roles, API keys, sessions, cloud accounts, policies, budgets, webhooks and activation requests within the organization. Every operation is tenant-scoped and audited. The owner is a single organization member; ownership transfer is an audited operation.

Activation follows:

DEMO -> REVIEW_PENDING -> platform review -> APPROVED / REJECTED
                                      |
                                      v
                                    ACTIVE

The activation request should describe company, role, use case, providers, infrastructure size, compliance needs and a contact consent. Platform approval applies explicit limits and entitlements; it does not make the UI a trusted authorization layer.

Platform administration

Platform admin is not the same as an organization OWNER. The server requires the explicit platform.admin entitlement before listing organizations, reviewing activation requests, changing status, applying entitlements, changing feature flags or inspecting platform health.

Operation	API area	Evidence
Review activation	/platform-admin/activation-requests	request status and review note
Approve organization	/platform-admin/organizations/:id/approve	status, plan and entitlement audit
Reject, suspend or reactivate	/platform-admin/organizations/:id/...	administrative status change
Inspect health	/platform-admin/health	API, database, AI configuration and email mode
Inspect feature flags	/platform-admin/feature-flags	flag update record

Suspension should be treated as an emergency containment action: it prevents new authorized work while existing job and audit records remain available for investigation. Re-activation is explicit and should follow a review of credentials, jobs, approvals and alerts.

Contacting support

The public contact flow exposes a short-lived server-signed challenge at GET /public/contact/challenge, then accepts a verified submission at POST /public/contact-submissions. Submissions are rate-limited, replay-protected, redacted for common credential patterns and stored as NEW without tenant ownership. Platform admins review them through /platform-admin/contact-submissions and the admin control room; status values include NEW, IN_PROGRESS, RESOLVED and SPAM.

When contacting the Devopsify team, include organization slug, environment, UTC timestamp, request ID, contact/request/run/agent ID, job status and the exact error code. Do not include secrets or full authorization headers. For a suspected tenant-isolation issue, stop the affected operation and report it as a security incident.