> For the complete documentation index, see [llms.txt](https://docs.pharos.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pharos.ai/configuration-guide/advanced/log-categories.md).

# Log Categories

Manage how Pharos maps log categories to Salesforce record types from the Log Categories page in Pharos Admin.

The **Log Categories** admin page assigns a Salesforce **Record Type** to each log **Category**. Pharos's own tailored per-category views don't come from this mapping—Pharos ships a **single** Log record page (`Log_Record_Page`) that adapts to each category via component-visibility rules on the record's Category value. The record-type mapping is the hook for *your own* customization.

## Why Map a Record Type to a Category?

Salesforce lets an admin assign a custom Lightning record page per record type. When the built-in adaptive page isn't enough, mapping a record type to a category lets you customize how logs in that category appear—show or hide fields, add your own components, or rearrange standard ones. A Flow log and a Bulk API log can each surface exactly the detail that matters for that category.

{% hint style="info" %}
**This is a power-user feature.** Pharos ships with rich, category-aware views out of the box, so most orgs never need to configure this. Reach for it when you introduce custom categories or want a specifically tailored Lightning page for a particular category. For how categorization itself works, see [Categorization](https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/log-processing/categorization.md).
{% endhint %}

***

## Accessing Log Categories

Navigate to **Pharos App → Pharos Admin → Advanced → Log Categories**. The page lists the existing category-to-record-type mappings, each with edit and delete actions, and a **New** button to add more.

![Log Categories page — a table mapping Category to Record Type, with New, edit, and delete actions](https://4264222071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdl9tmJ56lvwg5XY63QYr%2Fuploads%2Fgit-blob-2589a627705f3e411a55549a1da2d0248c72f0a2%2Flog-categories-list.png?alt=media)

***

## Adding a Mapping

Click **New** to open the **Add Mapping** dialog, then make two selections:

1. **Category** — the log category to map (for example, Apex, Process Builder, Flow, or Email-to-Case).

   ![Add Mapping dialog — Category dropdown listing technology categories such as Apex, Process Builder, Flow, and Email-to-Case](https://4264222071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdl9tmJ56lvwg5XY63QYr%2Fuploads%2Fgit-blob-eab44ae12856b7a5170d0e3b719910dfe011efc1%2Flog-categories-add-mapping-category.png?alt=media)
2. **Record Type** — the record type to apply to logs in that category (for example, Debug, Error, Event, Warning, or Master). These record-type names survive from earlier releases; they are mapping targets only and are no longer Category values.

   ![Add Mapping dialog with a Category selected and the Record Type dropdown listing Debug, Error, Event, Warning, and Master](https://4264222071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdl9tmJ56lvwg5XY63QYr%2Fuploads%2Fgit-blob-c1c4d3a5e271476de4dc6765edd53a86f982d05b%2Flog-categories-add-mapping-record-type.png?alt=media)

Save the mapping to add it to the list.

![Add Mapping dialog completed — Category set to Flow and Record Type set to Error, with Save and Cancel buttons](https://4264222071-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdl9tmJ56lvwg5XY63QYr%2Fuploads%2Fgit-blob-5087304486e263db1ebaed7c9be06b19ca4cb7e8%2Flog-categories-add-mapping-completed.png?alt=media)

{% hint style="warning" %}
**Mappings keyed on removed categories:** Mapping rows whose Category is **Error**, **Warning**, **Debug**, **Event** (or the earlier-removed **Integration**) keep applying to legacy logs that still carry those values, but match nothing produced by upgraded producers. Remove or re-key them to a technology category. Category is not severity—to act on severity, filter on the **Log Level** field instead.
{% endhint %}

***

## Editing and Removing Mappings

Each row in the list has two actions:

* **Edit** (pencil) — change the category or record type of an existing mapping.
* **Delete** (trash) — remove the mapping.

***

## Related

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>🏷️ Categorization</strong></td><td>How categorization works and category-driven behavior</td><td><a href="https://docs.pharos.ai/platform-overview/pharos-platform-architecture/logs/log-processing/categorization.md">Categorization</a></td></tr><tr><td><strong>📋 Monitoring Logs</strong></td><td>Filter by category in monitoring rules</td><td><a href="https://docs.pharos.ai/configuration-guide/monitoring/logs.md">Logs</a></td></tr></tbody></table>
