When to use restrictions and group assignment
I wondered if you can help as I'm struggling to understand the difference between Restrictions and Group Assignment in the Licence Properties tab, and when you would use either to lock down a licence.
On our FNMS instance, we purchase entitlement in each individual market that we operate in, so the UK and Canada for example. We then have one licence of that product so Adobe Acrobat Standard DC 2020, in which we allocate the Purchase and Entitlement to that market under Group Assignment.
Or should we be creating a licence for the product for every market we have purchased for, and then use Restrictions to define the parameters of the licence. So for example Adobe Acrobat Standard DC 2020 | UK, we then attribute all UK purchases to this licence, and then use Restrictions to restrict this licence for the UK only.
The point to note is if we purchase a licence for use in the UK, we do then share this with our other markets.
Any thoughts would be welcome.
Restrictions would normally be used when there are (legal) license entitlement restrictions that need to be enforced when license compliance calculations take place, please refer to the Restrictions Tab section of online documentation.
Group Assignment can be used when the license may be pooled, e.g. company wide and data is "only" used for internal charging. In this case, a branch office might be out of "internal compliance", but some one else is consuming less, overall you might still be compliant.
Restrictions are normally used when there are hard limitations, like language specific releases only valid in a region or country, preventing global pooling.
You might also want to consider tool- or process-related limitations. If you plan a complex access rights/roles schema in FNMS, dedicated licenses might help you limit what people can access.