Volunteer Management – Knack 101

Alright.

I like to get started promptly at the top of the hour. There’s always a ton of information that we have to cover within this webinar, and so it always feels like it’s not enough time. Things tend to go by pretty quickly.

Just as a heads up, this webinar is being recorded and will be available to you upon the close of this webinar. So in about a day or two, we’ll send that out. But let’s go ahead and get started.

Again, thank you for joining us today. My name is Roe, and I’m a part of our onboarding team here. And I’ve got my colleague, Knack Max as well who’s joining us today. He is also a part of the team, and we are here to help and assist and help you get onboarded to the product. So thank you again for joining us today.

Also, I just wanna let you guys know, I’m having some Internet issues.

If not, Knack is here to jump in, and hopefully we’ll be able to assist as we go along.

So, just let us know. Quick thing to note here, you are able to chat send us through a chat as well as, any information in the Q&A if you haven’t already done that. And I’m gonna jump off camera here to see if this will help with some of the lag because Max is letting me know that I’m having some lag issues here.

Alright. So we’ve got that turned off. But just as a general heads up, if you’re having a hard time hearing, please let us know. He’ll be keeping an eye out on the webinar chat area, and we will then pause things, and then we’ll let him pick things up while we figure that out.

So I apologize. Hopefully, we don’t have any issues. Hopefully, turning my camera off was super helpful. So again, welcome to everyone just joining.

I see some more people coming into the room now.

What to Expect Today

So, what to expect today? We’re going to discuss all things Knack, and we’re also going to talk about getting support. Then we’re going to demo one of our template apps, and hopefully have some time at the end for live Q&A.

Again, if you have questions, we are monitoring the chat and the Q&A session, so feel free to leave your questions there. Max will be following up, and towards the end, we will definitely demo those questions—if possible—live during the Q&A portion.

Also, feel free to share with us your use case. If you’ve got a use case that you’re looking to validate or build out within the product, even if it’s not a direct question, feel free to share that as well. We can take a look at it at the end of the webinar today.

What You Can Build with Knack

So, if you are new and just now coming to Knack, let’s just get into some of the things that you could potentially build with Knack if you’re getting familiar with our platform.

You see our lovely list here. I’m not gonna read every single one of those, but there’s a ton that you can do with Knack—from custom business, responsive-type applications to custom forms and surveys, and sharing your data.

Internal Tools and Customer Portals

As we dive into each one of those items, what does that look like when we talk about custom business applications or internal tools and customer portals?

In general, with Knack, it’s a solution that allows you to customize and build out your business applications, your workflows, or ways to share your data with either your customers or your internal teams. It helps you better manage your data so you can get more insight from it.

So, again, what can I build with Knack? You’ve got customer portals. You’ve got data management systems—things like inventory management, project management, event registration, attendee management—a lot that you can do.

I saw a couple of use cases around vendor management, volunteer management, and donor management. We’ve got more information on that here in a little bit.

Ecommerce, Reporting, and Marketplaces

Diving into some other things you can do with Knack—from ecommerce solutions like managing purchase orders or a product catalog, to reporting options like sales dashboards, tracking employee performance, or gathering customer feedback.

And if you’re doing things like data sharing, and you want to build a market research-type database or a data marketplace where you’re giving access to that data, it’s definitely possible with our tool.

Core Features You’ll Be Using

Alright. So again, you’re building with Knack. What types of things are you doing?

You’re doing data collection. You’re using our form feature to grab data. You’re building out custom workflows where you can set up approvals, notifications, and updates.

You’re looking to visually show a dashboard or report using one of our grid views, search views, or reporting views. You’re also looking to give people different levels of access to the data, so you’re able to create user roles and permissions.

Integration and Developer Options

We also integrate with other tools. So, if you’re working with our platform and you’re a developer—or working with a developer—you can use our APIs, as well as a couple of other tools like Zapier, Make.com, and Integrately.

Submit Questions and Share Use Cases

Again, let me know if you have any questions or thoughts. We’ve got the Q&A section and the webinar chat area, so feel free to drop your questions there or share your use case. We’re keeping an eye out.

If not, like I said at the top of the webinar, I have a ton of information to share. There is never a shortage of information as we dive into Knack and all the features that are available.

How to Get Support

Some general information—how do you get support as you’re starting to build out your application?

We’re available Monday through Friday, from 8 AM to 8 PM Eastern Standard Time. You can also reach out to us at onboarding@knack.com.

And you can learn more about working with our support team and the different support tiers via the link provided, which will take you to our knowledge base. Look under “Working with Support” to explore all the options that are available to you there.

Knack Demo: Volunteer Management Use Case

Alrighty.

I’m going to take a step back here into our slides, and we’re gonna dive into a Knack demo. The use case we’re going to take a look at today is volunteer management—and more. I say “and more” because I’m also going to talk about how you can enhance your apps, especially if you’re starting with a template app, which we’ll be doing here.

And you may be wondering: if you’re starting with a template app, how can you build out or enhance that app further, or use it as a guide as you’re building out your own application?

Accessing Template Apps

So here we are. We’re going to jump into another tab here, so hopefully everyone’s able to see my screen.

We are going to log into our Volunteer Management template app. Just for some quick context—on our website, you can go to knack.com/templates, and you’ll see a list of all our template apps.

You can filter by organization, or you can filter by feature. But as I mentioned just a moment ago, template apps are great as a way to quickly validate whether or not it’s going to work for what you’re looking to build. They’re also a great starting point if you’re comfortable with using databases and no-code applications to build out your applications.

Why Use a Template App?

It’s a great starting point.

It’s also a great way to, as far as building goes, look at different templates to see if one has a specific functionality or workflow you’d like to build out in your application—and then use that as a guide. If you’re not sure and don’t want to dive into each one of these template apps to see what functionality it has, again, you can always reach out to our team at onboarding@knack.com. We’re happy to help you validate.

Installing and Launching the Template

So, particularly for this template app—which we’ll be diving into—you can install these template apps from the template app page. You’ll see the “Install” link.

As long as you have an account set up… (and I just got a notification that I was having a little bit of lag here, so my apologies if things are going slow)…

Here’s that “Install This App” link. You can also learn more about each template app in the information listed there—what features it uses—and again, you can install this for free into your account.

Exploring the Volunteer Management App

Alright, I’m going to drop off this tab here and jump back over to our template app that we’ve already got installed. We’re just going to take a tour through Knack and learn a little bit more about the product and what we’re seeing.

This is a live app. Your live app has its own personalized URL.

That personalized URL will include your account name plus some other details that are related to the app in particular. We’re looking at our Volunteer Management app. Our name for this particular template is “Volunteer Management 2023 Edition Template.” Very long—but you may have something different, like “Volunteer Manager” or “Volunteer Data.”

Whatever you name your app, you’ll see that as part of your URL.

Everything after the hash (#) refers to the page you’re on. That’ll make a little more sense once we dive into the backend of this and start to build out the application, but this makes up your Knack personalized URL. This is what you’d share if you were giving people access to your database. You could copy this link and then share it with your users.

Logging In and User Roles

We’re looking at our Volunteer Management platform, and we have a login form. With Knack, as we discussed earlier, you’re able to set permissions. You can allow people to log in to access data, so you can secure your information.

We use a feature called user roles that allows us to create different roles that may have different levels of access to the information. Right now, I’m going to log in as our admin to see what the admin can see.

Data Views in the App

Upon logging in, you’ll see data being displayed within your application.

We have a variety of ways to display the data—and we call this a view. So here, for example, we’re looking at a grid view. This shows data in a table-style format. All of the data within the system under our Events table is listed here.

You’ll also see a menu view here that looks like a button. We can click it and open a form view that allows us to collect information.

Using Forms and Fields

Being able to add forms to your application to allow people to submit information—from your team internally or from external users—is totally possible with Knack.

Just from this high-level example, you’ll notice we have different field types. Right now, we’re seeing a paragraph field, a short text field, and a date field—but there are many more available in Knack. You can also see we have notifications and buttons here. There are lots of ways to display your data within the app.

Admin Navigation and Volunteer Data

So here we’re looking at events information visible to our logged-in admin. You’ll also notice the top-level navigation at the top of the app. We can navigate to view events, check day-of-event information (if available), or view all of our volunteers in the system.

We have another menu view that allows us to add a volunteer. Again, note the different field types here—email, address, phone number, etc. You can even run counts across tables to get sums, counts, or averages, just as long as the data is related properly.

Calendar and Relational Views

We can also see volunteer details, and we have a calendar view—going back to how we display data in Knack. The calendar view allows us to see events on a calendar, and clicking on those events shows more details.

Exploring a Single Record

Let’s jump back to our Events section. Another important piece to go over is the ability to see more details about a single record in our grid view. For example, we can click “Edit Event” to make changes. But let’s look at the “Clean the Stream” event.

Now we can really get into the relational part of Knack, where we see how data relates across tables. We have an event, and we want to see all the jobs tied to that event and which volunteers have signed up.

Viewing Related Data and Job Registrations

We can definitely start to do that—dive into our app and see the related pieces of data. We could also take a look at the job registrations to see who signed up for our event. We have a specific job, and volunteers are signing up for those jobs.

We can dive in and see even more details about the job, as well as who has signed up within our platform. So again, going back—Knack is relational, and we’re able to show these relationships in one view, like a parent-child relationship.

Wrapping Up the Admin View

Jumping back here, this kind of wraps up what we’re seeing from the admin side of things within the application.

We’re able to show admins everything and give them access to do things that we may not give to volunteers in the system. For example, they can edit an event, whereas we might want to limit that permission or limit the level of access that a different user role or group has.

Volunteer Perspective: Getting Started

So let’s take a quick look at what a logged-in volunteer will see.

I’m pausing here—again, let us know if you have any questions. Take a look at our chat area or the Q&A section while we jump into our app and look at it from the volunteer’s perspective.

Before we dive into this, this is the Builder environment—the design area where you’re designing out your app.

Viewing the App as a Volunteer

Before we dive into the Builder, I do want to take a look at my app from the volunteer’s standpoint.

This might not make a lot of sense right now, but I assure you we are going to walk through it. I’m going to go look at Volunteer Events, and I believe that is this here.

One thing to note—we are still logged in as an admin. As you know, the admin doesn’t have access to the volunteer area unless we explicitly give them access. This is just to show you: if you’re wanting to limit which pages a user can access, this admin cannot see what the volunteer sees. So we’ll have to log in as a volunteer.

Switching to the Volunteer Role

I’m going to grab those details here and log in. This will log me out of the admin session and now log me in as a volunteer.

You can see my tabs have completely changed up top.

Another thing to note—our URL is also slightly different. Again, I mentioned that everything after the hash relates to the page you’re on. So here we are seeing that we’re on the Volunteer Events page, versus the Admin Events page.

Volunteer Experience Overview

So again, taking a look at what our volunteer is seeing—they can see events, but you’ll notice they don’t have edit access. They can only see what’s upcoming. They can view any event and view the jobs tied to the event.

Again, there’s no option for them to make edits. They’re mostly in read-only mode for what they see here.

We’re able to display details for a single record, as well as related pieces of information—those related records on the Event Jobs table. We can see whether jobs have been filled or not.

Job Sign-Up Experience

We can also allow volunteers to sign up for the job. If jobs have already been filled and there’s no room left to volunteer, we can trigger a notification that says, “Hey, it’s too late. These jobs have been filled.”

And we can dive into how that’s set up in the application.

If we jump back to a job where there are still openings, again, you can see that all jobs have not been filled. We can dive into a single job, and we should see a form on the page that allows the volunteer to go ahead and sign up.

They click “Sign Me Up”.

Confirming Volunteer Sign-Up

As we get redirected back to the event page, we can see that we now have new volunteers signed up for this particular job.

Alrighty—and we were redirected back to this page here.

Volunteer Access and Navigation

So again, the volunteer has very limited ability to do anything beyond signing up for events. But they can still access and view that information within their application.

We can jump over to their navigation here at the top. They have different views—they can see the events they just signed up for. As you can see, I used the “Sign Me Up” button and included a comment, which is now visible with that event.

And again, you can add links to these views to show more details about a particular registration.

Volunteer Leaderboard and Count Field

This particular app also includes a leaderboard, where you can make things a little competitive among volunteers. They can see how many jobs they’ve signed up for. This is powered by a feature called a count field, which runs a count of all the jobs an individual volunteer has signed up for.

So again, we’re working with two different tables within Knack—and using a formula field to run sums, counts, or averages.

Pretty cool feature. We’ll definitely dive into that more in just a second.

But this is what a logged-in volunteer would see in the app for that particular role.

Granular Access with Knack

A really nice piece about Knack is that it supports different users and gives them as much—or as little—access to the data as makes sense for your use case.

Exploring the Backend

So let’s take a look at the backend and see what this looks like within a Knack application.

I’m going to actually start on the left-hand side here and work my way down and across. We’ll go through what it looks like if you’re using or starting with a template app—how to even make sense of where you’re at, what you’re doing, and how to customize this to meet your needs.

We’ll cover some of the basics of getting started with Knack and understanding the features, and then talk about how to update and edit.

Understanding the Data Tab

The first thing we’re looking at on the left-hand side is our Data tab. The Data tab shows all of our tables within the system and our user roles.

If I start at the top with my tables, I can click on a table and you’ll see that I’ve already got some fields populated on the right-hand side. I also have some actions I can take at the top, and another button to continue adding fields.

Encouragement to Explore

At this step—if you’re just getting started building in Knack—please, please give yourself the freedom to explore.

I could sit here for hours and take you through: “This is what happens when you click here,” or “See what happens when you click that,” but I do want to encourage you to click around and explore.

You probably won’t remember where everything is right away, and that’s okay. Giving yourself that freedom to explore early on will help you feel more comfortable once you really start building out your solution.

Table Settings and Field Types

So again, we are on our Data tab. We’ve selected our Events table.

You’ve got some actions up top—you can edit or rename the table. You’ll also see table settings where you can change the table name and set your display field, which acts as the lookup field in dropdown menus.

You can also set your sort preferences here. This becomes important when you’re connecting tables—like Event Jobs connected to Events, or Event Signups connected to Event Jobs. This field determines what appears in the dropdown when selecting a related record.

This may not make sense yet, but we’ll touch back on it shortly.

Adding Fields to Tables

If you want to build out the table further, click “Add Field.”

We have a variety of field types in Knack to help ensure data is captured in the most efficient way possible:

• Text fields
• Number fields
• Formula fields (like sum, min, count)
• Count field, which we mentioned earlier

For example, you could say: “How many event jobs are tied to this particular event?” Using the count option, you can look into a connected table and retrieve that count from Event Jobs.

You’ll also see formatting and filter options. For instance, you might want to count only jobs that are active. If you had a field like “All Jobs Filled = No,” you could filter on that to count just the remaining open jobs.

Again, we won’t dive too deeply into that right now, but it’s a useful feature when working with table connections.

More Field Options

Continuing down, you have lots of choices when it comes to field types:

• Date fields
• File/image upload fields
• Personal detail fields
• Link and connection fields (these tie your tables together)

Combining Fields (Q&A)

Alright, pausing here—just making sure I’m not missing any questions.

Looks like one just came in: “For the display field, can you combine two fields, like an ID and a client name, in case there are multiple clients with the same name?”

Yes, that’s a great question—and the answer is yes!

Let’s say we have a Volunteer table and two volunteers with the same name. How do you distinguish between them?

You would use an ID field, and Knack provides a Text Formula field to do something similar to concatenation in a spreadsheet.

Adding Tables and Import Options

Back to tables—you can add new tables by clicking “Add Table.”

Once you do that, you’ll see options to:

• Add a table from scratch
• Import your data
• Start with a pre-made table
• Use Google Sheets integration

You’ll see those import options clearly: you can start with pre-populated fields, or bring in data from Google Sheets.

I’ll exit out of that—but that’s how you create a new table and add additional fields.

User Roles and Permissions

Now jumping down to this next area—User Roles—and also addressing the earlier question about combining fields.

User Roles are also tables, but they serve a unique purpose. They help manage permissions when we get to the Pages tab and begin designing the pages of our live app.

They can be treated just like other tables—you can add fields to them like you would any other table.

But this is also how we configure permissions.

Creating User Roles for Volunteers

Let’s say we create a new table from scratch to allow volunteers to log in and take actions.

We’d treat that as a role, just like a table. We’d build it out with name fields and other necessary details.

For example, I’ll rename this table to “Volunteer Users,” so we know what we’re working with.

However, if we don’t configure it correctly with permissions and connections, we won’t be able to leverage it much when designing the Pages of the app.

User Roles and Login Page Logic

So, if I jump over to Pages—I know I might be jumping around here—we have a feature that allows us to create a login page that works with a specific group.

If we had wanted to pull in our Volunteer Users, we don’t have that as an option unless it’s set up under User Roles. So it’s really important at the early stages to ask: Who needs to log into my application? That decision determines whether a table should live under Tables or under User Roles.

So, jumping ahead a bit—the way to determine what should be a user role versus a regular table is this:
👉 If someone needs to log in, create it as a user role.

You can still build that role out like a table—it just also enables login permissions. That’s the purpose of user roles. It starts the process of controlling access to the app once you head over to Pages.

It also ties into connecting logged-in users to actions like event signups.

Connecting Records Across Tables

What do I mean by that?

When we talk about connections, we’re talking about how tables relate. For example: how do you tie an event signup record in your database to a specific volunteer in your user role table?

This is where connection fields come in.

Let me walk you through it.

We already have, for instance, a dropdown that lets us select a volunteer when entering a signup. That dropdown pulls from the Volunteer table. The field that shows up in the dropdown is what we set in the display field under table settings.

Creating Connection Fields

How did we get that dropdown field into our app?

Let’s go back to Fields. You’ll see a field type called Connection. You can add a connection field in two ways:

1. From the Fields tab in the table.
2. From the right-hand panel in the app.

This allows you to say, “Hey, I want to connect to my Volunteer table,” and then you can proceed to define that relationship.

Where to Place the Connection Field

Now, before I walk you through that—how do you know where to place the connection?

Should you put it in your Event Jobs table?
Or in the Signups table?

Here’s the rule of thumb:
🔁 One-to-many relationships → the connection field belongs on the “many” side.

Another way to think about it (if you’re familiar with databases):

• The foreign key lives in the child table
• The primary key lives in the parent table

So if:

• Events is the parent
• Jobs are tied to events
• You’ll place the connection field to Events inside the Jobs table.

Same logic applies if:

• Volunteers sign up for jobs
• You’ll place the connection to Volunteers inside the Signups table.

If you’re tying a volunteer to a signup, that connection field lives in the signup table.

Adding the Connection

When you go to add the connection field, choose the parent table you want to connect to.

So, if you’re on the Signups table and connecting it to Jobs, you’d see this:

“Each signup connects with one event job”
✅ That’s true.

“Each event job connects with many signups”
✅ Also true.

If you find yourself having to reverse the logic just to make it work, you’re probably in the wrong table—exit and start again from the right place.

Once the connection is added, you’ll be able to select a volunteer from the dropdown in your signup form—pulled directly from the user role table.

Role-Based Page Access

Again, user roles behave like tables—you can add fields to them—but they also serve the purpose of controlling who sees what pages in the app, based on their role.

Navigating to Records

Let’s now move top to bottom, and also left to right across the interface.

Starting with Records:
This is where you can get a high-level overview of all the data in your system. From here, you can:

• Import records
• Export records
• Batch update
• Batch delete

All handy tools when managing your data.

Automating with Tasks

The Tasks tab won’t show up during the trial—it’s a feature available on our Pro plan and above.

Tasks let you automate workflows, such as:

• Sending trigger emails
• Dynamically updating records
• Inserting new records into connected tables

If you need those automations, explore upgrading to the Pro plan.

Designing with Pages

Finally, we come to Pages—where all the magic happens in your application.

This is where you build the front end of your app and start tying everything together:

• Who sees what
• What views they interact with
• How data is displayed based on roles and relationships

Revisiting the Text Formula Field

Oh—you know what? Before I jump to Pages, I need to make sure I address a previous question that was asked about the Text Formula field. Sorry, my bad—I forgot to go back to this.

We were talking about our Volunteers table specifically.

The question was: What if you have two people with the same name—say, two Alonzo McReidys or two Jared Gonzaleses—and you want to distinguish between them?

Let’s say we don’t have a great unique identifier showing in the app. In that case, you can use a feature called an Auto-Incrementing field to assign each user a unique ID.

Creating a Unique ID Field

You’ll see this option when you go to Add Fields—look for Auto-Incrementing.

All it does is start at 1 and increment up automatically for each new record. Let’s go ahead and call this our ID Field.

It doesn’t have to be an auto-incrementing field, though. You can use any field that captures a unique piece of data. If you already have unique ID numbers stored elsewhere, you can pull those in, then combine them with a name using a Text Formula field.

Combining Fields with Text Formula

So what do I mean by combining these two—maybe the name and the ID?

The Text Formula field is great not just for this, but for lots of other things. You’ll find different functions inside the formula editor. In this case, we’re just going to combine the name field and the ID field.

You can add formatting, too—like wrapping the ID in parentheses or adding a hyphen between the name and ID.

If I jump into Records, we should now see the combined value appear, showing each volunteer’s name alongside their unique ID. Hopefully that helps clarify things!

Let us know if not.

Field Settings and Validation Rules

Continuing forward—there’s a ton of functionality and features just like what we saw with the text formula field.

In your field settings, you’ll find:

• Formatting options
• Validation rules
• Conditional logic

Again, I can’t say this enough: give yourself time to explore. Click all the links, dots, ellipses, carets—just poke around and get familiar with the settings.

And of course, if you get stuck or need help, our team is always happy to assist. Just reach out.

Moving to Pages: Where the Magic Happens

Alright, being mindful of the time—we’ve talked about Data, Records, and a few core Knack features. Let’s now jump into Pages, where all the magic happens when building out your application.

So, what is a Page?

Let me walk you through it in a way that hopefully gives you some clarity when you’re getting started.

Understanding Page Structure

Right now in our Volunteer Management app, we’ve already got some pages set up.

Any page with a lock icon is a Start Page—it’s part of your top-level navigation.

If you remember from earlier, when we looked at the app logged in as the admin, you saw “Events,” “Event Day,” “Volunteers,” “Event Calendar.” These are the top-level items.

Once you’re past login, these nav items come from your page structure in Knack. You create this navigation using the “Add Page” button.

Page Types: Public, Login, and Role-Based

When you click the plus icon to add a page, you’ll get a few options:

• Public Page: Anyone with the link can see it. Use this for registration forms or public info.
• Login Page: For role-based access. This is where you start giving permissions to users.

For example, if you’re building a volunteer registration form, you can put that on a public page. But if you want volunteers to log in and manage their tasks, you’ll need a login page.

Knack will ask: Do you want to give permission to all users? Or only a specific group?
If you say specific group, you can assign it to your Volunteer user role.

Once you have your user roles and relationships set up properly, limiting access becomes super easy.

Building a Volunteer Dashboard

So let’s say we want to create a Volunteer Dashboard.

After clicking Add Page, we assign it to the Volunteer role.

Once that page is created, it’ll be empty at first. So now we have to start adding views.

For example, we may want volunteers to see a list of jobs they’ve signed up for. Because we connected the Signups table to Volunteers earlier, we now have the option to filter data based on the logged-in user.

We’ll choose:

“Show signups connected to the logged-in volunteer.”

That’s how Knack knows which records to show per user. You can continue to add permissions, link to detail pages, and define what actions users can take—like viewing or editing their signups.

Grid View Basics and Source Settings

Once your view is added—let’s say a grid—you’ll notice it’s selected by default (you’ll see a gray background and view settings on the left).

Clicking elsewhere deselects the view. You can click back into it by clicking the pencil icon or anywhere on the view itself.

A few quick tips:

• Always check your source—this tells you what data is showing.
• If a grid is showing all signups instead of just the logged-in user’s signups, your source settings may need adjusting.
• Re-add the view and make sure to select “connected to logged-in user”.

Customizing Views and Columns

In your grid view settings, you can:

• Enable keyword search
• Enable record exporting
• Allow inline editing, like a spreadsheet
• Hide or show columns
• Add column summaries (totals, averages)
• Add or remove action links (like “Edit” or “View More”)

You can also pull in fields from connected tables, like displaying a volunteer’s phone number from a related table.

And don’t worry—removing a field from a view won’t delete it from your database.

Adding Record Rules and Email Notifications

You can also add:

• Record Rules: e.g., auto-fill a field with the current date or a note when a form is submitted.
• Email Rules: e.g., notify a staff member when a volunteer registers.

You’ll find all these options under your form view settings.

Wrapping Up the Webinar

Being mindful of time—we’ve covered:

• The Data tab
• The Records tab
• A bit about Tasks (available on Pro plans)
• The Pages tab (where the app comes to life)

Adding a page starts with the plus button. Then you add views to define what users can see and do.

Login pages don’t show as many options because they’re usually kept simple, but you can always build more as you go.

Final Tips and Support Info

We had a quiet group today, but I hope the information was helpful.

This video will be available for you to review later, and we have many more webinars available on our Knack Webinars page.

One last note—because of the relationship between events and jobs, it’s super easy to show those child records. Just go to your event detail page, and Knack will know to offer “Event Jobs connected to this Event” as an option. It’s all driven by your Data tab relationships.

Support Resources

If you need help, don’t hesitate to reach out to us:

📧 onboarding@knack.com
📚 Visit our Knowledge Base
💬 Use the Help icon inside the Builder

There, you’ll find:

• Integration help
• Expert directories
• Community resources
• Live support

Thanks again for joining us today. I hope everyone has a wonderful rest of your day!

Bye, everyone! 👋