> 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/productions/crew.md). # Crew and invites The Crew tab is the production's crew list: who is booked, for which days, on what terms, and whether they can sign in to Pictures Up. It is also where crew get their invitation. ![The Crew tab](https://2219266317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3d0MFWUa7VoBOdFAsEhL%2Fuploads%2FkQrSMwSAEEvLNtLaLNff%2Fcrew.e5795597.png?alt=media) *Crew grouped by department. Admins also see rates, kit fees and agreements.* ### The crew list People are grouped by department in a fixed order: Production, Camera, Lighting, Grip, Electric, Sound, Art, Hair & makeup, Wardrobe, Post, Talent, Other. Everyone sees the name, role, dates and access. Admins also see the day rate, the kit fee and the agreement status, and a line at the top with the day total. Access has three states: * **No access**: booked, but not invited to Pictures Up. * **Invited**: an invitation is out and has not been used. * **Signed in**: they have an account and can open this production. When a production uses more than one department, "All departments" filters the list. ### Booking someone Admins and editors can book people. 1. Choose "Add person". 2. Pick "From your team" to choose someone already in People, or "Someone new" and enter their name, with an email and phone if you have them. New people are added to People under Team as well, so you can book them again. 3. Enter the role and department. Choosing someone from the team fills these in from their usual role. 4. Set their first and last day if they are only on for part of the shoot. With no dates they are on every shoot day. Call times are set on the call sheet, not here. 5. Choose "Add to crew". Their sheet opens straight away. ### The crew sheet ![A crew member's sheet](https://2219266317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3d0MFWUa7VoBOdFAsEhL%2Fuploads%2FanUF7k24JfVJmV7uc28p%2Fcrew-sheet.37b767cd.png?alt=media) *Deal memo, booking, kit and access, in one sheet.* Click anyone in the list to open their sheet. **Deal memo** (admins only). Set the rate as a day rate, an hourly rate or a flat fee, plus the kit fee per day, the overtime terms and notes. The sheet works out the days from the booking dates and shows the total: day rate times days, or hourly rate times a 10-hour day times days, or the flat fee, plus the kit fee for each day. Move the agreement along with "Mark as sent" and "Mark as signed", or set it in "Edit deal memo". The statuses are Draft, Sent and Signed. **Booking.** The role, department, dates, email and phone. "Edit" changes any of them. Dates are optional: none means every shoot day. **Kit.** The gear this person brings. "Edit kit" opens their page in People, where kit and its daily fee are set. **Pictures Up access.** This is where crew are invited. ### Inviting crew to Pictures Up Crew do not need an account to be on the call sheet. They need one to open Shoot day, see their call times and check gear on their phone. Admins invite them from the crew sheet. 1. Open the person's sheet. Under Pictures Up access, choose what they can do: "Crew ยท this production only" is the default. Editor and Viewer are the other options. 2. If no email is on file, enter one. 3. Choose "Invite to Pictures Up". With no email, choose "Make invite link" and send the link yourself. 4. The link works once and expires in 7 days. Copy it from the sheet if you need to send it another way. "Resend invite" sends the email again. What they see when they open the link: a page in your studio's branding, their name and email already filled in, a password field, and a box to share their Pictures Up profile with the studio, which is ticked by default. A 6-digit code confirms their email, then they are in. If they already use Pictures Up with another studio, they join with that account's password, and one sign-in opens every studio they belong to. See [Your account](/your-account.md) for profiles. What crew can see once they are in: their call times, Shoot day, the schedule and their own kit, on the productions they are booked on. Nothing else, and never money. ### Taking someone off "Take off this crew" at the foot of the sheet removes the booking and the deal memo. The person stays in People, and a crew member loses access to the production once they have no booking left on it. ### Good to know * Being on a production's crew list is what opens that production to crew. Booking someone who already signs in adds it to their list straight away. * Roles and seats for everyone with a sign-in are managed in Studio settings under Members. Crew on a single production do not use a seat. * Deal memos, rates and totals are for admins only. "View as Crew" in the production header hides them on your own screen. --- # 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/productions/crew.md?ask=&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.