> For the complete documentation index, see [llms.txt](https://info.picturesup.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://info.picturesup.app/inbox.md).

# Inbox

Inbox is where Pictures Up tells you what happened: approvals and change requests, comments from clients and guests, failed uploads and previews, signed releases, call sheets sent to you, and people joining. The Notifications row in the sidebar shows how many are unread.

![The Inbox](https://2219266317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3d0MFWUa7VoBOdFAsEhL%2Fuploads%2FSDSeLl7sP5bOdS48GNah%2Finbox.b43cb898.png?alt=media) *Notifications, grouped by Today and Earlier.*

### Reading it

Notifications are grouped into Today and Earlier, newest first. Click one to open what it is about: the note in the viewer, the file, the call sheet, the release. Hover a row for "Mark read" or "Mark unread" and "Open". On a phone, swipe a row left for the same. "Mark all read" clears the count.

The chips at the top narrow the list: Comments, Approvals or Uploads. Releases, call sheets and people joining show under All.

### What arrives

| Notification                                                                           | Who gets it                                  |
| -------------------------------------------------------------------------------------- | -------------------------------------------- |
| Someone mentioned you in a note                                                        | You                                          |
| A cut was approved or changes were requested, in Pictures Up or from the client portal | The studio, and whoever uploaded the version |
| A client or a guest commented on a file                                                | The studio                                   |
| A guest uploaded files through a share link                                            | The studio                                   |
| Someone shared a file with you from the share dialog                                   | You                                          |
| A preview failed                                                                       | Whoever uploaded the version                 |
| An upload stopped                                                                      | Whoever was uploading                        |
| A talent release was signed                                                            | The studio                                   |
| A call sheet was sent for a day you are on                                             | Everyone on the sheet who signs in           |
| Someone joined the studio                                                              | The studio                                   |

"The studio" means every member except crew. Crew see only notifications addressed to them, and only on their own productions.

### Good to know

* Only call sheets go out by email as well. Everything else is in-app.
* A client's or guest's notes on one cut update a single notification for six hours rather than piling up.
* "Retry" on a failed upload opens the file so the upload can resume from there.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://info.picturesup.app/inbox.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.