Links Banner
Main Content
Recent Content
Mastering Your Inherited Quickbase App
3 MIN READ The 90-Day Framework New admins can quickly build confidence by following a structured 90-day approach instead of diving straight into fixes. Days 1 to 30: Learn the organizational goals and business processes an app supports. Identify priority apps and build your Quickbase fundamentals before trying to solve problems. Days 30 to 60: Prioritize tasks. Determine which apps or issues need immediate attention and which can wait. Days 60 to 90: Apply your foundational knowledge. Tackle key problems and bring well-considered solutions to your team. Beyond day 90: Stay current. Keep an eye on Quickbase updates, since tools and features evolve over time. Understand the “Why” Behind Your Apps Apps often drift from their original purpose. An app built as a CRM might now function as a project management tool, for example. Before making changes, investigate your newly inherited app's history: talk with its original creators or managers if you can, survey users, and align expectations with leadership where needed. Build a Game Plan A practical starting point is learning your account structure: Review existing apps through the admin console. Identify public-facing apps and address any security risks. Interview app users to understand how they’re using apps, pain points, and additional areas of potential growth. Categorize apps by business area (ie: internal, customer-facing, finance) to streamline prioritization. Document roles and permissions, and confirm that managers or builders stay engaged with the apps they oversee. Leverage Quickbase Support Resources Several resources can support new app owners as they get up to speed: Quickbase University: E-learning courses, instructor-led training, and certification programs deepen app-building and administration skills. Certifications also double as a professional credential recognized across industries. Technical support and services teams: These teams help with complex topics like pipelines, integrations, and scaling, and are a good resource when account entitlements or technical configurations are unclear. Community forums and office hours: The Quickbase community offers advice and solutions to common problems, with regular events for connecting with other admins and exploring new ideas. Keep Apps Organized and User-Friendly A few habits go a long way toward making an inherited app easier to manage: Structure data visually Relationship diagrams or tools like Miro or Figma help map out app structures and workflows. Grouping tables logically reduces complexity. Automate routine tasks Quickbase pipelines support automated workflows, and integrations with external systems extend that flexibility further. Customize the user experience Adjust forms to surface important fields, and use visual cues like color-coding to distinguish areas of focus (customer data versus project data, for instance). Plan for Long-Term Success Long-term success is crucial. Ongoing maintenance helps to keep your app useful and relevant: Subscribe to Quickbase release notes to stay informed about new features. Review and optimize apps quarterly. Document processes thoroughly to make succession planning easier when admins leave or hand off responsibilities. Common Challenges and Solutions No matter how prepared you are, challenges will happen. Luckily, many of these are common to Quickbase users and have simple solutions you can enact. Succession planning Admins preparing to step away, whether for retirement or a role change, should document processes, categorize apps by importance, and transition critical accounts to a service account so administrative access doesn't lapse. Gaining access to unassigned apps Admins can add themselves to apps they don't currently manage through the admin console, and technical support can help when that process hits obstacles. Conditional logic on forms Form rules, not pipelines or advanced automation, are the right tool for tailoring form behavior based on user input. The Bottom Line Inheriting a Quickbase app doesn't have to be daunting. Starting with organizational context, prioritizing methodically, and leaning on Quickbase's support resources turns app ownership into a manageable, even confidence-building, process. Every problem starts with one focus area, one lens: start small, prioritize well, and grow into a confident steward of your Quickbase environment. To learn more, watch the full webinar on app inheritance.How to deal with nested lists/arrays in Pipelines?
4 MIN READ What are arrays and nested arrays? If you're building pipelines, then you most likely have encountered query steps and loops. Query steps in Pipelines produce arrays (also known as "lists") that can be looped through (1). This works seamlessly because the array exists at the top level of the step’s output. But what if the array is nested inside a step (2) (not necessarily a query step)... and what if the nested list is compiled of objects (3), not just values? Many Pipeline builders run into this when integrating with APIs, working with multi-select fields, or processing structured data with parent-child relationship. While Pipelines can loop through arrays, it currently does not support looping through nested arrays. So, below I'll explore how to deal with (2) and (3). Looping through a nested list of values (2) A nested array of values may appear as a list but its values are actually stored as: A single value With a delimiter separating each selection (for example ";") value1; value2; value3; value4 Because of this: Pipelines treats the field as one value You cannot loop through the individual selections directly A common example of a nested array of values are Multi-select text fields in Quickbase tables. Solution: Use the “Find all Matches to a Regex” query step To make a multi-select field "loopable", we first need to extract each value into its own array element. The Find all Matches to a Regex query step allows you to: Take a nested list of values Apply a regular expression Output a flat array of matches Once extracted: The output becomes a standard array Pipelines can loop through it natively Each selected value can be processed individually This is a simple and effective workaround for nested lists that contain only values. “Find all Matches to a Regex” example Check out the video. Use case: We have a multi-select text field in QB called "multi-select_text". The record has values "1;3;value1" I want to loop through each value and check if any records in the table have it for example. Here is how my pipeline will look like: Query step to fetch the record (or "Look up a record") Find all Matches to a Regex step where I'm referencing the "multi-select_text" field and "[^;]+" as my Regular Expression Loop through each value from "multi-select_text" Search records step that filters and matches if a record contains any of the values Looping through a nested list of objects (3) Things get more complex when the nested list contains objects, not just values. In this scenario: Each nested object represents a row Each object contains multiple fields You want to insert multiple records into Quickbase { "date": "2025-12-03", "invoice_number": "INV-1001", "items": [ { "description": "Wireless Mouse", "quantity": "2", "unit_price": "$15.99", }, { "description": "Laptop Stand", "quantity": "1", "unit_price": "$34.75", } ] } This type of structure is very common when working with APIs and documents — and it’s also where most Pipelines workarounds fall short. Solution: Use the “Make Request” QB step To solve this, builders need a "Make Request" Quickbase step with custom Jinja code to process the nested objects. The step is doing the following: Extracts the information in the nested array Loops through each item in the array Creates a new record in Quickbase for each item Maps the properties of the object to the fields in Quickbase Check at the end of this article for the full Jinja snippet. “Make Request” example Check out the video. Use case: A user uploads an invoice to Quickbase Top-level invoice data should be stored in a parent table Invoice line items should be stored in a child table related to the parent Here is how my pipeline will look like: Trigger step when a user uploads a new invoice in QB AI Actions step that extracts all the invoice information in a Structured AI Output (JSON Object) Create record with the top-level invoice information Make Request step where I'm recording the line items of the invoice and relate them to the top-level invoice info Final thoughts Nested arrays are a common part of modern data — especially when working with APIs and AI-generated outputs. While Pipelines does not currently support looping through nested arrays: Simple nested lists can be handled by reshaping text into arrays Complex nested objects can be processed using Jinja Once the data is flat, Pipelines behaves exactly as expected Whenever possible, consider recording intermediate data into staging tables to simplify debugging and validation. The key is understanding how to reshape your data before trying to loop through it. Full Jinja from example { "to": "XXXX", {# REPLACE WITH TABLE DBID #} {# LIST FIELD NAMES AND IDS FROM QB TABLE #} "data": [ {%- set F = { "Description": 6, "Qty": 7, "Unit Price": 8, "TotalAmt": 9, "RecordParentId": 12 } -%} {# Normalize source: parse if string #} {%- set _src = b.output_json | default({}) -%} {%- if _src is string -%} {%- set _src = _src | from_json -%} {%- endif -%} {%- set items = _src.items | default([]) -%} {%- set _comma = joiner() -%} {%- for li in items if li is not none %} {%- set desc = li.description | default('') -%} {%- set qty = li.quantity -%} {%- set price = li.unit_price -%} {%- set total = li.total_price -%} {%- if desc != '' or qty is defined or price is defined or total is defined -%} {# MAP EACH FIELD FROM ARRAY TO TABLE (CHECK F VARIABLE) #} {{ _comma() }}{ "{{ F['Description'] }}": { "value": "{{ desc }}" }, "{{ F['Qty'] }}": { "value": {{ (qty | default(0) | string | replace(',', '') | replace('$','')) | float }} }, "{{ F['Unit Price'] }}": { "value": {{ (price | default(0) | string | replace(',', '') | replace('$','')) | float }} }, "{{ F['TotalAmt'] }}": { "value": {{ (total | default(0) | string | replace(',', '') | replace('$','')) | float }} }, {# PARENT RECORD ID - FROM STEP C IN PIPELINE #} "{{ F['RecordParentId'] }}": { "value": {{ (c.id | default(0)) | int }} } } {%- endif -%} {%- endfor -%} ] }Inside Pipelines: July Improvements from the Engineering Team
3 MIN READ Last month we shared how our Pipelines engineering team protects one day each month, the first Friday, to work on the small things: the rough edges, the extra clicks, the moments of friction that individually seem minor but collectively shape how a product feels to use every day. The response to that post genuinely made our day. One reader commented: "I had noticed several of these and really appreciate the little changes, they are impactful. I really like being able to auto-gen description and notes for the steps, that is a huge time saver, and I found it to be more accurate than I would have expected." That is exactly the outcome we are after, so we are keeping the series going. To get to know our team better, I am going to start tagged the engineers who worked on each improvement. Here is what came out of our July session. More canvas real estate with the new floating islands tweaked by rmilushev-qb The top bar of the Pipeline Builder was taking up a lot of real estate, one merged bar stretching across the canvas, claiming space that could be yours. We decided to open it up and give that space back to you. These controls now appear as two compact floating islands, so more of the screen belongs to your pipeline, which is especially valuable on smaller screens. All existing behavior is preserved, including side panel resizing. Pin fields in a pipeline step smoothed out by DzhemSS Previously, steps with long lists of additional fields forced you to scroll and search for the handful of fields you actually use, every time you opened the step. You can now pin fields in a step's additional fields section. Pinned fields are saved with the pipeline, so they are waiting right at the top the next time you open the builder. A new "is today" date filter polished by mboshikyova Filtering records by the current date previously required workarounds, and many of you asked for a simpler option. Date filters will now include an is today operator, available across search, create record, and other steps, with careful handling of timezones so the comparison lands on the right calendar day. A few other things we fixed Not everything needs its own headline, but these are worth knowing about: Show and hide columns in Connections Central. My Pipelines lets you choose which columns appear in the list view, and Connections Central now has the same column picker, with your selection preserved across visits. The Activity panel no longer loses runs of invalid pipelines. Running an invalid pipeline used to flash "Pipeline starting..." and then reset the Activity panel to empty as if the run never happened; the panel now shows these runs with their failure reason. Why we keep doing this The "is today" filter above did not come from a roadmap meeting. It came from you: several customers asked for it through Quickbase Feedback, an engineer picked it up on a Friday, and next month it ships. That loop, from feedback comment to a working feature in weeks, is the whole reason we protect this day. So if you have noticed a rough edge in Pipelines that deserves a spot in a future session, tell us in the comments or through Quickbase Feedback. You have just seen where those suggestions end up. See you next month.Explore What’s Possible with Enterprise Features
4 MIN READ Starting August 17, current Team and Business Plan realm admins can start a 30-day Enterprise trial directly from the account summary page in your Quickbase account. It's an opportunity to experiment with Enterprise features in your own environment, using your own apps and workflows, so you can learn what's possible before deciding whether those capabilities are right for your organization. A low-risk way to explore As your Quickbase environment grows, so do the challenges you're solving. You may be looking to solve something specific, or maybe you are just curious about features you've seen in the product, at Empower and webinars, or within the Community. Now you have a way to explore Enterprise features on your own, with your own data and workflows. Instead of wondering whether a feature could help, you can try it firsthand. At the end of the 30-day trial, your apps and work stay intact. Any assets you created during the trial are preserved, while Enterprise-only capabilities simply become unavailable. For example, pipelines created during the trial will stop running but remain in place, and documents generated with Document Creation will stay in your app, although generating new versions will require Enterprise access. That means you can experiment with confidence, knowing you won't lose the work you've done while exploring new capabilities. Is a trial right for me? If any of these situations sound familiar, this is a great opportunity to explore the features that the Enterprise plan was designed to help: For Current Team Plan Users: You manage projects in Quickbase and wish you had a better way to visualize timelines. Try the Gantt Plugin to view project schedules, track task dependencies, and update timelines through an interactive Gantt chart, all without leaving your Quickbase app. You're manually creating invoices, contracts, quotes, or other documents. Explore Document Creation to automatically generate professional PDF, Word, or HTML documents using live data from your Quickbase apps, helping reduce manual work and keep documents up to date. You want more visibility into what's happening across your Quickbase environment. Check out Admin Console Connected Tables, which bring backend information like app inventories, user activity, permissions, and other administrative data into Quickbase so you can monitor and manage your realm from one place. For Current Business Plan Users: You're responsible for protecting sensitive information Explore AI Data Scanner, which uses AI and machine learning to identify sensitive or private data stored where it shouldn't be, helping you proactively manage compliance and data security risks. Your organization needs more detailed auditing for governance or compliance. Try the Audit Log API to access activity, user access, and data change logs that can be integrated with your existing security and monitoring tools for deeper visibility into your Quickbase environment. Your apps aren't performing the way you'd expect, and you're not sure why. Explore Performance Insights, which analyzes your applications to identify performance bottlenecks and provides prioritized, data-driven recommendations to help improve app speed and scalability. This is your hands-on learning opportunity. The best way to understand whether a feature is useful is to use it with the apps and processes you already have. What's included? During your trial, you'll have access to Enterprise Plan features so you can explore them in your own realm. For Team customers, this includes all features on a Business Plan – even more for you to try! A more complete breakdown of the features on each plan can be found here. A few things to note: Paid add-ons, including the Intelligence Package and Extensions, aren't included in the trial. Additionally, certain account-level security settings, including SSO/SAML, encryption, and branding, are also excluded due to complexity of setup. Who can start a trial? The Enterprise trial is available for realm admins on Team and Business Plans to begin. Once turned on for your realm, builders and users will be able to use features their role has access to. If you're a builder or app admin and there's an Enterprise feature you'd like to explore, reach out to your realm admin about starting a trial. Learn by doing The best way to understand what a feature can do is to use it in the context of your own work. Whether you discover a capability that helps you today or simply learn more about what's available as your organization grows, the Enterprise trial gives you a chance to explore without changing your current plan. If you decide to give it a try, we'd love to hear what you discover. Share your experience in the Community and let other builders know which Enterprise features you found most valuable.August 2026 Release Enablement
1 MIN READ Learn about the most recent updates to Quickbase, right here: Highlights include: Enterprise Feature Trial See a full list of the available features during this trial in our help guide. Release Notes Record Extensions transaction usage To view this data, open the Account Summary page in the Admin Console and go to the Plan usage section. Learn more about Quickbase Extensions transaction counts. Release Notes Record Table Exports are now included in audit logs! Release Notes Record User list dashboard filter You can now filter dashboards by user list field Release Notes Record Anti-bot verification helps keep bots from submitting records Release Notes Record New feedback portal We're replacing our current feedback tool with a new experience Release Notes Record Pipelines: Nested lists Steps like Loop and Import to Quickbase can now point directly to a nested list within a step's output Release Notes Record AI Agent: Enhancements The Quickbase AI agent is gaining several enhancements Release Notes Record View and/or search the complete Release Notes AppWebinar Recap: Automating Work with Quickbase AI Features
5 MIN READ During the session, our product experts explored how customers can use the Quickbase Intelligence Pack to accelerate app building, automate repetitive work, and unlock insights while maintaining the security and governance you expect from Quickbase. We also shared a preview of upcoming capabilities. Read the recap and answers to questions asked live below. Quickbase Intelligence Package What is the Quickbase Intelligence Pack? The Quickbase Intelligence Pack adds AI-powered capabilities to Quickbase that help builders, end users, and administrators work more efficiently. Current capabilities include: AI Agent AI Actions Data Analyzer App Intelligence AI Control Center These features are designed to accelerate application development, automate repetitive work, surface operational insights, and provide enterprise-grade security and governance. Who can use the Intelligence Pack? The Intelligence Pack is available to customers who purchase the Intelligence Pack add-on. Current Quickbase customers can activate a free 60-day trial from the Realm Administration page. What AI capabilities are planned next? The product team previewed several upcoming enhancements: Knowledge Layer – enables the AI Agent to answer questions using company documentation such as SOPs, manuals, SharePoint content, compliance documents, and onboarding materials. Schema Management – allows the AI Agent to update reports, dashboards, forms, relationships, and other application components through conversation. Workflow Agent – generates, validates, simulates, and prepares complete Pipelines for review before activation. The first version of the Knowledge Layer is expected before the end of the year. AI Agent Can the AI Agent build Quickbase applications? Yes. Alex demonstrated an application that was built entirely using the AI Agent, including: Tables Relationships Fields Sample data The AI Agent can significantly accelerate initial app creation. Can the AI Agent analyze reports and explain unusual values or outliers? Yes—with some limitations. The AI Agent cannot currently analyze an existing report directly. However, it can: Query tables and apps the user has permission to access Join data from multiple tables Generate reports through conversation Explain unusual values or outliers in the returned data Can AI Agent manage reports or dashboards? The upcoming schema management capabilities will allow AI Agent to create and manage reports and dashboards through conversations. Note: these can be created in the conversation, but can't yet be saved as Quickbase reports. AI Actions What are AI Actions? AI Actions are Pipeline steps designed to automate repetitive manual work. They use AI to perform tasks such as: Extracting information from documents Classifying incoming requests Generating summaries Drafting resolutions Assigning work Creating structured outputs Can AI input data into Quickbase? Yes. AI-generated structured output can populate Quickbase fields through AI Actions. AI can generate values (such as assignments, summaries, classifications, or recommendations), and those outputs can be written directly into records as part of a Pipeline. How do AI Actions avoid hallucinations? Rather than relying solely on the language model, AI Actions can incorporate existing Quickbase data into prompts. For example, Alex's demo searched previous closed requests and used those historical resolutions to draft a suggested resolution for a new ticket. This grounds the AI's response in organizational knowledge instead of generating an answer from scratch. How are search results used during the Draft Resolution example? The Pipeline: Searches previously closed requests. Filters for similar requests. Passes those historical records into the AI prompt. Uses those prior resolutions to draft a suggested resolution. Writes the draft back into the new request record. This allows the AI to leverage previous organizational knowledge rather than inventing a solution. Can you share more about the Query step used in the demo? The query searched the Requests table and filtered records based on: Status = Closed Matching category Matching related products Only those filtered historical records were passed into the AI Action. How does AI classify request priority if users always write "URGENT" or "ASAP"? We recommend including business rules directly within the AI prompt. For example, prompts can instruct the AI to: Evaluate the severity of the request Avoid relying solely on words like "urgent" or "ASAP" Score urgency based on the overall context This allows organizations to prevent users from artificially inflating request priority. Are AI Actions limited by document size? The current supported file size limit is 3 MB. There are plans to increase this limit to 10 MB. Is example YAML available for AI Pipelines? Yes. The Quickbase Help documentation includes an example YAML definition for AI Actions pipelines. Security & Governance Does the Intelligence Package respect user permissions? Yes, it honors existing Quickbase security, roles, and permissions. Users can only access data they already have permission to view, and AI responses are grounded only in that accessible data. Are there safeguards to prevent accidental deletion of records? Yes. If a user asks the AI Agent to delete records: The AI first verifies that the user has permission. The AI displays what will be deleted. The user must explicitly confirm before deletion occurs. Can AI be enabled only for certain users or features? Yes. The AI Control Center allows Realm Administrators to: Enable or disable individual AI features Grant access by user or group Roll out AI capabilities gradually Maintain governance and audit controls Performance Will AI Agents slow down Quickbase? No significant performance impact should be seen. AI-generated queries are different from traditional in-memory formula queries and are not expected to introduce meaningful system slowdowns. Integrations Will Quickbase connect directly with Claude or ChatGPT? Currently, A ChatGPT Pipelines channel is available. A Claude integration is under consideration, but a decision will not be finalized for a few months. Licensing Can I use the Builder Program to build AI proofs of concept? No, the Builder Program does not currently include Intelligence Pack capabilities. Forward Deployed Engineers (FDE) What is a Forward Deployed Engineer? Forward Deployed Engineers (FDEs) work directly with customers to identify AI opportunities and implement production-ready AI workflows. Their work typically includes: Evaluating AI readiness Reviewing application schema Designing AI use cases Building AI pipelines Coaching customers on AI prompt design and implementation Customers interested in working with an FDE should contact their Account Executive or Customer Success team. Ready to dive deeper into the AI Discussion? Join our App Builder Qrew Meetup on Tuesday, August 18 for a virtual discussion on how others are using the Quickbase Intelligence Package. You’ll hear real-world examples and use cases from customers marking the most of AI Agent and AI Actions. Reserve Your Spot > Or, try the features for yourself. Start a free Intelligence Pack Trial >Inside Pipelines: June Improvements from the Engineering Team
2 MIN READ Most engineering teams spend a lot of time thinking about what's next. We do too. But over the past year we've also started protecting one day each month to improve what's already there. Around the team, we call it "Delightful Pipelines Day." It's a chance to focus on the smaller improvements that make building Pipelines just a little easier. The search that doesn't stick. The extra click. The workflow that slows you down just enough to notice. Most of the changes we make are small enough that you probably won't notice them in the release notes. But over time, they add up. We hope they make Pipelines a little easier to use every day. We'll keep sharing these updates each month so you can see what we've been working on behind the scenes. Naming Help Naming things is hard. We added a Suggest Name option that looks at your pipeline and proposes a name based on what it's doing. Use it if it’s helpful, or Dismiss if you already have a better name. Keeping your place when you're searching You search the dashboard and several similar pipelines appear. You open the most promising one. Wrong pipeline. You go back to try another. Previously, your search was gone. That meant entering it again and rebuilding your shortlist. Now, your search and results stay with you when you return, so you can move on to the next candidate without starting over. This works in both My Pipelines and Realm Admin. Filters should remember what you already told them We also noticed something while configuring filters. If you switched from one field to another with the same data type, your filter selections disappeared and had to be re-enetered. Now your filter selections stay with you when you switch between fields of the same data type. They'll only reset if you switch to a different type. It's a small change, but if you're building more complex pipelines, it removes one more repetitive step. A few other things we fixed This month we also: Improved the loading state while a pipeline opens so you no longer briefly see internal IDs. Added descriptions to Pipeline Tags, making it easier to understand what a tag is meant to represent. Sorted Pipeline Tags alphabetically in the Tags view. Improved canvas panning when working in larger pipelines. Updated documentation links for AI Actions. Made filter names more consistent with Quickbase reports. That’s June. That's what we spent this month's “Delightful Pipelines Day” working on. Some of these ideas came from customer feedback. Others came from things we noticed ourselves while building and testing Pipelines. We'll do it again next month. If there's something in Pipelines that makes you think, "There has to be a better way," let us know in the product Feedback, or add a comment below. Those are often the best kinds of improvements to work on. See you next month.4 Minutes with Qrew Legend Tammie King
1 MIN READ In this quick 4-minute video, Tammie shares what she loves about being part of a community of Quickbase users who learn from and support each other. Take a few minutes to watch Tammie’s story and get inspired by what’s possible when Quickbase builders connect. Watch the video: Want to meet more builders like Tammie? Connect with the Qrew on the community site and connect with your local Quickbase community. Want to connect with local Quickbase users in your area? We can help make introductions Join the online Qrew here Discover Qrew Groups Explore upcoming Qrew events Want to get a calendar reminder each month to upcoming virtual Qrew Meetups? Click here to sign upThank You, Qrew
3 MIN READ To The Qrew, My time at Quickbase is coming to an end. Wednesday, July 29 th will be my last day with the company. After 8 wonderful years working with Quickbase customers and partners, I’m logging off and starting a new challenge elsewhere. I’ll never forget Empower 2019 in Miami. During the keynote, Product Managers were on stage being treated like celebrities. Customers sat in the audience and gave raucous ovations to announcements to things like Dashboards and Formulas and Automations. Customers discussed tips and tricks while standing in line for breakfast, laptops were open everywhere and the only topic being discussed was Quickbase. The only complaint I heard all week was from customers who couldn’t fit into the most popular sessions. Fear not, those sessions would be offered again later in the week. It was Disneyland for no-code problem solvers. I couldn’t believe the level of enthusiasm radiating through the room. Prior to Quickbase, I worked at companies where it was rare to see any form of passion other than sheer anger coming from customers towards the vendor. Quickbase was different, the customers clearly loved the product. The main takeaway from Empower Miami was about this community. The talent, the passion, the creativity, there were so many individuals who had their careers catapulted into something new and awesome because of how well they gravitated towards using software Legos to build custom databases. It was infectious. In 2023, the opportunity to make a change in my career arrived, and I jumped on it. I became a Community Manager. But first we needed a name. Enter “The Qrew”. A collective of problem-solvers who just get it. Next we needed a way to celebrate the individuals who went above and beyond for this Community. We created The Qrew Legend Award, and I was so proud to see Mark Shnier, Sharon Faust, and Tammie King become the first three recipients. Legends indeed! Qrew Groups expanded from virtual-only to being held in-person. Online we met over Pipelines and Governance and whatever else you were willing to share. I’ll miss the meetups. At some point a Discord server was created and I started participating. I was there mostly to listen, but soon after joining it became one of my favorite ways to connect with Qrew members. And finally, yes. Empower came back. The conversations in the breakfast buffet were about Pipelines and Jinja now; while the energy of this community hasn’t changed, the product certainly has. It’s still incredible to me what you all can do with a Quickbase app. The Qrew has an amazing team here at HQ keeping this train moving. Esther LaVielle and Maria Peralta are Qrew diehards, committed to giving you the best community experience possible. Caroline Englert will oversee The Qrew as well as our Advocacy efforts. As someone who has worked closely with Caroline for so long, there’s no one I would rather have run this incredible community than her. Be good to her or you’ll hear from me! I want to thank you for this incredible experience. A great product is useless without great users. I loved seeing the infinite ways Qrew members were solving problems at their respective companies. Quickbase the product + The Qrew is a power duo that will thrive in the years ahead. You taught me about the value a strong community can bring to a business, and more importantly, to each other. I won’t forget it. Forever grateful, Ben
