A quick proposal to at least partially resolve SONAR-16030. I think the problem is essentially Baner blindness and thus generally a banner is probably the wrong pattern/component to use regardless of where you place it and how prominent you make it.
My suggestion would be to design this message such that you make sure users would read it by adding interactivity, a checkbox, and relocating it where it may make more sense contextually.
Whenever an admin signs in (make the Log in button depend on the checkbox)
(a small note here that there is a Cancel button on the Log in screen that doesn’t seem to do anything, I omitted it in my mockup)
Similarly, you can do the same thing in the context of creating a new project: the user will have to consent to this database limitation in order to create a project. Thus they’ll either address the situation or contact whoever is in charge of that.
Thanks again.