Welcome to the Bentley Subscription Services user feedback site. We value your feedback, and our team regularly reviews your ideas and considers them for future improvements to our products and services.
You have 3 options for providing feedback:
VOTE for an existing idea. The popularity of an idea helps us understand its importance to the community.
COMMENT on an existing idea. We want to hear your unique point of view.
ADD a new idea. You can always submit a new idea if no existing one describes your suggestion.
When you add, vote or comment on an idea you will also be subscribed to that idea and receive status updates. Please note we may merge or rename ideas for better clarity for the community. Thank you for your support and feedback.
Connection Client -Same Login on Multiple Machine. It should be avoided to use same user login on multiple machine
We do have access controls based on the user signed in. I'd recommend using those tools to control who has access to the product until you've had a chance to educate the new users on what you expect them to do in cases where they receive the threshold alert.
Hi
It seems pretty good that the option is available to login on multiple machines.
But we experienced some issues.when same user use login on multiple machine and we don't have option to block the other users machine instead to go for uninstall.
Sometime the user who are intern or new when acknowledge the additional license then it comes to QTL.
Either login option must be on one machine or controlling managing mechanism should be introduce to control the other user attempt.
Regards
AbdulBasit
Thanks for the feedback. I'd like to understand better what you're asking for. What is your goal for this limitation? There are many valid use cases where a user needs access on multiple machines to the resources that require signing in to our Identity Management System. If we introduced this kind of limitation, it would just be a burden on users who do require multiple machines to do field work.