> 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/your-account.md). # Your account Your account is yours, whatever your role: your profile and who you share it with, your password, backup sign-in codes and the appearance you prefer. Open it from the account menu at the bottom of the sidebar. ![Your account](https://2219266317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3d0MFWUa7VoBOdFAsEhL%2Fuploads%2FP4S8R7ZTDmKJ2FzvRAZQ%2Faccount.b3068b4f.png?alt=media) *Your profile at the top, sign-in and appearance below.* ### Your profile One profile for every studio you work with. It is locked with your password, so Pictures Up cannot read it, and a studio sees it only if you share it. 1. Fill in what you want studios to have: name, pronouns, phone, home base, usual role, department, emergency contact and phone, and dietary needs and allergies for catering. 2. Under "Share with", turn on each studio that should see it. A studio you do not share with sees only your name and email. 3. Choose "Save profile". Sharing copies your details into that studio's People entry for you, and every later save updates it. Turning sharing off stops future updates; what the studio already has stays until you ask them to remove it. "Delete my profile" erases it from Pictures Up. Studios keep what you shared before. If an admin resets your password, the profile can no longer be opened with the new one. Your account then offers "Start a new profile", which begins again with just your name. ### Sign-in and appearance **Password.** "Change password" asks for the current one and the new one, at least 10 characters. It signs you out everywhere else. **Backup sign-in codes.** For when the emailed code cannot reach you. "Make backup codes" gives you 10 codes, shown once, with a file to download. Each works once, in place of the emailed code, and you get an email when one is used. Making new codes retires the old ones. **Trust this browser.** The sign-in code step offers to trust the browser for 30 days, so it skips the emailed code next time. It is ticked by default. **Appearance.** Dark is the default. Light is high contrast, for direct sun. "Match this device" follows the system. Only you see this, and the same choice is in the account menu. **Overview layout.** How a production's Overview opens for you: Slate, Poster or Frame line. See [Productions](/productions.md). The switch on the Overview itself sets the same thing. ### Good to know * Your email is the one your invite or studio setup used. Changing it is not built yet. * Your name comes from your profile once you have one. * A profile shared with a studio fills their People entry, including the emergency and dietary fields that only admins, editors and you can see. --- # 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/your-account.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.