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

# Sentry

> Error details for investigations. Auto Monitors can create Sentry alerts and receive them.

**1. Connect**

Go to **Connections**, click **Connect** next to Sentry, and authorize Ordyn for your organization.

## Permissions

Ordyn's Sentry connection needs the OAuth scopes `org:read`, `project:read`, `event:read`, `alerts:read`, `alerts:write`. Scopes are fixed when you connect, so a missing scope means reconnecting Sentry from Connections.

### Errors and monitor reads

Read your organization, projects, errors and existing alerts.

| Scope | Used for |
| - | - |
| `org:read` | Your organization and its projects |
| `project:read` | Project settings |
| `event:read` | Issues, events and stack traces |
| `alerts:read` | Existing alert rules |

### Manage monitoring

Create and maintain the alerts Ordyn manages.

Scopes: `alerts:write`.

### Alert delivery setup

A one-time approval that creates the internal integration named Ordyn AutoMonitors, which delivers alerts from Ordyn's monitors back to Ordyn. The elevated token is not stored.

Scopes: `org:write`.

### How to grant

**Reconnect Sentry.** In Ordyn, open Connections → Sentry → Reconnect and authorize as a Sentry user whose organization role can edit alerts (Owner or Manager, or a Member when the organization lets members edit alerts).

Permission catalog version `2026-10-16.1`. See [permission changes](/reference/permission-changes).

## What Ordyn reads

* Stack traces, to find the exact code path.
* Breadcrumbs, to reconstruct what led to the error.
* Error frequency and affected users, to judge whether this is new and how bad it is.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.