> 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/people.md). # People and profiles People is the studio's address book: the team you book on productions, the contacts at clients and locations, and the companies they belong to. A person's page gathers their details, their productions, their kit and their Pictures Up access. ![The People page](https://2219266317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3d0MFWUa7VoBOdFAsEhL%2Fuploads%2FzQWVr1gGvVoFHZxTln0E%2Fpeople.745eb027.png?alt=media) *The team, with their usual role, department, contact and access.* ### Three tabs * **Team**: crew and staff. Anyone here can be booked on a production and invited to Pictures Up. The columns show the usual role, department, contact, productions and access. * **Contacts**: client contacts, talent and location owners, each linked to a company. * **Companies**: clients, agencies, rental houses and vendors. Productions pick their client and agency from here, and rentals pick their house. Search matches names, roles, departments, emails and productions. Filter the team by department and by access: Signed in, Invited or No access. ### Adding someone 1. Choose "Add person" on Team, or "Add contact" on Contacts. 2. Enter the name and pick Team or Contact. For the team, add their usual role and department; for a contact, their title and company. 3. Add an email, phone, location and notes, then "Add person". Companies work the same way from their tab: name, type, email, phone, website, address and notes. People also arrive on their own: booking "Someone new" on a crew list adds them to Team, and a new client named on a production is added to Companies. ### A person's page ![A person's page](https://2219266317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3d0MFWUa7VoBOdFAsEhL%2Fuploads%2FO4ZMlckRsOPOneF9aKDG%2Fperson.5b409e36.png?alt=media) *Details, productions, kit and access, in one sheet.* * **Details**: email, phone, location, company and notes, plus pronouns, emergency contact and dietary needs when the person has shared them from their profile. Emergency and dietary details are seen by admins, editors and the person only. * **Productions**: every booking, with the role and dates. Each opens the production's crew list. * **Kit**: the gear this person brings, with quantity, category and serial. Admins also see a day rate and replacement value. The kit follows the person onto the gear list of every day they are booked on. * **Pictures Up access**: whether they sign in, and as what. Admins can invite from here, resend an invite or copy its link, and manage roles in Members. * **Remove from People** deletes the person, their kit and their crew bookings. Someone who signs in has to have their access removed in Members first. ### Profiles A profile is a person's own record of themselves, kept across every studio they work with: name, pronouns, phone, home base, usual role, department, emergency contact and dietary needs. It is encrypted with their own password, so Pictures Up cannot read it. When they share it with a studio, those details fill their entry in that studio's People and stay up to date as they change them. Crew are asked to share when they join from an invite, and the box is ticked by default. Anyone can change it later in [Your account](/your-account.md). ### Good to know * Admins and editors see everyone and edit anyone. Crew see themselves and the people on their productions, and can change only their own email, phone, location and kit. Viewers have no People page. * Pronouns show to anyone who can open the person. Emergency contact and dietary needs do not. * Money on kit is for admins only, and "View as Crew" hides it. --- # 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/people.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.