> ## Documentation Index
> Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Event Registry

> The Event Registry page (/settings/automation/events) provides a searchable, filterable catalogue of all registered workflow events across the platform,…

The Event Registry page (`/settings/automation/events`) provides a searchable, filterable catalogue of all registered workflow events across the platform, showing each event's owning core, category, consumer count, and governance status.

## Overview

The page is gated by `fw.events.view`. It uses `useEventRegistry` with filters for `owning_core`, `category`, and search text, all scoped to `currentOrganization?.id`. Stats are derived from the filtered events: total count, active count, deprecated count, and total consumer count. Results render in a `Table` with columns for event name, owning core, category, consumer count, status badge, and row actions. A `EventDetailSheet` opens when a row is selected. A `DeprecateEventDialog` is triggered from the row action menu. Filters include a search input, an **Owning Core** select sourced from `OWNING_CORES`, and a **Category** select sourced from `EVENT_CATEGORIES`.

## Who it's for

Requires permission `fw.events.view`.

## Before you start

* You must hold `fw.events.view`.
* Event schemas are defined by platform modules; this page is read-access for browsing and governance, not event creation.

## Steps

<Steps>
  <Step title="Open the Event Registry">
    Navigate to `/settings/automation/events`. All registered events load in the table.
  </Step>

  <Step title="Search events">
    Type in the search field to filter events by name.
  </Step>

  <Step title="Filter by owning core or category">
    Use the **Owning Core** and **Category** dropdowns to narrow the results.
  </Step>

  <Step title="View event details">
    Click a row to open `EventDetailSheet`, which shows the full event schema and governance metadata.
  </Step>

  <Step title="Deprecate an event">
    Use the row action menu to open `DeprecateEventDialog` and mark the event as deprecated.
  </Step>
</Steps>

## Key concepts

<AccordionGroup>
  <Accordion title="Owning core">
    Each event is owned by a specific platform core (e.g., `fw`, `pf`, `cl`). The `OWNING_CORES` constant defines the valid values.
  </Accordion>

  <Accordion title="Event categories">
    Events are grouped by category (e.g., `lifecycle`, `notification`, `integration`). `EVENT_CATEGORIES` defines the available values.
  </Accordion>

  <Accordion title="Consumer count">
    Consumer count reflects how many automation rules, workflows, or subscriptions reference a given event. Deprecating an event may affect these consumers.
  </Accordion>
</AccordionGroup>

## Related

<Columns cols={2}>
  <Card title="Platform Foundation" icon="layer-group" href="/pf/overview">
    Platform Foundation overview.
  </Card>

  <Card title="Governance & parity" icon="scale-balanced" href="/governance/index">
    Documentation coverage and governance.
  </Card>
</Columns>

<Note>
  This page documents shipped product behavior. It is not medical, legal, or
  billing advice. Verify against your organization's policies and applicable
  regulations before using it for clinical, compliance, or billing decisions.
  Protected health information (PHI) shown in the product is governed by your
  tenant's access controls and is never exposed in this documentation.
</Note>

<Accordion title="Documentation sources">
  * src/routes/platform.tsx
  * src/cores/fw/pages/EventRegistryPage.tsx
  * src/cores/fw/hooks/useEventRegistry.ts
</Accordion>