> 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/readme.md).

# Welcome

Pictures Up runs a small film studio's shoots from one place: productions and their plans, shot lists, locations, call sheets and tasks, crew and gear, an encrypted media library with review and client sharing, paperwork and talent releases, and a Shoot day mode that works on a phone with no signal.

This guide covers one part of the app per article: what it is for, how to do the main jobs step by step, and what to expect along the way. The screenshots come from an invented studio, Lantern Bay Pictures, so every name, email and number in them is made up.

[**Open Pictures Up**](https://demo.picturesup.app), or start with [Getting started](/getting-started.md).

### How do you use Pictures Up?

Pick the path that fits your role. Most studios have all three.

<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>Producers and editors</strong></td><td>Build and run productions: the plan, the crew, the gear, the call sheets and the media.</td><td><a href="/productions.md">Productions and the pipeline</a></td></tr><tr><td><strong>Crew</strong></td><td>Your call times, the day on set, the gear check and releases, on your phone.</td><td><a href="/shoot-day.md">Shoot day</a></td></tr><tr><td><strong>Clients and guests</strong></td><td>Review a cut from a link or the client portal, leave notes, approve.</td><td><a href="/library/client-portal.md">Client portal</a></td></tr></tbody></table>

### Who does what

Pictures Up has four roles. The guide says which role a step needs when it matters.

| Role   | What they can do                                                                                        |
| ------ | ------------------------------------------------------------------------------------------------------- |
| Admin  | Everything, including money, settings, members and invites.                                             |
| Editor | Build and run productions: plan, crew, gear, media, review and sharing. No money, no studio settings.   |
| Viewer | Look at media and schedules. Nothing changes.                                                           |
| Crew   | Their own call times, Shoot day, the schedule and their own kit, on the productions they are booked on. |

Money means day rates, kit fees, rental totals and deal memos. Only admins see it, and an admin can hide it from their own screen with the "View as" switch on any production.

### The articles

1. [Getting started](/getting-started.md): setting up a studio, signing in, finding your way around, and Home.
2. [Productions and the pipeline](/productions.md), with [Plan](/productions/plan.md), [Crew and invites](/productions/crew.md) and [Gear](/productions/gear.md) under it.
3. [Library and uploads](/library.md), with [Viewer and review](/library/viewer.md), [Sharing links](/library/sharing.md) and the [Client portal](/library/client-portal.md) under it.
4. [Paperwork and releases](/paperwork.md)
5. [Shoot day](/shoot-day.md)
6. [People and profiles](/people.md)
7. [Your account](/your-account.md)
8. [Studio settings](/studio-settings.md)
9. [Inbox](/inbox.md)

The [Build tracker](/build-tracker.md) lists what is built, what is still to come, and when each screenshot was taken.


---

# 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/readme.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.