Thanks for the suggestion. I think Cloud Zoo may already be able to support this particular use case by splitting the licenses between two teams and have some users be members of both teams, for example:
Team A (Construction): 3 licenses
Team B (Accounting and Education): 2 licenses
Those in the Construction department could be members of both teams, whilst those in Accounting and Education would be members of Team B only.
It might help also for the Construction dept to enable “ManualEntitySelection” to ensure that they’re using Team A where possible.