I have a need to disable BO access while we work on server migration except for myself and few others. This is not unitl 2 weeks, but we need to know how this can be done since there are 200+ users that need to be updated (and don’t want to do this manually)…
lots of choices if I remember from past posts.
If they all run thru the server, can you stop them there via IP address.
Or change the server url
Or do something in Supervisor with timestamp and group
Or update the repository actor table
or gen a new key file different from the last
Try:
You could disable the database user account which was used to create the original *.key file.
Then create a new *.key file with a new database user account and use this new *.key file for yourself.
You could also use the import/export function of Supervisor or modify the repository directly (which as always is unsupported).