How to stop user(s) requesting permission to create applications billed to the account
We are periodically getting an email from users stating they are requesting permission to create applications billed to the account. Checking in with one of the users, the request to create an app cam...
It's not a popup, it's an errant click on your users' part.
The apps ribbon looks something like this:
And when a user without app creation permissions clicks on 'New App', which always appears to the right of the 'tabbed' list of apps they've lately accessed, it will send the account owner the email request you're describing.
We have one user who does this HABITUALLY and it took us a while to figure out what was happening. I can all but promise you that if you take this description to your user(s) who are 'randomly' getting these 'popups' they will reveal that they do in fact regularly click on that area of the screen - probably the table home page that appears under that screen real estate, for their role (since the table home page button ribbon is what goes under the apps ribbon).
Unfortunately as I understand it there is nothing you can do but ignore the emails without taking some truly drastic and probably undesirable measures in the BOL realm. Though you can at least rest assured that those emails can safely be ignored.
You might be able configure your email client to route these emails to a special folder or delete them based on some unique content in the email that distinguishes them from other QuickBase emails.
> ... taking some truly drastic and probably undesirable measures in the BOL realm ...
I would not characterize using any script solution as drastic or undesirable. Script allows you to solve problems like this almost immediately without forlorn appeals to QuickBase or suggestions that languish in UserVoice. Instead of "I have been asking QuickBase to do this for several years" you will be saying "I knocked that feature off in a mere 10 lines of script. What is the next problem to solve?"
I would use a Service Worker to do this as once setup it will operate against the entire account. The BOL operates against all pages withing an application, and would have to be setup in each application the user had access to.
In either case, the only mildly challenging issue is deciding if the current user should be allowed to see the "new app" button or access the "new app" functionality. Do you decide access based on a whitelist or blacklist of user ids, user names, role ids, role names etc?
