12-13-2017 06:48 AM
Is there a way to unilaterally disable a user's access to a database remotely, or better yet to delete a remote database remotely?
I don't need to do this at this time, but I'd like to have the ability to disable access or delete the remote database of a user should we terminate a working relationship with them, and not worry they'll continue to have access to client data.
I understand I could likely get the solution I want by simply limiting to web based access, however I generally prefer the remote database solution over the web based access, simply for the speed of the process and larger feature set.
12-13-2017 08:41 AM
Some companies usually sign a confidentiality agreement with users, the business information of the company should not be used outside of the permitted work parameters or after the employment relationship has ended.
The remote database can be disabled on the server, so that the next synchronization is blocked on the remote user's computer
Before you can Delete a database or disable Synchronization from the Parent database you must Disable Sync for the Remote database. Use the following steps to Disable Sync for a Remote database:
The issue is ... if the person does not synchronize again their database will be able to have unlimited access to this information ... then... in that case the best way to manage security is... that users work by web and mobile
I do not recommend removing the user, it is important to keep the story, it is better to inactivate
If you need to change a user from Activate to Inactive (or vice versa), follow the steps below
In user administration, you may not want users to be able to export the information to EXCEL or delete records
Additionally, custom permissions may be granted by the Administrator to Manager and Standard users to allow them to perform additional tasks within Act!. These custom permissions are:
12-13-2017 10:09 AM
I would also suggest changing the user's password so that they can't log in after the next time they sync.
12-13-2017 10:14 AM
Thanks for the details. Glad to know there is a solution. I can understand why a sync is required, though I understand why it is necessary.
We have a confidentiality and data use agreement with our team, however I prefer to prevent issues where possible rather than litigate them. Far less expensive on all sides.
Will have to think about how to make this all work best.
Thanks again for the input.