> 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/sharing.md). # Sharing links A share link gives someone outside the studio a page with a file, a folder or a collection, in your studio's branding, with no sign-in. Every link carries its own permissions, expiry, password, view limit and watermark. There are no studio-wide sharing settings. ### Making a link Admins and editors share. Start from any of these: * a file's or folder's menu, "Share" (⌘⇧S) * the "Share" button at the top of a folder or collection * "Share" in the inspector * the "Share" button in a production's header, which asks which folder * "Share link…" in the [viewer](/library/viewer.md)'s Share menu ![The share dialog](https://2219266317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3d0MFWUa7VoBOdFAsEhL%2Fuploads%2FYsEXK2MzOA4JwttEiXvD%2Fshare-dialog.6b6050b6.png?alt=media) *Share from the viewer: a link, a client invite, or all share links.* The dialog opens with three templates that set sensible starting points: | Template | People with the link can | Expires | | -------- | -------------------------------------------------------------- | ------- | | Review | View, comment, see versions | 7 days | | Download | View, download the original | 30 days | | Client | View, download the original, see duration, resolution and size | Never | Then adjust anything: * **View** is always on. * **Download**: Off, Proxy or Original. * **Comment**: timecoded notes. Guests see Public notes only, and their own notes are always Public. * **See file details**: choose from duration, resolution, codec, size, frame rate and description. * **See versions**: earlier versions of each file. * **Upload**: on folders only. Guests can add files to the folder. * **Expires**: Never, 24 hours, 7 days, 30 days, or a date. * **Password**: the dialog suggests one you can keep or change. At least 4 characters. * **View limit**: none, 10 or 50 views. A view counts once per browser every four hours. * **Watermark**: the viewer's email and the time over the picture. Guests give their name and email before they see anything. The watermark is on screen only; downloads are not marked. The sentence at the bottom says exactly what the link does. "Copy link" makes the link and copies it. After that, every change saves at once. Links are short, eight characters after `/s/`, so they read out over the phone and sit cleanly in a message; the short part opens nothing by itself, since the page checks the link's settings every time. A new link on a collection starts with every permission off except View. ### Turning a link off "Disable" stops the link but keeps its settings, so "Turn back on" brings it back as it was. "Delete" removes it; anyone with it loses access straight away, and its views and comments stay in Pictures Up. Every link is checked on every visit, including the media it plays, so disabling, deleting, shortening the expiry or adding a password takes effect immediately. ### What guests see ![A share page](https://2219266317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3d0MFWUa7VoBOdFAsEhL%2Fuploads%2FgK5wLVV9ihYUE22YWixh%2Fpublic-share.e0b20168.png?alt=media) *A single file with its public comments, in the studio's branding.* A link to several files opens on a page with the cover, the studio's logo, the title and description, and a grid of files. One file opens straight into the player. Guests get only what the link allows: download buttons if downloads are on, versions if versions are on, and a comment box if comments are on. The player plays the 1080p preview; the quality menu under it offers the other sizes, and the original when downloads are on. The first time a guest comments or uploads, the page asks for their name and email, and tells them the studio sees both. Guest uploads go into the shared folder, up to 10 GB a file. They do not resume if the connection drops. The studio gets a notification for comments and uploads. Links that are disabled, deleted, expired or over their view limit show a short page saying so and asking the guest to get in touch with the studio. The link's preview in Messages, Slack or email shows the cover, the studio's logo and the title, and goes blank as soon as the link is turned off. ### All your links ![The Share links page](https://2219266317-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3d0MFWUa7VoBOdFAsEhL%2Fuploads%2FI3LoUmgsLuW3m0HflHii%2Fshare-links.8853ad25.png?alt=media) *Every link, with its views and expiry.* "All share links" in the viewer's Share menu, or `/library/links`, lists every link with its template, views, visitors, plays, downloads, last viewed and expiry. "Extend" adds 30 days, "Disable" and "Delete" do what they say, and clicking a link opens its dialog. The Client portal tab on the same page is covered in [Client portal](/library/client-portal.md). ### Good to know * Share links include subfolders. Files in the trash are left out. * Files in an active review link go to the front of the preview queue. * "Add people from your studio" in the dialog sends a studio member a notification with the link, rather than a public link. * Nothing here is money, so "View as Crew" changes nothing. Viewers and crew cannot share. --- # 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/sharing.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.