How do I add an app to a group?

Are you trying to invite a group to use the app?  If so go to Users icon, then the green Invite button and then start typing the name of the group until you see it  and invite the group.  Let me know if it solve your question.

No, and here is the path I take that leads up to my question.
Manage Billing Account Summary tab > Groups > "Group Name" > List Applications Accessible to this Group > Select 'Search for text in the name or description of an application' and I search for "My App Title" > Search > Select 'Add' in Search Results > taken back to My Apps page.

Well, now I no longer understanding your question.  Can you explain what you are trying to accomplish?  You question was "How do I add an app to a group".  I'm not understanding the question.

I am trying to add an app to "My Group Title."

Sorry, I don't know what "My Group Title" is.  Can you get a screen shot and post it to your original question and then comment so we know that you have done that?

Screen shots attached. I'm sorry if my vocabulary doesn't jive with what I'm describing or wanting.

Wow, we definitely have a terminology problem.  

A group is a collection of Users. Typically this might be like mycompany.all.managers as a name.  Then when you want to grant access to an app you do not need to list every manager, you just give the group access.

You are talking about what appears on your My Apps page. When you are on your my apps page there is a box called category.  You can make your own personal categories if you like.  Some people at least do a category called "favorites" and then each app is either in our out of your favorites.  So then you can filer to just show your favorite Apps which would be a shorter list.

I appreciate your time.

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

Rob, I want to just correct one thing that you said above. When it comes to actual permissions of what a users can view and modify and permissions to add and delete, QuickBase will give the most permission as possible when a user is in multiple roles.

The area of QuickBase where the sequence matters is for example which user interface they experience, such as which dashboard and whether or not they see certain Table icons. Since a user can only land on one Dashboard, QuickBase decides that by the sequence of the Roles.