Administer the platform

1. Sign in to Agent Barn.
2. Open your profile menu.
3. Find the Platform section.
4. Select Platform view.

The route changes to:

/dashboard/platform

The top navigation changes to Overview, Users, Organizations, Event Deliveries, and Templates.

Platform View does not establish an Active Organization. The Organization switcher may still list Organizations where you hold a real Membership, but that Membership state is separate from the Platform View route.

To return to Organization View, select an Organization where you are a Member.

If the profile menu contains no Platform section, the signed-in account does not have Platform Privilege. Platform routes require an authenticated user session belonging to a user with Platform Privilege — API-key, service, runtime, and other non-user credential classes cannot exercise Platform Administrator authority.

The Platform landing page begins with point-in-time inventory.

The Agent status cards form a current inventory snapshot. They do not change when you select a different activity period.

The Organizations card is currently a global count. Selecting an Organization or messaging-app filter for the activity report does not narrow that card.

Use these cards for inventory and lifecycle trends, not as a replacement for Agent health or runtime monitoring.

The Activity section reports work observed during a selected period. Unlike the inventory cards, every value here is period-scoped.

The charts show inbound and outbound messages per bucket, and existing, newly created, and active Agents over time.

Select a period

The default interface period is This month. Presets include the last hour, last 6 hours, last 12 hours, today, yesterday, last 7 days, last 30 days, this week, last week, this month, last month, this year, and a custom range.

The interface converts these selections into explicit timestamps. If the statistics endpoints are requested directly without a period or explicit timestamps, the server’s raw default is the previous 30 days.

Apply filters

The current interface can narrow activity by Organization, and by messaging app — Slack, Teams, or Telegram.

The API additionally supports filters for Agent ID and Agent creator ID, which the Platform View controls do not currently expose. The underlying Agent platform contract also supports Discord, although Discord is not currently included in the statistics interface’s messaging-app selector.

Interpret Active Agents

An Agent is active when Agent Barn observes at least one inbound message, outbound message, or Tool Call during the period. Agents are deduplicated within the period and within each chart bucket.

Tool Calls matter here because scheduled or proactive Agent work may never produce an outbound chat message.

Understand time buckets

Agent Barn selects a bucket size from the requested span:

Buckets are UTC instants. The interface builds calendar presets from the viewer’s local timezone and sends them as absolute instants, so near local midnight a chart label can fall on an adjacent UTC date even when the totals are correct.

Requests that would produce more than 5,000 buckets are rejected. Shorten the range, or request a coarser granularity.

Select Users to open the global account list. The page displays each user’s full name, email address, Platform Administrator status, creation time, and email-verification state. Organization Memberships appear on the user detail page.

Create a user

1. Select Create user.
2. Enter the user’s email address.
3. Optionally enter a provisional full name.
4. Optionally enter the initial Organization name.
5. Select Create and invite.
6. Copy the invitation link if email delivery is unavailable.
7. Send the link only through an approved secure channel.

Agent Barn atomically creates:

Pending User
├── Initial Organization
├── Owner Membership
└── One-time set-password invitation

The user chooses their own password. This is not a password-setting workflow — the Platform Administrator never creates or learns the password.

If no Organization name is supplied, Agent Barn derives one from the full name or email identity. Organization names are display labels and do not need to be globally unique.

Resend an invitation

1. Find the unverified user in the list, or open their detail page.
2. Select Resend invitation.
3. Copy the new invitation link if necessary.
4. Ask the user to discard any older link.

Resending rotates the invitation token, so previous invitation links stop working. An already-active user cannot be reinvited through this action.

Current limitations

Platform user administration does not currently provide administrator-selected passwords, platform-level password reset, user account deletion, or account impersonation.

A Platform landing-card description may still mention password resets or account removal. Those workflows are not implemented, and must not be treated as available.

Select Organizations to search the global Organization catalogue. Each card shows the Organization name, description, Organization ID, Owner name and email, and creation date.

Organization names are not globally unique. Use the Organization ID, the Owner, and the immutable Creator identity to tell two Organizations apart.

Inspect Organization detail

Open an Organization to review its name and description, the current Owner, the immutable Creator identity, the creation date, the member count, and Membership names, emails, roles, and pending state.

The Owner and the Creator can be different people. Ownership can be transferred, while Creator identity remains the historical creation identity.

Platform Organization detail is an allowlisted oversight projection. It does not expose allowed model configuration, Agents or Agent configuration, Templates and Skills, Shared Credentials, Agent Secrets, messages or Tool Calls, Logs, or Organization Costs.

Viewing an Organization in Platform View does not grant Membership, and does not add the Organization to the Organization switcher. To administer Organization-owned resources, obtain a real Membership and use Organization View.

Platform Organization operations

Platform View currently cannot create a standalone Organization, rename one, modify its description or model allowlist, change Membership roles, remove Members, transfer ownership, delete the Organization, or suspend and reactivate it.

New Organizations are created either through user onboarding or through authenticated user self-service. See Manage organizations and members.

Platform Privilege grants access to the global Platform View routes and operations.

Grant privilege

1. Open Users.
2. Find the target user.
3. Select Grant Platform Admin.
4. Enter a specific operational reason.
5. Select Grant privilege.

Revoke privilege

1. Find an existing Platform Administrator.
2. Select Revoke Platform Admin.
3. Enter the reason.
4. Select Revoke privilege.

The reason must contain between 1 and 1,000 characters after surrounding whitespace is trimmed. Use a reason such as:

On-call platform operations responsibility for Q3

Do not use:

Requested

Every successful change updates the user’s Platform Privilege, emits a Platform-scoped Domain Event, and creates a durable Security Audit Record through the audit projection.

Protected cases

Agent Barn rejects:

• Revoking your own Platform Privilege
• Revoking the final Platform Administrator
• Granting privilege to an existing Platform Administrator
• Revoking privilege from a user who does not have it
• An empty reason
• A reason longer than 1,000 characters

Privilege changes take effect for the target user’s subsequent requests.

Select Event Deliveries to open the read-only Event Delivery Monitor.

Event Deliveries represent handler work created for internal Domain Events. They are not runtime telemetry, public webhooks, or the Security Audit Record explorer.

Delivery lifecycle

1. PENDING
2. ENQUEUED
3. PROCESSING

A claimed delivery then reaches one of two terminal states:

• SUCCEEDED The handler completed successfully
• DEAD_LETTERED The delivery reached a terminal failure

The lifecycle runs PENDING, then ENQUEUED, then PROCESSING. From PROCESSING a delivery ends in either SUCCEEDED or DEAD_LETTERED.

Read the summary

The summary cards show a count for every status, a stale count for the active states, an unknown-age count, the age of the oldest active delivery, and dead-lettered terminal failures. Select a summary card to filter by that status.

Filter deliveries

The monitor supports search by delivery or Event ID; search by Organization, event name, or handler prefix; and filters for status, event type, Organization, and creation date range, with newest-first or oldest-first ordering.

Expand a row to inspect safe operational metadata — delivery and Event IDs, event name and schema version, handler name, Organization identity where applicable, status and attempt count, created, enqueued, claimed, and completed timestamps, the dead-letter reason, a bounded and redacted last error, and curated Actor or Subject display strings where available.

The monitor never exposes raw Event Payloads, credentials, Agent Secrets, message content, tool data, or raw Actor and Subject envelopes.

Refresh and current limits

Select Refresh to fetch current data. The page does not poll automatically.

A dead-lettered delivery requires investigation of its handler, event contract, configuration, or dependent service. It is not automatically republished.

Select Templates to manage the global Platform Template catalogue. Platform Templates are global resources available for Organization adoption; they are not owned by an individual Organization.

A Platform Template lineage can have immutable published versions, at most one mutable Draft Template Version, required global Skills, and multiple Markdown prompt artifacts.

Create a new lineage

1. Select New Template.
2. Enter the Template metadata.
3. Edit the Markdown artifacts.
4. Select the required global Skills.
5. Save the draft.
6. Review every artifact.
7. Publish the draft.

The system derives the Template key. Do not invent or edit it manually.

Update an existing lineage

1. Open a Platform Template.
2. Select Start draft or Continue editing draft.
3. Edit the draft.
4. Save without publishing as often as necessary.
5. Publish when the version is ready.

Publishing creates the next immutable version and clears the draft.

Restore an older version

1. Select the historical published version.
2. Start a Template Restore from that version.
3. Review the resulting draft.
4. Publish the draft.

Publishing the restore creates a new version. It never modifies the historical version, and it never moves an active-version pointer backward.

Review Work with templates before publishing global Template changes.