JoshMillerQB
Quickbase Staff
Joined 3 years ago
User Profile
User Widgets
Contributions
What is the [User Agent] Field in Quickbase Audit Logs?
Example User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36 Edg/134.0.0.0 Full Breakdown: Part Meaning Mozilla/5.0 This is a legacy prefix. Originally meant "compatible with Mozilla browsers." Today it just signals "I'm a web browser" for compatibility. (Windows NT 10.0; Win64; x64) Operating system and architecture: Windows 10, 64-bit (x64 architecture). AppleWebKit/537.36 Rendering engine: WebKit (like Safari and Chrome use), version 537.36. Means the browser uses WebKit-based layout. (KHTML, like Gecko) Says the engine behaves like Gecko (used by Firefox). Another compatibility statement. Chrome/134.0.0.0 Browser engine version: Chromium version 134.0.0.0. Safari/537.36 Compatibility tag indicating Safari WebKit behavior (same as AppleWebKit version). Edg/134.0.0.0 Microsoft Edge browser, Chromium-based, version 134.0.0.0. What This Tells Us: Operating System: Windows 10 Architecture: 64-bit machine (x64) Browser: Microsoft Edge (Chromium-based) Browser Version: 134.0.0.0 Rendering Engine: WebKit (via Chromium 134) Note: Although Chrome and Safari are mentioned, the real browser is revealed by the Edg/ identifier. Quick Tip: Identifying Browsers Edg/ = Microsoft Edge Chrome/ without Edg = Google Chrome Firefox/ = Mozilla Firefox Safari/ (without Chrome or Edg) = Apple Safari Splitting the User Agent into Useful Fields: Field Name What It Captures Example Value Browser Name The name of the browser Microsoft Edge Browser Version Full version of the browser 134.0.0.0 Operating System The OS platform Windows 10 Architecture CPU architecture type 64-bit (x64) Device Type Desktop, Mobile, or Tablet Desktop Engine Name Rendering engine (WebKit, Blink, Gecko, etc.) WebKit (Chromium-based) Engine Version Rendering engine version 537.36 How This Would Look When Split: Raw User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36 Edg/134.0.0.0 Browser Name: Microsoft Edge Browser Version: 134.0.0.0 Operating System: Windows 11 Architecture: 64-bit (x64) Device Type: Desktop Engine: WebKit (Chromium) Engine Version: 537.36 Conclusion: The User Agent field in Quickbase audit logs isn't just technical noise — it's a treasure trove of insights. By understanding how to read it, you can better identify user environments, troubleshoot access issues, and improve your governance practices within Quickbase. Next time you see a long User Agent string, take a closer look — the story it tells might surprise you!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.
Groups
Realm Admin Qrew
Where Realm Admins help other Realm Admins Realm Admin.
