Optimizing Quickbase Admin Console Connected (Sync) Tables for Effective Governance
Approximately 5-minute read In the ever-evolving landscape of data management, Quickbase's Admin Console Connected (ACC) tables (known also as Sync tables) stand out as a pivotal tool for administrators. These tables are more than just a feature - they represent a methodology for streamlined data governance and management. This blog post delves into the strategic setup and utilization of ACC tables, guiding you through a journey of efficient administration and governance of your Quickbase realm. The Governance Core Apps To establish a comprehensive governance framework, realm admins need to create three core applications. These three apps lay a solid foundation, which allows for easy expansion and subsequent modifications. For in-depth instructions, go to the Exchange and search for "GCA Instructions". This app will guide you through the build below: Step 1 - Create an app called Admin Console Sync Hub: This is the centralized location for all ACC tables and is crucial for warehousing data points that the realm admin will use in the Realm Insights app. Less is more in this app. It is not advised to add relationships, reports, roles, users, etc. This is essentially a data repository that updates according to the app manager's specifications. ACC Tables currently include Applications, Users, User Access, User Tokens, Pipelines, and Connected Tables. It is important to create this foundation to prepare for future tables that will be added. Step 2 - Create an app called Realm Insights: This is where the Realm Admin will analyze all realm data to get a holistic understanding of the realm and its overall health. It shows how Apps and Users are being utilized and what they interact with in the Realm. It will also help develop, enforce, and maintain policy with Quickbase and ensure alignment with your company IT strategy. Step 3 - Create an app called Realm Logger: An advanced audit log that tracks specific attributes with a defined granularity. Some examples of data tracked would be App Deletions, User Token Additions, User Token changes, User Access additions/removals, App Manager changes, etc. Through the utilization of Pipelines, this app creates logs from changes in data in the Admin Console Sync Hub app and the Realm Insights app. Governance Core Apps Overview It is important to note that each ACC table should come with a Pipeline. The Pipeline has multiple purposes. It copies data from the Admin Console Sync Hub into Realm Insights. It also logs its results in Realm Logger and tracks changes, additions, or removals of the data that was interacted with. ACC Table Pipeline Process Example The ACC Table of Applications updates once a day. When the table updates, the Apps Pipeline fires. It updates the Realm Insights Applications Table with the updated data. The Pipeline then compares the updated data and removes all records (apps) that are no longer in the Apps Table of the Admin Console Sync Hub. These records are then added to the Realm Logger Apps Deleted Table. Now the Realm Admin can see all Apps deleted in the Realm and the attributes they choose to maintain. Separation for Simplification A common question is why this solution keeps the Admin Console Sync Hub and its ACC tables separate from Realm Insights. While integrating directly into Realm Insights is possible (and often necessary for certain API integrations), maintaining separate entities simplifies app management. This separation prevents the need for re-architecting Realm Insights with each new ACC table addition, enabling a more streamlined update process through pipelines. This method has proven easier to scale and allows the client to build the solution as they see fit. There are a wide range of building skillsets, and technically, you may not want a pipeline per ACC Table. You may want to use one pipeline or twenty. The point is to prepare for scale and keep applications limited in roles and scope so that a "Franken-App" does not occur. Use Cases Users – Users in the Realm How many non-company emails are being used in the realm Anytime a user changes permissions: Can Create Apps Realm Approved Realm Admin Super User Pipeline create permissions App Admin Can Create User Tokens Non-Realm Approved Employees Users to Deny (based on length of time not accessed) Users that have Never Accessed an app, but still have Access Access – Users and their app access # of App Access per User App Level Permissions per User per App # of Apps Accessed per specific timeframe Apps – Apps in the Realm How many applications have not been accessed in 90/180/240/360 days # of Apps per App Manager Apps Created per Year Everyone on the Internet Apps Apps with or without Vendor Access Anticipating Future Expansions Quickbase's commitment to growth is evident with the planned introduction of new Admin Console connected tables, encompassing Groups, Tables, Pipeline Access, and Solutions. These additions, expected throughout 2024, highlight the need for a robust foundation to facilitate easy scaling. Conclusion The ACC tables are more than just a single feature. They are a cornerstone of effective Quickbase governance. By understanding and implementing these strategic practices, you can transform the way you manage your realm, laying a foundation for growth and efficiency. As more data points become available, scaling becomes much easier as you mature with the product and the product adds additional ACC Tables and APIs. Explore more about connecting ACC tables in our help center article. For in-depth information and if you need further assistance, don’t hesitate to reach out to your sales or service support contacts.
Still no way to hide 'New App' button?
Is there still no way to hide the New App button? It's the first button everyone tries to click, so I receive about 10 requests a week to try to create new apps. Has anyone come up with a way to remove this button?? ------------------------------ Michael Tamoush ------------------------------
Recommendations on when to delete or archive contacts
Hi We use QuickBase for our CRM with many contacts who are related to companies, who have notes. (Three related tables.) We have a long term relationship with our customers that spans years and doesn't end at the sale close. If I have notes on a project with "Bob Smith" and he leaves Company ABC, what should I do? What makes the best sense to do with his contact record? Option 1. Delete Bob from the contact table: Pros: this is what my sales people say they want. Since he's gone, they don't want to see his name in the system. We may have many contacts, and we don't want to be confused about who is there and who is not. We may be working with a large account that has 20 contacts for 5 different projects over the course of several years. They have a hard time figuring out who is currently relevant. Cons: any notes related to Bob will show up with no contact since he no longer exists. Is there a way to keep his name associated without him being in the contact table? Option 2. Set Bob to a type "archive" Pros: as a separate type I can easily filter him out of the main contact list on the account; his name will still show on notes so the sales team can tell who old notes are related to, even though he's not there. Cons: in the global search, if I search for Bob, he will still show up (is there a way to filter the global search?) This is a problem with people with common names. I could have a different Bob Smith at another company. Also, it often happens that contacts who job hop, end up contacting us from their new company, and then we now have Bob Smith at Company XYZ. I already have 16000+ contacts in the database; keeping people extra people seems silly. Is anyone else using QB in a similar way? How do you do it? What do you recommend? I'm leaning on the "archive" method, but it's my sales team that has to be happy. I appreciate any suggestions on how to structure this. Kim ------------------------------ Kim Gardner ------------------------------
How we can version control in QuickBase?
Hi Guys, Any idea how we can do version control in Quickbase, so I have capability to rollback the changes or do work with my team parallelly? Also please let me know if we can create different environment like QA, Development, Staging and Production? Many Thanks Saurabh ------------------------------ Saurabh Rathi ------------------------------
