Deliver superior customer experiences with an AI-driven platform for creating and deploying cognitive chatbots
Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
A complete cloud platform for an app or your entire digital business
Detect and predict anomalies by automating machine learning to achieve higher asset uptime and maximized yield
Automate decision processes with a no-code business rules engine
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Personalize and optimize the customer experience across digital touchpoints
Build, protect and deploy apps across any platform and mobile device
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
The content you're reading is getting on in years
This post is on the older side and its content may be out of date.
Be sure to visit our blogs homepage for our latest news, updates and information.
Today I am going to take a look inside a functionality, which is not used every day and even the people who have seen it before tend to forget it and… that also includes me. In the next few paragraphs, this post will quickly reveal what happens when the maximum number of concurrent backend users is reached.
To clear any confusion down the road, I want to briefly explain what is the meaning and the logic behind the notion of a concurrent backend user. Sitefinity CMS separates the users into two main types – backend users and everyone else. The backend users are all the users who have permissions to access the administration pages of Sitefinity and execute various content editing or other CMS actions. Each Sitefinity version has a certain licensing differentiator, which defines a limitation on the amount of such backend users who are simultaneously logged into Sitefinity.
With that said, let’s see what happens when a backend user tries to log in when already the maximum allowed users limit is reached.
The user enters his/her credentials and a new dialog opens showing the currently logged in users. In the image below you can see what is presented to the less powerful user:
Now we have a more powerful user stepping in and things are different. Admins now see the button saying "Force someone to logout":
Once they click that button, admins have the ability to select any of the currently logged in users and they can forcefully log off any user so they can get their job done:
That's it! I told you it is going to be a quick one. I hope that if you came here searching for an answer, this article was what you were looking for.
View all posts from Peter Marinov on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Copyright © 2018 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.