Andy,

Andy,
Dave is absolutely correct.  There are two types of licensed users for Build Forge.  One is Authorized and the other is Floating.  An Authorized user license can be used by one person and that person alone.  Thus, their license is always available for them to use.  A Floating user license can "float" between different users.  In this way, you can "oversubscribe" the number of users to the number of licenses.  For many organizations using Build Forge, it can make a great deal of sense to share licenses.  Not all users need to access the system at the same time.  If the user base is geographically distributed and their working hours are staggered, then it makes sense to be able to have fewer licenses that are shared between a number of users.  There are many other reasons why sharing makes sense.

Now imagine that inside this community of floating users that some may be build engineers, some may be operators, and some may be simply guests, where they can see build results, but not execute projects or edit projects.  If the ratio of actual users to floating licenses is optimized, there should be very few times where there are more users wanting to access Build Forge than licenses available.  On those occasions where demand is greater than supply, then you would probably want your build engineers to have priority over less critical users such as guests so that the build engineers can log in and perform critical duties.

You are correct in thinking that this priority user setting is redundant for an authorized license.  Just keep in mind that a Build Forge console will recognize either floating users or authorized users, not both.  Given this limitation, I always recommend that organizations purchase Floating user licenses.  It always seems to make more sense than Authorized.