You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
This request is similar to #3619, but prevents other users from working in the database at all.
Sometimes I need to work directly on the database, or I want to do a massive operation with the workbench, and I’d feel more peace of mind if I were to know that no one else is working on the system at the same time (though I know WB has been designed to address concurrent access, and I could stop the web server when working directly on the DB).
Institutional scoping might add complexity though, putting a whole institution on maintenance, or just a division or a discipline… 🤯
But let’s say a maintenance mode at institution level, that would only accept logging from institution admin and show a “maintenance mode” screen to any other user.
Describe the solution you'd like
...including a “Maintenance mode” 🛠️ entry in the User Tools menu ?
Reported By
Philippe Verley at IRD via the Speciforum
The text was updated successfully, but these errors were encountered:
To add to this, I am not sure how common it is with the various monitoring providers, but ours has the ability to add in an announcement banner into applications that syncs up to maintenance notifications on the status page.
Obviously not super critical, but a nice to have if easy to work into the implementation.
Is your feature request related to a problem? Please describe.
This request is similar to #3619, but prevents other users from working in the database at all.
Describe the solution you'd like
Reported By
Philippe Verley at IRD via the Speciforum
The text was updated successfully, but these errors were encountered: