> 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/library/client-portal.md). # Client portal The client portal is where a client reviews cuts: on a phone or a laptop, with your public notes, and an Approve button. They get one email with one button, and the link signs them in on that device. No account, no password. ### Inviting a client 1. Open the cut in the [viewer](/library/viewer.md), choose "Share", then "Invite a client to review…". Or go to the Client portal tab under Share links and choose "Invite a client". 2. Enter their name and email. Names from the client's company in People are suggested. Pick the company, and tick the productions they review. 3. Choose "Send invite". The email is from Pictures Up in your studio's accent colour, with the cut's thumbnail if one is waiting, and a single button: "Review the cut". Replies go to whoever sent the invite. The link is for that email address only and signs them in, so the dialog that follows offers to copy it for you to pass on directly, and asks you not to forward it elsewhere. Inviting the same email again adds productions to their access. ### What the client sees ![The portal on a laptop](https://2219266317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3d0MFWUa7VoBOdFAsEhL%2Fuploads%2FxGHwJIxURC4M3vWqjGNv%2Fclient-portal.030815d1.png?alt=media) *Cuts waiting for review, the player, your public notes, and the decision.* Cuts appear in the portal when they are marked for review in their productions. The client sees the current version only, as a preview. There are no downloads. ![The portal on a phone](https://2219266317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3d0MFWUa7VoBOdFAsEhL%2Fuploads%2F3UrgCEHLKcS4ssAKitik%2Fclient-portal-phone.2f9fff5b.png?alt=media) *On a phone: the cuts waiting, then the player.* * **Notes.** Pause and "Add a note at" the timecode. Client notes are always public and show in your viewer with their name. * **Approve.** Records the approval with an optional note. The client is told the studio will start finishing the cut and that they will still see the final. * **Request changes.** Asks what should change. Their notes on the video go with it. Both end on a confirmation naming your contact, and the client gets an email when the next version is ready for them. ### In the studio A client's decision is recorded on the version like any other: who, when, "from the client portal", and the note. It shows as the banner in the viewer and in its Versions tab, and the file moves to Approved or Changes requested. Everyone in the studio except crew gets a notification, and so does whoever uploaded the version. The cut drops off Home's Needs you list. ### Managing access The Client portal tab under Share links lists every client with their company, productions, when they were last seen, and whether their access is on. For each: "Copy link", "Resend" the invite, "Turn off" or "Turn on", and "Delete". Turning off keeps them on the list; deleting removes them, while their notes and approvals stay. ### Good to know * The portal shows video, audio and images that are in review, up to 60 at a time. * A note is up to 2,000 characters. The studio gets one notification per person per cut, updated as more notes arrive. --- # 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/library/client-portal.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.