> 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/studio-settings.md). # Studio settings Settings is deliberately small: Studio, Members, Integrations, and Plans and storage. Only admins open it, from the sidebar or the account menu. ### Studio ![Studio settings](https://2219266317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3d0MFWUa7VoBOdFAsEhL%2Fuploads%2FIVe3YH86jRwMyRfrbP6x%2Fsettings-studio.7184bb24.png?alt=media) *The studio's name, logo, accent, location, time zone and recovery key.* * **Studio name.** * **Logo.** Shows on share pages, call sheets, the signing page and the client portal. JPEG, PNG, WebP or GIF under 5 MB. Without one, the studio's initials stand in. * **Accent colour.** The colour of the one thing that matters on a screen: the Shoot day button, Approve, the portal's button. Tally red, the Pictures Up colour, is the default. The second swatch opens your browser's colour picker for the studio's own colour; the hover, pressed and text colours on it are worked out for you. Picking applies everywhere at once, share pages and the portal included. * **Location** and **time zone.** Call times, today and shoot dates follow the time zone. * **New comments.** Whether a new note in the viewer starts Public (clients on share links and in the portal see it) or Internal (your team only). Public is the default, since most review links go to clients. Anyone can switch a note before posting. * **Recovery key.** When it was made, and "Make a new recovery key". The old key stops working the moment the new one is made, and the new 12 words are shown once, with a file to download. Nothing changes for anyone signing in. See [Getting started](/getting-started.md) for what the key is for. Name, location, time zone and the comment default save together with "Save changes". ### Members ![Members](https://2219266317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3d0MFWUa7VoBOdFAsEhL%2Fuploads%2FqdTCwrqHDi5YQFCHpKCT%2Fsettings-members.38d616dc.png?alt=media) *Who signs in, what they can do, and who is waiting to join.* Members is everyone with a sign-in, with their role and when they last signed in. Seats are counted at the top: crew on a single production do not use one. **Roles.** Click a member's role to change it: Admin, Editor, Viewer or Crew. Crew also get "Productions…" in their menu, which sets which productions they can open. Booking them on a production's crew adds it too. The studio always keeps at least one admin, and you cannot change or remove yourself. **Inviting.** "Invite" asks for an email, a name, and the role. Crew invites also need at least one production. With an email, the invite is sent; without one, you get a link to pass on. Either way the link works once and expires in 7 days. Open invites wait under "Waiting to join" with "Copy link", "Resend" and "Cancel". **Reset password.** From a member's menu. Their current password stops working at once, they are signed out, and they get an email with a link to choose a new one, which you can copy as well. The link works once and lasts 48 hours. **Remove from studio.** They are signed out everywhere and cannot open the studio again unless invited. Their entry in People stays, with their bookings and kit. "Recent changes" at the bottom keeps the last few member and invite changes. ### Integrations ![Integrations](https://2219266317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3d0MFWUa7VoBOdFAsEhL%2Fuploads%2Fkvd2dYAlTvTL7Ce1qYCX%2Fsettings-integrations.1abcd24a.png?alt=media) *Work tools and AI assistants, each connected on its own terms.* Notion, Slack, Google Calendar, Claude, ChatGPT, Gemini, and any other tool that supports MCP. Each "Connect" dialog says what the tool will be able to see and do, offers Read only or Read and update where that applies, and asks you to confirm that whatever the tool reads leaves Pictures Up's Canadian storage and is handled under that company's terms. No integration ever sees rates, contracts or signatures. On this build, connecting records the choice and nothing is sent anywhere. ### Plans and storage ![Plans and storage](https://2219266317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3d0MFWUa7VoBOdFAsEhL%2Fuploads%2FrgyyG3vHis4GTO1gPGKe%2Fsettings-plans.a52efeb0.png?alt=media) *Seats, storage, cloud rendering and client streaming, with the next invoice.* The plan's seats, storage, cloud rendering hours and client streaming, with meters that warn at 80% and the next invoice estimated in Canadian dollars with GST. Below that: where files are stored (Pictures Up Cloud in Canada, or the studio's own S3, Wasabi or Backblaze bucket), and how previews are made (on a Mac with Pictures Up Drive, free, or cloud rendering), with a per-production override. Prices are placeholders, nothing is billed yet, the storage choice is not saved yet, and files stay encrypted on Pictures Up's own server in Canada. ### Good to know * Every change here is written to the studio's activity with who made it. * Admins who switch "View as Crew" on a production still open Settings; the switch only hides money. --- # 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/studio-settings.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.