Suspending an employee's OneClick account
Currently when suspending an employee's OneClick account you only have the option to replace that employee with another for the OneClick team. What happens if you don't know the replacement yet or your firm has decided not to replace that employee because they are more junior or a member of the admin team perhaps? The solution that was given was to just replace with anybody, well that doesn't always work and you don't want your clients to see a random person in their team. The alternative is to change the employee's email address so when they try logging in they don't actually know the new email address. Ok, yes but the account is never then closed and will remain open forever.
It would be great to have the ability to choose whether you replace the leaving employee with a new one or not - this was my understanding anwyway from the beginning.
Caroline Hoare
shared this idea
-
Cara Cole
commented
This also causes a lot of problems for us - we are forced to select a replacement then have to manually enter every client record to remove that person from the client team, which isn't the work of a moment
-
Martin Chapman
commented
When an employee leaves their client list is usually divided up between a number of staff members. With the need to update Assignments and Client responsibilities the number of changes runs in to the hundreds and sometimes will be into the low thousands. This year already we have processed over 3,000 changes. Historically these have been applied via a script however we have been informed by support that only changes made via CCH Central will actually update the cloud service. Given the volumes involved this isn't practical - nor is the current Bulk Update.
If it cannot be made possible for these changes to be made via a script then we require the need to upload a spreadsheet which would contain details of the changes that need to be made for Central to then process each of the changes line by line. Currently we produce a spreadsheet which details the team type (client or assignment), client code, client name, whether they are OneClick activated or not, assignment name, name of the current individual, their employee code, the responsibility type, a column for the replacement employee code and then the assignment code.
-
Caroline Hoare
commented
Further reasoning has been provided on why you must replace with an employee, which I do understand, in cases where that employee is the only person in the client team. Could the system perhaps suspend the employee. ask if we want to replace with another, if yes great, if no it does a scan of the client team and if they are the only person it flags this up and doesn't allow you to suspend until you resolve this but if there are other staff members in the client team then they get suspended.