Inventory Management & Purchase Orders – Knack 101

Alright.

I’d like to promptly get started right at the top of the hour just because there’s so much to cover. And I also want to try to leave some time at the end for Q&A. So I will go ahead and get started. Just as a heads-up, if you have to drop early, this is being recorded, and we will be sharing the recording link after the webinar today.

So, again, hello, everyone. Thank you for joining. My name is Roe, and I am part of our onboarding team here at Knack. You will also see my colleague, Max, on the call. He’s part of the onboarding team as well. You’ll see a note that he just dropped in the chat. But thanks again for joining us today.

As we get started, we’ll talk about some initial things so you’re getting familiar with the platform and what we’re going to be discussing today.

Let’s see—why am I drawing a blank today on what we’re talking about? What we’re going to do? What to expect in this webinar today? First things first—you are in our conference room here.

There are a couple of areas where you can reach out to us and ask questions during the webinar. You’ll notice there is a chat area as well as a Q&A section. Feel free to share your questions in the chat or drop them in the Q&A area. Max will be keeping an eye out and responding there.

We’ll also highlight some of those questions towards the end in the Q&A section and, hopefully, there’ll be some time to demo or show you around the product. If you’ve got specific questions or workflows you’re building, feel free to share what you’re looking to create with Knack. Please let us know—we’ll take a look and discuss those toward the end of the webinar.

What to Expect and How to Participate

We’re going to talk a little bit about what you can build with Knack. We’ll also walk through a demo of a couple of different template apps and do some live building. If you haven’t started yet—whether you’re working from a template or building from scratch—we’ll cover what to expect and how to begin.

Again, feel free to share questions in the Q&A or chat at any time.

Building with Knack

Alright. So if you are new to Knack, you may be wondering: what can I build with Knack?

I’m going to jump off screen here so we can focus on what we’re looking at.

So, what can I build with Knack? If you’re coming in to build out custom business applications, data management systems, educational resources, custom forms, or data sharing platforms—Knack is a no-code tool that allows you to build applications to help you manage and share your data.

Diving into each one of those bullet points a bit more in-depth: Knack can handle workflows from project management and CRMs to learning management systems, event registration, and client dashboards.

There’s a lot of functionality you can get just with the features Knack provides. If you’ve created a trial, you probably noticed that once you get into the platform, it’s a blank slate. You start adding your tables, fields, and then work your way over to pages to build out workflows and define the actions your users can take.

Knack also supports e-commerce solutions, reporting, and analytics. We’ll touch a little on dashboards today.

If your team is working in the field and needs to access and update data while on the go, our apps are web-based and mobile-responsive. That means they’ll adjust to screen sizes on phones or tablets.

And if you want to give external users access—like clients or research participants—you can do that too. This could look like a market research database or a customer portal where users can log in and only view their own information.

Use Case Introduction

Before we dive into a live demo of a couple of different use cases, I want to give you a quick heads-up about how to get support from our team.

Again, Max and I are part of the onboarding team here at Knack. We’re available Monday through Friday, 8 AM to 8 PM Eastern Standard Time. You can reach us at onboarding@knack.com. We’re here to help you get onboarded, find value in the product, and figure out how to get started based on your needs.

You can also learn more about working with our onboarding, support, and success teams in our knowledge base. Just search for “working with support” in the knowledge base, and it’ll be one of the first things to pop up. That article includes information about support hours, chat availability, response times, and more.

I’ll also show you where to find that information in the builder during the live demo.

Navigating the Inventory Management App

Alright, let’s get started.

Today, we’re going to look at two different use cases: inventory management and purchase orders.

Both apps use a feature called formula fields. If you’re trying to run calculations across your app—like tracking how many purchases are affecting your inventory—we’ll show you how that works. Same thing for calculating totals across line items in a purchase order.

We’ll demo those apps first, and then we’ll actually build out the inventory management tool from scratch.

I see a quick question here: is every Wednesday focused on inventory management and purchase orders? No—these rotate weekly. Next week might be a different use case. We’re also starting to make these recordings available on our webinar page, so you’ll be able to go back and review earlier sessions.

Alright—Max dropped some helpful info in the chat too.

Let’s take a look at the inventory management workflow.

Exploring the Inventory Management App

I’m going to jump here back to our homepage. So if you’re not familiar with Knack or you’ve yet to see what a live app looks like, this is what a live app looks like. Knack URLs are what we call your Knack personalized URL. It consists of your account name—usually your business name—followed by .knack.com. The “inventory manager template” is the actual name of your app, and anything after the hash is the specific page you’re on. There may be some additional components in the URL, but that’s the general format.

When we take a look at the other template app, you’ll notice its link is slightly different as well. But that is your Knack personalized URL, and you can share that out with your users.

We’ve got ways to put your app behind a login. Right now, this is a public page—so if anyone had access to this link, they would be able to see the information here. We’ll talk about how to secure your app shortly when we start the live build.

Looking at the inventory management app, you’ll see at the top we have navigation items that let us move through the app. We can look at current inventory, incoming purchases, outgoing orders, and a reports page. I’m going to jump back here, but that’s our main menu navigation you can set up in your application.

We also have buttons here—we call these “menu views.” They allow you to create a button that links to a form, which lets you add records to your product database. So if we wanted to add a new product, we could. One question we often get is, “Can I use forms to add data to my database?” And yes, you absolutely can.

Once you add a product, it will appear in the grid view we’ve set up. Knack has a variety of views that allow you to add to, edit, and display your database. You’re only seeing a few here—there are many more available.

These views display data in a variety of ways. Here, we’re seeing a grid view. We’ve got multiple field types: short text, paragraph fields, number fields, multiple choice—you name it.

Our tables can be filtered to show things like “what needs reordering,” and we can use color highlighting to help our users quickly identify important information. For example, if inventory is running low, we can draw attention to it visually.

If we dive into a specific product, we can see relational data for that product. For example, here we’re looking at the Google Chromebook. We see all the details for this one record, as well as its related incoming purchases and outgoing orders.

You can also edit this product. We offer multiple types of forms—both add and edit forms—to help you manage data.

You can also use add forms to capture new purchases or orders. This lets you keep everything connected in a relational structure, giving you a complete view of each product and its activity.

You’ll notice we can navigate through the app using links, buttons, and menus. Maybe we want to view purchases—let’s say we know our Chromebook inventory is low, and we’re planning to order more. We can add 50 more, select our product, choose today’s date, and submit the form.

Back on the incoming purchases page, we’ll see that data reflected. We could even go back to the current inventory page and see that our Chromebook is no longer flagged as low inventory. It’s now above the reorder threshold.

Knack also lets you apply conditional and validation rules. We’ll touch on those shortly.

In addition to purchases and orders, we also have a reports page. With Knack, you can create dashboards that let you see your data at a high level. Reports can be built with grids, search views, pie charts, column charts, pivot tables, line charts—lots of options to help you analyze and share data.

Exploring Purchase Orders Template

We’re now in our Purchase Orders template app. If you want to secure your application and place it behind a login, you can absolutely do that with Knack. In this app, users can log in to manage purchase orders, including tracking line items and vendor relationships.

I’m going to log in here as an admin. Once I’m logged in, I can view all my vendors and purchase orders. Again, we’re seeing different views—table views, form views, and menu views. You can export data, filter it using controls, and adjust what’s visible. All of this happens inside a grid view that’s easy to customize.

There’s also a button that links to an “Add Vendor” form. If I dive into a specific vendor record, I can view more detailed information, including all of the products associated with that vendor. I can also jump directly to my Products table to view all products in the system and dive into individual records to see purchase history, quantity, and amount.

Within these grids, we can enable summaries—so for instance, you can automatically total up all the amounts for purchases related to a particular product. It gives you a quick overview without needing to run a separate report.

Jumping over to the Orders tab, I can see all the orders in the system. Let’s click into one to look at the line items.

Each order includes line items, and the system calculates totals based on the quantity and product price. We’re seeing those totals both within the child table and in the parent order view. If I want to add a new line item, I can do that right here.

Let’s pick another product and say we’re ordering 10 of them. You’ll see the new line item appear, and the total cost is calculated automatically.

Knack offers tons of field types that make this flexibility possible. You can customize forms, connect tables, and use summary features and formulas to automate much of the data tracking.

We also have a Reports page here. Like the inventory template, it includes column charts, line charts, and pivot tables. These visualizations help you interpret and share the data in your app more effectively.

This template—along with the Inventory Manager template—is available in the Knack Template Library. You can install and start using either one for free.

Getting Started with the Builder

Let’s now look at the backend of the Inventory Manager template from the Builder view. If you’ve installed a template, you’ll land on your app’s dashboard. This is your builder environment.

If you’re wondering where you are or how to get started, you’re inside the Builder for your individual Knack app. On the left-hand side, you’ll see Tables, User Roles, and Ecommerce options.

Tables are basically like spreadsheets or forms—they hold your data and define your structure. You can add new tables in several ways: start from scratch, import data, use premade tables, or even import from a Google Sheet.

Once you’ve added a table—like the Products table—you’ll see your list of fields. Each field has its own settings. You can add new fields by clicking the “Add Field” button, and then you’ll see a list of field types. Want to add an image field? Just click on it, and it will be added to your table.

From there, you can rename the field, make it required, and configure formatting and validation rules. There’s also a three-dot menu (ellipses) with quick-access settings for things like conditional rules, default values, and more.

I encourage you to explore—click around, see what options are available. It’s the best way to get familiar with everything Knack can do.

User Roles and Access Control

So that is your Tables section. Now let’s look at User Roles.

If you remember, in our live app, it was a public app—anyone with the link could view it. But if you want to put your app behind a login, all you need to do is enable users. This allows you to create different roles so that users can log in and access only the parts of the app relevant to them.

Think about it like this: you might want your admins to have full access, while your customers only see their own orders. Many new users mistakenly create a table called “Clients” or “Customers” up top and then start tying those records to data—but that doesn’t work well when it comes to login and access control.

Instead, you should enable User Roles in this section. You might add two groups: “Admin” and “Client Users.” Then Knack creates a separate user table for each group. These tables come with built-in fields for name, email, password, and status.

Once you’ve done this, you can tie records to users, and later in your Pages section, you can control what each user group is allowed to see and do. For example, you can set it so only clients see their own orders and admins see everything.

Again, if you need someone to log in—even if not today, but maybe later—set them up as a user role from the start. It’ll save you restructuring work later.

User role tables work just like regular tables—you can add custom fields for address, phone number, or anything else you want to track.

Creating Login Pages for Users

Let’s head over to the Pages section. This is where all the magic happens.

This is where you define workflows—what your users will see and do. You might think, “I’ve added tables and fields, so when I go to view the app, I’ll see something.” But no—you won’t see anything in the live app until you build out pages.

Pages are where you add Views—like forms, grids, menus—and control how users interact with your data.

Let’s say you want to let customers log in and submit an order. First, you’ll create a login page. When creating this page, Knack will ask who should have access. You can choose “All Users” or limit it to a specific user role.

Let’s pick “Client Users” and call this page “Customer Dashboard.”

Once you add the page, it will show a login form by default. When users log in, they’ll be taken to the next page in your sitemap. If you go to the live app now, you’ll be prompted to log in before you can see anything on that page.

You’ll notice the lock icon next to this page in the builder—it indicates that access is restricted. That’s how you know this is a secure, login-required page.

Working with Records and Tasks

Next, let’s talk about Records.

Clicking on the Records tab allows you to view the raw data in your system. If you just created your tables, you probably won’t see much yet. But here’s where you can manually add test data, import records, export your database, or batch update and delete records.

Keep in mind: the live app is where your end users interact with the system. The builder is where you or your developers manage the backend—like importing spreadsheets or updating multiple records at once.

Now let’s touch on Tasks.

Tasks are available on the Pro plan and above. They let you automate workflows. For example, if you want to mark any record as “expired” when its expiration date is today or earlier, you can set up a daily task to do that.

Tasks can also send automated emails—like birthday greetings or reminders. You define the schedule (daily, weekly, etc.), the condition (e.g., today’s date = birthday), and the action (send an email or update a record).

They’re not available during the free trial, but you can read more about them in the Knowledge Base.

Navigating the Knowledge Base

Earlier, I mentioned our Knowledge Base. Let me show you how to access it inside the builder.

Click the question mark icon at the top right of your screen—this opens our Help Drawer. Here, you’ll find tons of helpful resources.

You’ll see Getting Started links that take you straight to foundational guides. There’s a link to our demo apps, which are our template apps. If you’re curious about what’s available or just want to explore how certain features are built, definitely check those out.

You’ll also see deeper documentation in categories like “Extend Your App.” This is for developers or users who want to go further—embedding their Knack app into their own site, adding custom CSS or JavaScript, or using our API.

And if you want help from a Knack expert, we have a partner network. These are verified partners who’ve demonstrated proficiency with our platform. You can hire them directly to help with consultation, custom builds, or anything else you need.

You’ll also find links to our support center and community, where Knack users and experts are active. It’s a great place to search for similar use cases, ask questions, and learn from others.

So that’s all under the Help icon in the top right corner of the builder.

Building Workflows and Pages

Now let’s take a deeper look at Pages.

This is where your workflows take shape—how your users will interact with your app. You’ll see that when you first create a Knack app, a public homepage is automatically added. That’s what users will land on unless you build more pages or restrict access.

To show data or allow interaction, you’ll need to add Views to a page. These are visual components like grids, forms, menus, calendars, and reports.

Once you click “Add View,” you’ll choose what type of view you want. For example, you might add a Grid to show records, a Form to add or edit records, or a Menu to display navigation buttons.

When you add a view, a panel opens on the left-hand side where you can configure its settings. You’ll see “Source,” which tells you what data the view is connected to. You can also apply filters and sorting. For example, you could filter the view to only show orders from the past 30 days.

Every view has its own settings—grids can have search bars, export options, column summaries, and conditional formatting. You can choose which columns to display and rearrange them. You can even click into a specific column to edit its settings.

If you’ve connected your tables using connection fields, you can also pull in fields from related tables. For example, in an Orders view, you could show the related Customer Name or Product Cost.

Finally, Action Links let users edit, delete, or view more details. You can toggle those on or off depending on what you want your users to be able to do.

So, again—each view is highly customizable. I encourage you to spend time exploring all the options.

Creating an Inventory Management App

Now let’s build something from scratch so you can see what it looks like to set up an app yourself.

I’m going to use a blank app that I created earlier. When you start from scratch, Knack gives you one table by default—just a starting point.

If I go to “Go to Live App,” it’s completely blank. Even the title says “Untitled App.” And that’s expected because we haven’t added any Pages or Views yet.

Let’s fix that.

First, we’ll build a simple inventory app. We want to track products and outgoing orders, and we’ll also add a customer element so we can associate each order with a customer.

We’ll start by renaming the default table to “Products.” You can do that by clicking into Settings, changing the table name, and choosing a Display Field. This field will show up in dropdowns and connections—usually the product name or ID.

Now let’s add fields to this table. We’ll keep it simple.

We’ll add a Number field for “Starting Inventory.”

Then a Currency field for “Cost.” As a quick note, when you’re just starting out, you’ll see four basic number fields. But once you create relationships between tables, more formula options will become available—we’ll come back to that.

Let’s now add an Orders table to track purchases. Click the plus icon to add a new table, and start from scratch. Rename it to “Orders.”

Initially, you might think to capture customer name using a Short Text field. That’s okay, but it’s not ideal if you want those customers to log in later. We’ll cover a better approach soon using User Roles.

For now, let’s focus on connecting this order to a product. Some users will try to use a Multiple Choice field to list products, but that’s not scalable.

Instead, use a Connection field. This creates a live relationship between the Orders table and the Products table. Choose “Products,” and set the relationship as: Each Order connects with one Product, and each Product connects with many Orders. That’s a one-to-many connection and works for most use cases.

Now, when we add a new order, we can choose from the actual products in our Products table. If you change the “Display Field” on the Products table, that dropdown will show the updated field. So, for example, you could show the product name, the cost, or the inventory count—whatever is most helpful.

Establishing an Orders Table

Now that we’ve got our Products table, let’s finish setting up our Orders table properly.

Earlier, I mentioned we don’t want to just capture a customer name as a text field if we plan to let customers log in. Instead of managing that data manually, we should use User Roles to handle customer records and login access. We’ll set that up shortly.

For now, we’ll continue working on the Orders table. We already added a connection to the Products table. Let’s now add some fields to capture order details.

First, we’ll add a Number field for “Quantity.” This tells us how many units the customer ordered. We can even set a default value—like 1—to make data entry easier.

Next, we want to capture the Cost of the product being ordered. One approach is to create a Currency field and allow users to enter the cost manually. But a better approach is to automatically pull in the cost from the Products table. We’ll do that with record rules later in the Pages section.

For now, we’ll still add a manual Currency field for “Cost” to use in our equations.

Finally, let’s create an Equation field to calculate the “Total” order value. We’ll multiply Quantity × Cost. That equation will automatically calculate the total price of the order.

Keep in mind the order of operations in Knack: for equations to work correctly, the fields they reference must appear above them in the table.

Now the Orders table includes: the connected Product, Quantity, Cost, and Total.

Connecting Tables for Data Relationships

Let’s now connect the Orders table to Customers the right way—by using User Roles.

Go to the User Roles section and enable users. Then, create two groups: one for “Admins” (internal users) and another for “Customers” (people placing orders). Knack automatically creates a table for each role.

Each user role includes default fields: Name, Email, Password, Status, and Role. You can also add custom fields, like Phone Number or Address, depending on your needs.

Now that we have a Customer user table, we can go back to our Orders table and add another Connection field, this time connecting it to the Customers table.

Just like we did earlier, we’ll say each Order connects with one Customer, and each Customer can have many Orders. That’s another one-to-many relationship.

Now, each order is associated with both a Product and a Customer. The structure is clean, scalable, and ready to support login-based access.

Adding Products to the Inventory

Now that our tables and connections are set up, we’ll add some sample data to test things out.

Start with the Products table. Add a couple of items manually—for example:

• iPhone, Starting Inventory: 1, Cost: $1,000
• Samsung, Starting Inventory: 2, Cost: $250

This gives us test data we can use to confirm our calculations and relationships.

Next, go to the Customers table and add a record—let’s say “Max.” We’ll use this login later when testing the customer portal.

Then go to the Admins table and add your own record so you can log in as an admin and test both user experiences.

By manually entering this data in the Records tab, you’ll be able to test everything without needing to import spreadsheets. For evaluation and prototyping, that’s the easiest way to get started.

One important note: when you’re setting up login access, the credentials you’ll use to log into the Live App are the ones created here in the User Role tables, not your main Knack account login.

Also, remember: Knack doesn’t charge by user seat—each user is just a record in your database. If you need 100 customers to log in, that’s 100 records in your Customer table.

Implementing User Roles for Customer Management

Now that we’ve added sample data, let’s refine how we manage customer access.

We already created a “Customers” user role and added a connection from the Orders table to this role. This is the right approach because it allows us to associate each order with a logged-in user.

With this setup, we no longer need a separate short text field for “Customer Name” in the Orders table. That would be redundant and not secure. So let’s delete that unnecessary field.

From here, we can build specific experiences for different user roles. For example, admins can see everything, while customers only see their own orders. This structure gives us control over data visibility and permissions in the live app.

Once again, a reminder: enabling user roles early is key to building secure and scalable apps. If you think a group of users might need to log in eventually, go ahead and set them up as a user role from the start.

Calculating Costs and Totals

Now let’s improve our order logic with some automatic calculations.

We already added Quantity and Cost fields to our Orders table. Next, we’ll create an Equation field to calculate the “Total” value for each order.

To do this, we simply multiply the Quantity by the Cost. Knack provides a list of available fields, and once you select those two, it handles the math. You can also configure the display format—for example, showing the result as U.S. currency.

There’s another approach worth knowing: using a record rule to pull in the product cost at the time an order is created. This is helpful when you want to “freeze” the product price, even if it changes later.

We’ll set that up in the Pages section using form settings and record rules. But for now, the key takeaway is: Knack gives you flexibility. You can calculate values live using equations, or you can store them at the time of entry using rules.

Summarizing Inventory and Orders

Let’s now calculate how many units of a product have been ordered—and how many are still available.

To do this, we’ll go back to the Products table and add a Sum field. This type of field lets us total the Quantity values from all connected orders.

Since each Product can have many Orders, this sum will tell us how many units have been sold or reserved. We’ll name the field “Total Ordered.”

Next, we’ll create an Equation field called “Inventory On Hand.” This will subtract the Total Ordered from the Starting Inventory. Again, you can format this result to match your needs—plain number, currency, etc.

Want to go a step further? Add a Number field for “Minimum Required.” This is the threshold below which inventory is considered low.

Then add a Yes/No field called “Below Requirement.” Using a conditional rule, you can configure it to say: if Inventory On Hand is less than Minimum Required, set “Below Requirement” to Yes.

This setup lets you flag low-stock items automatically. You can use this field later for filtering, highlighting rows, or triggering alerts.

Creating an Inventory Management App Dashboard

With our tables, relationships, and test data set up, we can now begin building out the user experience using Pages.

By default, Knack creates a Homepage, which is a public page. You’ll see it in the Pages tab with a simple document icon. However, we want to restrict access and build specific dashboards for different users.

To do this, click the pink plus button to add a new page. Select Login Page, and choose the user role it’s for—let’s say Customers. Then name the page something like “Customer Dashboard.”

Once added, this page will include a login form. After a user logs in, they’ll be taken to the next part of the sitemap, which you can now build out with views.

If you go to your live app now, you’ll see the login form. After logging in, you’ll land on a blank dashboard page, ready for custom views. You’ll also notice tabs appear for every page the user has access to. Pages without permission won’t appear in the navigation.

Now that we’ve created the Customer Dashboard, we’ll begin adding interactive features like order forms and order history views.

Creating Order Forms for Customers

Let’s now add a form to the Customer Dashboard that lets users create new orders.

Click Add View, then choose Form. Connect it to the Orders table. When configuring the form, make sure the order is automatically connected to the logged-in customer—you’ll see that option in the form source settings.

You don’t need to show the customer field on the form because the system already knows who is logged in. So remove it from the visible fields.

Instead, display just the Product dropdown and the Quantity field. That’s all the customer needs to fill out.

To automatically pull in the product cost, use a record rule. Go into the form’s settings, click on Rules, and create a record rule to copy the product’s cost into the “Cost” field of the order when the form is submitted.

This way, the order captures the cost at the time of purchase—even if the product’s price changes later.

You can also configure redirect settings to return the user to a summary page after submission, or send an email to notify your team of the new order.

When you’re done, hit save. The form is now live and ready for use.

Enhancing Customer Experience with Order Views

Now let’s show customers their past orders.

Go back to the Customer Dashboard and Add a Grid view below the form. This grid should show records from the Orders table and be filtered to the logged-in customer.

This ensures that each customer only sees their own orders. You don’t need to add any filtering rules manually—Knack will handle it as long as the connection between Orders and Customers exists and the page is set up for the Customer user role.

In the grid, you can choose which columns to show—such as Product, Quantity, Cost, Total, and Date. You can also turn on features like column summaries, search bars, and pagination to enhance the user experience.

If you don’t want customers to edit or delete their orders, disable those action links in the grid settings. You can also add a “View Details” link to show more information in a read-only format.

When you preview the page, you’ll see the full customer experience: a button to place a new order, and a grid showing their order history.

And just like that, you’ve created a functioning customer portal.

Recovering from Mistakes in the Builder

Let’s say you accidentally added a view or form to the wrong page. No worries—Knack makes it easy to fix.

In our example, we mistakenly added an order form to the wrong part of the app. To move it, click the three-dot menu (ellipsis) on the view and choose Copy or Move. You’ll then select the correct destination page—in this case, the Customer Dashboard.

Once the copy is complete, you can safely delete the version that’s in the wrong place. Just double-check that everything works as expected on the new page before removing the original.

This ability to move or copy views is super helpful, especially as your app grows more complex. It saves time and prevents unnecessary rework.

So even if you make a mistake while building, Knack provides you with flexible options to recover and continue.

Reviewing the Full Customer Experience

Let’s take one final look at what the customer will experience.

We go to the Live App, refresh the page, and log in using our test Customer record. After logging in, the user sees:

• A button (menu view) that links to the order form
• A form to place a new order
• A grid view showing their order history

We test by placing an order—selecting a product and entering a quantity. The form submission takes us back to the dashboard, and the new order immediately appears in the grid.

If we view the records in the database, we’ll see that the cost was automatically copied in, thanks to the record rule we configured. And the Total calculation appears correctly based on quantity and cost.

Everything works seamlessly for the customer, and we’ve created a secure, intuitive interface tailored to their needs.

This approach can be expanded with additional features, like order filtering, confirmation emails, or charts for tracking activity.

Wrapping Up and Final Tips

That wraps up the build for today’s webinar.

We covered how to:

• Build and relate tables like Products, Orders, and Customers
• Set up user roles and manage login access
• Use connection fields to enable dynamic dropdowns
• Create forms and grids tied to the logged-in user
• Use equations, summaries, and conditional rules for automation
• Configure record rules to copy values at the time of entry

Thanks for sticking with us through a ton of information! I know this was a longer session, but I hope it gave you a solid foundation.

Remember, if you have questions, our onboarding team is here to help. You can email us at onboarding@knack.com. You can also check out the Help icon in the builder to access knowledge base articles, community forums, and our partner network.

In the coming weeks, we’ll host more webinars—many of them will be Q&A-focused. So please send in your questions ahead of time and we’ll address them live.

Thanks again for joining. We’ll send out a link to the webinar recording soon. Have a great rest of your day!