How do I add an app to a group?
When I click "Add" from the list of apps I'm taken to My Apps page. Then what? From "My Apps", I click on "Manage my billing account" > Manage Billing Account Summary tab > Groups > "The name of t...
Forum Discussion
Hi Jim,
I'm sure you've found your answer by now, but I'd like to pontificate a bit, in case it helps new users, like myself from 45 min ago.
It seems that 'groups' are not intended to have or manage permissions, but only exist in order to group 'users' for easy role assignments. This may seem obvious once said out loud, but not to those of us used to other softwares' ACM systems, in which you set up group permissions, then alter those with individual permissions.
So, you never actually add groups to an app in order to enforce permissions, but rather users to a role. Groups only assist in facilitating the process of adding users to a role by allowing you to add several users to a role all at once, via the group. (Click add user, then search for and add your group to add multiple users)
Further, access to your QuickBase app is only restricted by roles, which users can belong too. Also, order matters.. If you have a user that has multiple roles, the top role literally trumps the one beneath it, so you have to plan your 'role-stacking' appropriately.
To me, this seems bad. But, I dunno. Once I'm used to it, maybe I'll better understand what is going on and enjoy it. I'm starting to think that my app design is flawed in QuickBase; and that QuickBase really wants me to plan my work in a more modular way. Like the world of the internet, we developers are trending towards the idea of microservices, which may be the solution here.
No more robust and all-encompassing solutions, but rather small apps managing tiny concerns and authentication schemes that are able to be stacked into larger and more meaningful things. I may be wrong because I'm fairly new to all this and have a lot more to read / watch (unfortunately), but this is my understanding as of now.
I hope it helps,
Rob
I'm sure you've found your answer by now, but I'd like to pontificate a bit, in case it helps new users, like myself from 45 min ago.
It seems that 'groups' are not intended to have or manage permissions, but only exist in order to group 'users' for easy role assignments. This may seem obvious once said out loud, but not to those of us used to other softwares' ACM systems, in which you set up group permissions, then alter those with individual permissions.
So, you never actually add groups to an app in order to enforce permissions, but rather users to a role. Groups only assist in facilitating the process of adding users to a role by allowing you to add several users to a role all at once, via the group. (Click add user, then search for and add your group to add multiple users)
Further, access to your QuickBase app is only restricted by roles, which users can belong too. Also, order matters.. If you have a user that has multiple roles, the top role literally trumps the one beneath it, so you have to plan your 'role-stacking' appropriately.
To me, this seems bad. But, I dunno. Once I'm used to it, maybe I'll better understand what is going on and enjoy it. I'm starting to think that my app design is flawed in QuickBase; and that QuickBase really wants me to plan my work in a more modular way. Like the world of the internet, we developers are trending towards the idea of microservices, which may be the solution here.
No more robust and all-encompassing solutions, but rather small apps managing tiny concerns and authentication schemes that are able to be stacked into larger and more meaningful things. I may be wrong because I'm fairly new to all this and have a lot more to read / watch (unfortunately), but this is my understanding as of now.
I hope it helps,
Rob