This is the scenario:
A connection is tied to user X.
A report uses that connection tied to user X.
User Y logs in, that's 1 seat consumed - All OK.
User Y accesses and edits the report mentioned - The system now logs seats for user X as well.
This licensing structure ends up consuming many seats.
The improvement is for the system to recognise only user Y's seats, and not user X.
For more details, please refer to the support ticket in the internal comments and contact the partner directly if needed.
