Platform Administration and Oversight

To work inside an Organization, select one where you have membership. Your Organization and Agent permissions determine which actions are available there.

Organization suspension and reactivation are not currently supported. Use /guides/observe-and-govern/platform-administration for the available administration workflows and current limitations.

Platform View also provides dedicated catalogues for global Platform Templates and Platform Skills. These are Platform-owned resources, not cross-tenant reads of Organization-owned content. Platform routes resolve no active Organization, require Platform Administrator authority, use dedicated Platform DTOs and API routes, and do not grant Membership in any Organization. The API remains authoritative even when the UI hides unavailable actions.

Platform Templates use /dashboard/platform/templates and /api/v1/platform/templates. Platform Skills use /dashboard/platform/skills and /api/v1/platform/skills, including /dashboard/platform/skills/new for creation and /dashboard/platform/skills/{skillId} with /api/v1/platform/skills/{skillId} for detail. Organization and Agent-private Skills are not managed through these routes.

Platform Skills are global resources visible to Organizations and Agents. Bundled aai-cli Skills are bootstrap-provided Platform lineages, while Platform Administrators may create custom global Skill lineages. Creation makes one mutable draft with no published version; the draft owns proposed SKILL.md, relative reference files, description, and provider metadata. Publishing copies its complete content into the next immutable Skill Version and clears the draft. Renaming changes lineage display metadata only; content and provider changes are draft-gated, and publishing never repins existing Agents, Templates, Overrides, Organizations, or forks.

Each published Skill Version contains exactly one root SKILL.md, with other validated paths relative to the Skill root. Consumers pin exact immutable versions. Platform Skills are read-only in Organization and Agent scope; Organizations can fork visible Platform Skills, Agents can fork visible Platform or Organization Skills privately, and forks remain independent with exact direct-source provenance.

Platform Administrators may delete an unreferenced historical Platform Skill Version or unused custom Platform Skill lineage through the shared branded confirmation flow. A version is blocked when it is final, Agent-pinned, Template or Override-required, draft-referenced, or a fork source. A custom lineage is blocked when any version has an Agent pin, Template/Override requirement, or draft/fork-source reference. Custom deletion removes draft, versions, and files; bundled aai_cli lineages cannot be deleted; soft-deleted Agent pins still protect versions; and blocked deletion explains its dependency.

Checked-in bundled Skills seed only missing Platform Skill lineages. Once a lineage exists, database drafts and published versions are authoritative, so redeployment never overwrites Platform Administrator changes. Bundles use isolated api/domains/agents/aai_cli_skills/bundled/skills/aai-<integration>/SKILL.md roots, not Python modules or a shared mutable aai-cli root.

Current Agent counts remain distinct from period-scoped activity statistics. Platform activity is bounded projection data, not tenant-level Conversation access; deferred Tool Call, model, and per-Agent drill-down work is not shipped behavior.

The Event Delivery Monitor displays Domain Event Handler deliveries only. It does not display Communication Deliveries or Connection operation-journal entries; those belong to /guides/observe-and-govern/communication-diagnostics.

Dedicated Platform catalogue APIs may expose and manage global Platform Templates and Platform Skills. This does not permit Platform View to read or mutate tenant-owned definitions. Platform Privilege remains separate from Organization Membership and Agent Access: a Platform Administrator still needs a real Membership and applicable Agent Access for Organization-owned workflows.

Platform-owned administration includes global Platform Templates, global Platform Skills, Platform Privilege management, and pending-user provisioning. Cross-tenant oversight is limited to allowlisted Organization and Agent statistics, user and Membership identity, read-only Event Delivery monitoring, and bounded activity projections.

Platform View is not a deployment control plane. It administers the Agent Barn installation the user is signed into; it does not deploy another environment, promote images, create a public release, or aggregate data across clusters. Each installation has its own Platform Administrators and oversight data, and Platform authority never crosses cluster or database boundaries.

The staging branch on AAI Labs k3s is branch testing with moving latest-staging images; main on the same k3s is the main-branch testing ground with moving latest images. Hosted public Agent Barn on Talos is public production and deploys only from an explicit vX.Y.Z release tag. .github/workflows/deploy-public.yml pins API and UI images from registry.agentbarn.dev; the main k3s deployment is not hosted public production. Public deployment and secret management remain infrastructure workflows outside Platform View, and public and k3s credentials are not interchangeable.

Continue with /guides/observe-and-govern/platform-administration, /guides/templates-and-skills/skill-scopes, /guides/templates-and-skills/skills, /guides/templates-and-skills/skill-versions, /guides/templates-and-skills/forks-and-updates, /guides/local-development-and-operations, and /guides/self-hosting/upgrades for detailed procedures.