# Attributes

Add custom key/value metadata to events with public or private visibility.

Source: https://statusdashboard.com/docs/events/attributes

Event attributes let you attach custom key/value metadata to any event, such as a ticket reference or runbook link. Choose public visibility to show an attribute on status dashboards and in notifications, or private to keep it visible only in the admin console.

***

## Visibility
Event attributes let you attach custom key/value metadata to any event — for example, `jira_ticket: XA-123` or `runbook_url: https://…`. Each attribute can be **public** or **private**, controlling whether it appears on status dashboards and in notifications.

| Visibility  | Status dashboard | Notifications | Event editor |
| ----------- | ---------------- | ------------- | ------------ |
| **Public**  | Shown            | Shown         | Shown        |
| **Private** | Hidden           | Hidden        | Shown        |

Use **public** attributes for operational context you want subscribers and status dashboard visitors to see. Use **private** attributes for internal references (e.g. internal ticket IDs, on-call notes) that should remain visible only to your team in the event editor.

Changing a **private** attribute does not trigger a subscriber notification. Changing a **public** attribute (or toggling visibility to public) does trigger a notification when notifications are enabled for the event.

## Limits
* Maximum attributes per event applies when you add attributes (the admin console shows your organization's limit).
* **Key:** 1–32 characters. Must start with a letter; may contain letters, numbers, underscores, and hyphens.
* **Value:** 1–256 characters.
* Keys must be unique within an event (case-sensitive).