How do I help client users keep track of their review lists?

Is there any way for a client user to easily track the review sites they’ve been assigned to? We’re running into an issue where we update/reuse playlists, and clients want to be able to go back and view things on the review site, but they are hard to find by digging through emails, etc. We realized recently that we can’t send out a digest with links because they are individualized per client user. We keep recommending the clients bookmark the sites but we can’t control their behavior which is really annoying. Would turning off the login requirement make the links to the review sites generic and shareable? Any suggestions appreciated! Thanks.


Hey there @jlweiss! No, there isn’t a way to have a digest or shared playlist client portal.

Under the hood, playlist shares are tied to an email address and :shotgun: generates a unique URL when you click share. By not requiring login, you’d reduce the overhead of your client needing to remember a password but they’d still need the URL.

Currently, the best bet is to reshare the playlist to the client again to pop it up in their email inbox.


Does anyone have any good ideas for managing playlists that have been sent to clients? We are constantly contacted by confused clients that do not manage their playlists on their own, and there is not a good way for us to manage them from the shotgun side because they only seem to exist as emailed urls.

Ideally, it’d be great for the client (and production) to be able to access a list of their active (and possibly expired) playlists so they don’t have to dig through emails. As far as I can tell, we don’t have access to any Client Review Site events, so we can’t create any triggered scripts.

I’m curious to see if anybody has any suggestions for handling client reviews.


This is a super-common lament about Client Review! I’m sure one of the official Shotgun folks will pop in to direct you to the roadmap suggestions thing, so be sure to put this on there - some sort of portal for the clients is a really common request and the more they hear about it, the more likely it is to eventually turn up.

The only current workaround I’m aware of is to constantly reuse the same Playlists and edit them to update with new content, so the clients can bookmark that URL and find what they’re looking for. So for instance, if you’re sending out shots in Scene 5 for review, you’d create a Scene 5 Playlist and ask them to bookmark that, then they’d know to go looking for any Scene 5 related content there. It’s not great, but it does work, but it also depends on the clients actually bookmarking it from their end, which is obviously outside of your control.

I’d also search here in the community posts for other things on Client Review because there’s been a lot of discussion about this.


Hey @stavernia— as @jlweiss mentioned, I’m merged your post with this thread which covers the same challenge. I’ll also ask our product team to chime in on this one as well.

Please have the product team visit… or, quicker solution: just go ahead and buy them. :wink:



Johnny brought this thread to my attention. Great topic! An admin portal isn’t on the near term roadmap, but I am gathering requirements around Client Review and trying to understand next steps. Admin & Management portal is high on the list of things we’ve been hearing, it seems to be a pretty common need. If you have other thoughts on this, please keep the discussion going and I’ll do my best to follow and update the thread! I’d love to hear more about the nuances of what clients can/can’t see and do in this scenario and what admins need to control for them. (And in both cases “why” they need to do this.) I can’t promise that it will end up in the app straight away but it will definitely influence how we are thinking about the problem.

As mentioned that roadmap portal is a great way to voice this opinion… it lands straight into my inbox. So I and the rest of the PM’s are definitely reading all of this feedback and using it as we dive into these issues.



We stopped using CRS and instead gave the clients proper shotgun accounts with a special “PseudoClient” permission group. Shotgun support helped us lock down the permission group so that it can only see Versions in playlists that contain the client user in a custom “Playlist.Shared With” field, and only see Notes that were created by client accounts. We didn’t care if one client could see notes written by another client. The Media App page has basically become our CRS.


Same here! We call ours “Client Artist” since their access/permissions most closely resemble the standard Artist permissions group. In our particular case, our “clients” on a big project are really more like co-directors, so they can see everything an artist can (which is essential in this case so they can look back at old versions, use Screening Room, etc.) but they can only see Notes that are addressed or cc’d to them. There’s only 3 of them so it’s worth the cost of their subscriptions to keep someone from having to curate playlists on CRS 24/7. Your view limited to playlists solution sounds great though - I could see using that option too in a different scenario.


Great suggestions @luke and @jlweiss! Yeah, I’ve considered making “Client Artist” users but was afraid the permissions might be pretty difficult to manage. I’m glad to hear Shotgun can help lock down those permissions. I may look into that. Unfortunately, we will likely have too many “Client Users” to be financially feasible.

Having clients as “users” would also give them access to review cuts, previous versions and their own previous notes (as mentioned above), all of which would greatly enrich the review process while reducing client confusion and unnecessary notes. They’d also have easy access to a list of their playlists, and we could add additional, automated information for them, such as playlist status.

It would also allow us to manage complex (multi-step) reviews a bit better (we have a fledgling system that hiccups with CRS). Since the CRS uses a single client approval on the Version it makes it very difficult to track multiple clients reviewing a single Version.

@Kevin, The main issues, for us, with CRS at the moment:

  • Clients don’t have a list of active playlists
  • Clients cannot view old versions, or their old notes (unless they are added as a description or a note with attachments, which is extra work)
  • Clients cannot view shots in context (unless we create a sequence for them to review, but then they are not leaving notes per shot, but per sequence, and these need to be transferred, which is extra work)
  • Multiple clients cannot approve the same version (unless they write, as a note, “approved,” then we search through the comments to parse out the approvals, which is extra work)
  • And then there’s the lack of a summary email, so production, and clients, get bombarded with emails during reviews

I will put these issues and suggestions in on the roadmap, but I wanted to see if the community had any other thoughts to add as well. Clients are such an important part of many productions (they pay the bills - like the the shotgun bill - after all), I hope their reviews can be a focus in the near future.


This is such a beautiful summary of the issues with Client Review, @stavernia! I second everything you’ve outlined above, especially bullets 2 & 3 (reviewing old notes and reviewing in context). For us, the straw that broke the camel’s back was notes not being connected to shots (we would post review movies as scenes and then have to try to figure out on which date someone made a comment on shot 3 in scene 5 or whatever) and I finally convinced everyone that our clients needed to be users, not “clients” in the Shotgun sense. For this particular project we only had three clients to add so the financial burden was worth the trade off in terms of efficiency, but that can be complicated to scale up.

This ties in to adoption issues as well - the fact that you can’t post shots in a viewable sequence in CRS really detracts from Shotgun’s usability for some folks, because if they insist on being able to do that, CRS is completely useless. When we tried to roll out Shotgun to a smaller project here, that was exactly the thing that torpedoed it for the creative director. We had to post the full 2 minute piece each time (about 25 shots) and then we’d have to cut & paste all the comments into notes on the individual shots afterwards - it was not an attractive process and did nothing to advance Shotgun as a project management tool in this person’s experience. (And he wasn’t wrong.)


Very elegant solution if you have few enough client users to add simultaneously. Others have said this, but I wanted to stress the importance of the SG team bringing the requested functionality into the CRS. In our case, with the number of clients we have on current projects, and lack of CRS ability to simply share or document playlist links (or the ability to click through previous versions to compare visuals or review past feedback), these issues will most likely force our hand to move to FrameIO, which have these very necessary client-facing functionalities. FrameIO is missing the user-side pipeline functionalities, but we really need our clients and producers to be well-equipped. Would like to continue following this thread in case the SG CRS is updated, as it would be preferable to keep it as part of our pipeline. Thanks all very much.

1 Like

Hi Guys! I’m having the same trouble with a client losing the links in the email.
I guess the Vendor permission role is made for this purpose, but our budget is very low, so we can’t afford to spend an extra shotgun account only because our clients don’t know how to bookmark a page : (

I will try something similar to what I do when sharing links from wesendit, wetransfer or other sharing platforms, I prefer to send the link to me, and then share it with the person, so I can have a copy of it in case he loses it.
Any suggestions, observations, errors are welcome!

  1. I will change the clients user email address to a custom one, a gmail account made only for this purpose, in the case of a new client I will set the temporary password manually by myself.

  2. I’ll set this gmail account with a custom filter per client, to automatically forward all incoming shotgun email to the real client email address. I will use this gmail account as a bypass filter, where I can see exactly what the client is receiving.

  3. Then I’ll send the invitation of the playlist to this gmail account, or click “Re share with selected” for already shared playlists, once the clients email has been switched for the custom one.

  4. Using Google Sheets or something like that I will collect all the links of the shared playlists into one sheet, and share this with the client, so he can have a bookmarks page with all the links, and probable other annotations in there too.

Suggestions for CRS so I don’t need to do what I just said.

  • Is it really no way to get the shared link with the API? this will help a lot.
  • Listen to Client Review Site events, so I can trigger a custom script.

Thanks for reading!!

I can’t hahahaha! At least not with a regular gmail account, I can’t not use the same email address for different client users, and also there is no text in the email body that says to who is the email addressed to, so I can’t filter them by client.


Hi @macbeth,

Sorry for the complications - not having that “See all my Playlists” view is definitely on our radar when we get the CRS on our roadmap. I admire your tenacious spirit with attempting to find a workaround!

With regards to your suggestions:

  • Is it really no way to get the shared link with the API? this will help a lot.
  • Listen to Client Review Site events, so I can trigger a custom script.

The first one is a feature request - I highly recommend submitting it under our roadmap and select “Submit Idea” at the top right of the page. Please note, a submission will not send a confirmation email back to you, but we will see your request in our productboard. Also, please include the CRS Playlist Admin view as well! the more votes the better chance it will become a reality!

The second, that is a great question, we have never actually tried from the tech side to see if that works - @bouchep said “I’d hope some events like versions being viewed would be generic enough that they would show up like any other user causing an event.” we’d love to hear how it goes if you get a chance to experiment!



Thanks a lot for your answers! I will submit this feature requests thanks.

In the short term maybe having a CC email in the user client entity will be very handy : ( just to keep a copy of all the emails send to them.