# Inbox Inbox is your personalized dashboard for managing pull request reviews from GitHub. It organizes your PRs into meaningful sections so you can quickly identify what needs your attention and take action. {% hint style="info" %} Inbox replaces the previous AttentionSet feature with a more powerful, organized experience. {% endhint %}

Inbox dashboard

## Sections Inbox organizes your pull requests into predefined sections based on your relationship to the PR and its current state: ### Requested review PRs where you've been requested as a reviewer and need to take action. These are PRs authored by others that are waiting on your review. ### Returned PRs you authored where the attention has come back to you — typically because a reviewer has commented, requested changes, or approved your PR. ### Approved PRs you authored that have received all required approvals and are ready for the next step (e.g., merging or queuing). ### Approved by me PRs where you've submitted an approval as a reviewer. These are no longer waiting on your action, but you can track their progress here. ### Waiting for others PRs you authored that are waiting for action from reviewers. You don't need to do anything here — the ball is in someone else's court. ### Drafts Draft PRs you've authored. These are work-in-progress changes that aren't yet ready for review. ### Queued PRs you authored that are currently in the merge queue, waiting to be merged. ### Snoozed PRs you've temporarily snoozed to remove them from your active sections. See [Snooze](#snooze) below. ## Section filters Each predefined section has a filter icon that lets you apply exclusion filters to fine-tune what appears in that section. You can exclude specific authors, labels, or PRs with failing CI, and set a freshness threshold to hide stale PRs.

Section exclusion filters

## Attention The core concept behind Inbox is **attention** — identifying who should be acting on a PR at any given moment. When the author sends a PR for review, reviewers have the attention. When reviewers respond, the author gets the attention back. Every PR can have one or more people who have the attention. A merged PR will not have anyone's attention. Attention is typically managed automatically based on GitHub events, but it can also be toggled [manually](/inbox/manually-change-attention.md) as needed. See [Attention reasons](/inbox/attention-reasons.md) for a full list of events that trigger attention changes. ## Real-time updates Inbox updates automatically in real time as PR activity happens. When a reviewer comments, a CI check fails, or a PR is approved, your Inbox sections update immediately without needing to refresh the page. ## Snooze Sometimes a PR doesn't need your immediate attention. The snooze feature lets you temporarily hide a PR from your active Inbox sections until a specified time. Snoozed PRs are removed from all predefined sections and moved to a dedicated **Snoozed** view, accessible from the Inbox sidebar. When the snooze period expires, the PR automatically returns to the appropriate section. To snooze a PR, click the snooze icon on any PR row in your Inbox. You can choose from preset durations (30 minutes, 1 hour, 3 hours, tomorrow morning, next week) or select **Custom** to pick a specific date and time.

Snooze duration options

When choosing a custom snooze duration, a calendar picker lets you select the exact date and time to unsnooze.

Custom snooze date and time picker

## Repository filtering If you work across multiple repositories, you can filter your entire Inbox by repository using the dropdown in the top right. The repository filter applies across all sections, letting you focus on PRs from a specific project.

Repository filter

## Custom sections In addition to the predefined sections, you can create your own custom sections with personalized filters. This is useful for tracking specific types of PRs — for example, PRs from a particular team, PRs with a specific label, or failing CI checks. See [Custom sections](/inbox/custom-sections.md) for details on creating and managing custom sections. ## Getting started If you are a new Aviator user, you will first need to install the Aviator app on your GitHub repository. This is typically done as part of the initial setup wizard. You can choose to start with any of MergeQueue or FlexReview workflows to begin the setup.

Welcome to Inbox

Once the initial setup is complete, you will be prompted to link your GitHub account. This step is necessary so we can verify your GitHub username that is used to track your attention. After linking your account, navigate to the **Inbox** page in the Aviator dashboard to see your pull requests organized by section. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.aviator.co/inbox.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.