Can I kick someone out of a session?
Hi.. In Software Planner I don't see the ability anywhere to kick a user out of a session (if logged in). I do have my session timeout set at default (30 minutes)... but was wondering if Software Pla...
Forum Discussion
Hi Barbara,
Customization of the timeout is one of the must features indeed. Great to know that it will be available soon.
However, I still think that web tool that has no means for the administrator to forcibly close user session exposes very serious usability risk for the customers. I don't think that a lot of teams/companies purchase a lot of extra licenses just to feel safe that there is a pool of available licenses to be used while orphaned sessions are closed by timeout. Without something like site license, it seems to me that the more common situation is when the number of purchased licenses corresponds to the number of team members. The usual deviation is to have not a big amount of extra licenses if team expansion is planned or on the contrary purchase two-three licenses less for those people who work with the tool not on the regular basis. The latter case may result in the situation that there will be no option to forcibly free a license for some team lead who needs urgent access to the tool. This is the reason of why I think that licenses management is a high priority functionality for the collaborative web tools.
Customization of the timeout is one of the must features indeed. Great to know that it will be available soon.
However, I still think that web tool that has no means for the administrator to forcibly close user session exposes very serious usability risk for the customers. I don't think that a lot of teams/companies purchase a lot of extra licenses just to feel safe that there is a pool of available licenses to be used while orphaned sessions are closed by timeout. Without something like site license, it seems to me that the more common situation is when the number of purchased licenses corresponds to the number of team members. The usual deviation is to have not a big amount of extra licenses if team expansion is planned or on the contrary purchase two-three licenses less for those people who work with the tool not on the regular basis. The latter case may result in the situation that there will be no option to forcibly free a license for some team lead who needs urgent access to the tool. This is the reason of why I think that licenses management is a high priority functionality for the collaborative web tools.
