User Seats and ShotFlow Capture Connections

Modified on Fri, 28 Jul, 2023 at 10:33 AM


ShotFlow utilizes two different mechanisms to control access to the ShotFlow cloud: 

  1. User Seats - tied to a unique email address and utilized for access to any ShotFlow component (web browser, ShotFlow Capture, Samples & Styling Mobile App)
  2. Capture Connections - limit on the number of concurrent ShotFlow Capture connections (simultaneous active Sets)

User Seats


User Seats are enabled at the Account level based on who is financially responsible for that User Seat. A User Seat can access an unlimited number of apps (brand, studio, executive dashboard, etc.) at no additional cost, including accessing apps that may be billed to another Account.


Example: The ShotFlow User Seat linked to bob@heroapparel.com is billed to the Hero Apparel Account and has access to the Hero Apparel brand app as well as the OurStudio studio app. Based on an increasing volume of work, Hero Apparel decides to outsource additional production needs to TheirStudio Inc., who is part of the ShotFlow Network. ShotFlow connects the Hero Apparel brand app to the TheirStudio 1 studio app, and an Admin user also grants the bob@heroapparel.com User Seat access to the TheirStudio 1 studio app. This access does not change the billing arrangement for Bob's User Seat, it remains billable to the Hero Apparel Account, and there is no cost to TheirStudio Inc. to grant Bob access to the TheirStudio 1 studio app.


A single User Seat can access ShotFlow from multiple systems/devices within certain pre-defined limits. When over the limit, the oldest session is terminated (automatically logged out). 


Origins and limits are as follows (where 0 indicates no limit):

  • Asset Automation: 0
  • Capture Module: 0*
  • Mobile: 2
  • Public API: 1
  • Web Interface: 2


The same limits apply to each environment; however, each environment performs separate checks. As an example, a user can simultaneously be authenticated in Sandbox twice and Production twice through the web interface.


*Capture is also restricted by Capture Connections (see below)


ShotFlow Capture Connections


Capture Connections are enabled at the Account level and govern the capture activity for all User Seats billed to that Account. Capture Connections can access an unlimited number of studio apps and their associated brand apps at no additional cost, including accessing apps that may be billed to another Account. Note a local ShotFlow Capture instance can only access one studio at a time, and available studios are based on the User Seat having access to studio apps with appropriate role permissions.

Capture Connections limit the concurrent (simultaneous) number of local ShotFlow Capture instances that can access the ShotFlow cloud for User Seats associated with the Account.


When a user logs out of a CM session, only the CM sessions which match the user and hardware uuid should be ended.  Any other sessions for the user which are either not in ShotFlow Capture or have a different hardware uuid should persist.



Example: The Hero Apparel Account has paid for 4 Capture Connections. On a Tuesday afternoon, 4 Sets are shooting in the OurStudio studio app, and all of the ShotFlow Capture connections are using Hero Apparel User Seats. Bob attempts to log in to a 5th ShotFlow Capture instance using his valid Hero Apparel User Seat but receives a "Capture Connection limit" message when logging into ShotFlow Capture. This is because the number of Capture Connections for the Hero Apparel Account has been reached. If another Set shuts down ShotFlow Capture, then Bob can log in successfully on his Set. It doesn't matter whether the Capture Connections are all in the same physical studio or not; the limit is the number of ShotFlow Capture instances being simultaneously accessed by User Seats from the same Account, anywhere in the world.





Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article