to gain exclusive access for administration updates
by: Stuart N. | over a year ago | Setup / Environment
Completed
238
Ability to kick users out the system
by: Stuart N. | over a year ago | Setup / Environment
by: Stuart N. | over a year ago | Setup / Environment
to gain exclusive access for administration updates
by: Stuart N. | over a year ago | Setup / Environment
Comments
Or to free up a license when someone's logged in but they are not at their computer and it is locked. That would be handy.
Overall the area of more powerful administrator control could use some attention.
If we kick someone out of the system - can we cancel whatever they are working on that that point? How do we know if there are no unfinished work that is done on that machine?
See also idea already suggested (with many votes) "Log users off the system without breaking DB connections manually"
Definitely a really important ability
This Sounds gooooooooooooooooood 2 kick out user
if we knew the user's status, could decide to break or not.
Definitely a good feature to have access too. However,this feature should also give you info on what a person is working on (i.e journal entry etc) before you make the decision to log the user out of the system. A solution could be a message system that allows you to notify persons to log off the system but it still does not always answer the problem about a person away from their desk. Maybe, if there is a time out feature on leaving an entry without inputing information. It could deter persons from leaving their work incomplete.
I want to limit the access by controlling the number of Accpac lanpak licenses that are allocated to each department. For example, max of 4 users from Finance Dept, and max of 2 uers from IT Dept.
A MUST add is the ability to kick CRM out of the system. CRM is now bundled with Accpac and cant be treated separately. For example, all of the code change tools will not function without stopping CRM. And it is NOT acceptable that finance cant use any of these out-of-the box standard tools until I.T. stop CRM!
i have been waiting if we can kick user out of the system and no need to call to the list of lanpack users who have been idling
It would be a very useful feature. But care should be taken not to log off user if he is already running a program. It may lead to incorrect data if we log off a user who is posting a batch or running day end process.
If the feature enables ADMIN to take over the users' Accpac session, then ADMIN can see what the user was doing, save their work, complete the users' task, and make an informed decision to log them off in an orderly fashion.
good idea to kick out someone from accpac
Totally agreed on this.
Or if the user has not been active on Accpac for more than half an hour, log them out automatically. Especially if they forget to log out at the end of their work day.
This should be marked as Completed. Sage 2014 SP2 does this
movement at snail pace