Given the nature of SharePoint and Flex, there should be no behavioral differences in performance from user to user. The only distinction that could come into play are the Permission levels of each user or group (this is not an error condition but an imposed restriction).
Also falling into this category are List Threshold settings that may play a part differently for users compared to Admin Accounts - again this an imposed and modifiable restriction.
Therefore, any support issue that is a single user or multiple user specific but not general to ALL users cannot be the responsibility of Flex. We call this situation a Single Point of Failure, which means that the error state must be common to all users given the same conditions to be accepted as a bug or a Flex issue.
If a situation occurs where one user performing a standard task gets an error or malfunction, this situation must be tested with another user under the same condition before it’s brought to our attention. This is all predicated on each user working with the necessary components installed and equal access across the board.
The Single Point of failure rule follows if the problem occurs to one user but not to other users given the same conditions. Under this condition, the issue is not Flex specific but rather an outcome of some condition, or due to some influence, outside Flex. Since Flex is (as is SharePoint) web-based, it is at the mercy of browsers, firewalls, network restrictions and configurations that can have a detrimental effect on the user base access and online performance.
Before contacting support@lookout-software.com please consider the above information and send the necessary details to help in isolating the problem.