ContributionsMost RecentMost LikesSolutionsThrowing out a Quickbase idea!! I'm on the Qcrew meetup for cascading permissions, and it reminds me how much I detest the (necessary) zillions of tables we might create, and how they are potentially confusing for an end user. I know we can hide tables, but they're also a lot to look at as an administrator. Would Quickbase ever consider a sort of self-designed table organization structure -- wherein users can organize tables in nests that make sense for the user, like a folder structure (of course, some tables are children under multiple parents) -- or maybe even offer a dynamic structure offering? The sheer number of tables can be incredibly overwhelming as apps get more complex. Changing owner of notifications - role limits? Hello! What drives the drop-down menu in the "change owner" email list in notifications and subscriptions? My list comprises of me (only person with app edit permissions), and my system office's realm manager (I think that's what their role is anyway). I need a middle-ground to change subscription ownership to my team members - including those who otherwise have full app access, just not app edit permissions - as well as a new role coming on board that will have more limited access, but will be crafting their own notifications. Thanks! Re: Minimum role permission level needed to toggle/adjust notifications Thanks, I think so but on my test run, my colleague who is now no longer an admin couldn't see all of the ones she indeed was the natural owner of - only one report showed, and the rest were hidden from her. I am hopeful any that she creates from here should show, but not sure why those legacy ones didn't -- I did try to "change owner" but saw I could only even change it to myself or the realm owner. Re: Minimum role permission level needed to toggle/adjust notifications Bumping :) Re: Audit logs - Is there a way to see previous detail Bumping! :) Re: Audit logs - Is there a way to see previous detail Updated thought: Is it possible I didn't change the name of this field, but just added it to a form that it previously wasn't on? I think this might have been the case. I went through a fairly significant comb-through and cleanup, mostly aligning our previously-titled fields to the report we have to compile, and I do NOT remember changing this field's name/am not gleaning anything from the audit log about what exactly the field update was. My suspicion is I just put it back on the form thinking I removed it with an accidental mouse-click. (The form is a legacy form type). Minimum role permission level needed to toggle/adjust notifications Is there a way to give permission to users who are not app administrators to create and update notifications? I'd like to have my future-anticipated team be able to create and manage notifications, however it seems that my current end users who have nearly universal access to my app but are not administrators can not get to that section. If it's not possible, I'd love to suggest that to be incorporated if possible since it would not interfere with the app's architecture in any way! Audit logs - Is there a way to see previous detail Hello! I cleaned up an app that I'm inheriting on Wednesday, and now am retracing my steps on a field that I *may* have renamed. I see the "field_update" in audit log, but is there a way to see what it was before the update? Another report question - tallying checkboxes in a report Hi all! Looking for ideas on how to draft a report that will tally how many records have more than one checkbox checked (of a series of defined checkboxes). Please and thank you in advance! Report help, take 2 Figured out my first one (well, kind of). I'm building a summary report summarizing several check-box fields. Two questions: Is there a better way to do this where I want summaries of a LOT of check-box fields? It looks like the cap of line items to summarize is 24 Do I have to "Group by Rows"? I basically just want a total summary, but don't want to group it. Speaking in Excel terms, what this might look like in an ideal world is: Rows that are limitless, identifying each field to summarize Columns are only two -- 1) The title of the field being summarized, and 2) distinct count Here is what I'm looking at, and I ended up just creating a summary field generally to just have one summary row.... but really, I just want the bottom line.