In this article, you will find general information about Knack's main features and links to learn more about them.
The Knack Dashboard is where you manage your account, as well as access and share all apps on your account.
The Knack Builder, also called the Builder, is where you design and create your app. Here you define what type of data your app uses and how it will present that data to your users.
Tip: You can learn more about the Knack Dashboard and Builder here.
The Live Application, or Live App for short, is where your users will interact with the data defined in the Knack Builder. The Live App is composed of pages, which are made of visual elements called "Views".
Think of the live application like a website, which includes pages and different visual elements like forms, grids, and menus.
Tip: You can learn more about your Live App here.
The App Settings can be found within each individual app and are used to define various settings for the app, such as layout, colors, E-commerce functionality, security settings, API & custom code, user logins, and embedding.
Tip: To learn about Live App Security settings found in the app settings, see our article here.
Tables are used to separate your data into common groups and are composed of fields and records. You can think of a table like a spreadsheet or a database table.
Tip: You can learn more about working with tables here.
When table records are shown in connection fields, the value representing the table in the connection field is the display field. This is a specific field chosen to represent that table.
Fields are used to define the types of data used in a table. You can think of fields like columns in a spreadsheet where each field is an individual column.
You'll want to add a field for each different type of data you want to store for your table.
Tip: You can learn more about fields here.
You can think of records as rows in a spreadsheet where each row is an individual record. This looks like a table in a traditional sense, but each individual row is a record.
Tip: You can learn more about working with records here.
Connection Field Types
- One-to-one connection:
A connection type where two tables can only be connected by one record from each table.
Example: In a connection between a Contact table and a Company table, each Contact record connects to one Company record and each Company record connects to one Contact record.
- One-to-many connection:
A connection type between two tables, where many records from one table connect to a single record from the other table.
Example: In a connection between a Contact table and a Company table, each Contact record connects to one Company record and each Company record connects to many Contact records.
- Many-to-many connection:
A connection type where two tables can be connected by many records from each table.
Example: In a connection between a Contact table and a Company table, each Contact record connects to many Company records and each Company record connects to many Contact records.
Tip: To learn more about connections, see the following articles:
A page is used to group multiple views which visually display the data in your app. Your Live Application can have multiple pages that your users can navigate with menus and links.
Pages in the Live App:
The page tree is the listed page structure in the left hand menu when viewing the Pages section of the Knack Builder. This includes different types of pages like Login pages, Starting pages, and Parent & Child Pages.
- Start Page: A start page is a starting point into your app. A start page is always a parent page.
- Parent & Child Pages: A parent page is one that has other pages (child pages) that it links to.
- Login Page: A page that is password protected and requires a user to login.
- Single Record Page: Any child page that has the data for a single record and can display Details Views, Edit Forms, and/or connected records.
Tip: You can learn more about working with pages here.
The page menu appears at the top of your Live App where it displays page links to the starting pages in your app. This is managed within the "Pages" section of your Builder.
Tip: You can learn more about page menus here.
View Editor: The section in the Builder for editing the settings for individual views. You access the View Editor by clicking on the pencil icon that contains the view name.
View Types: There are multiple view types which format the data in your app differently. These include grids, lists, searches, forms, calendars, maps, reports, menus, and rich text.
Source: The primary source is the main table used by a view. For example, if a Form view created a new record for the Contact table, the Contact table will be the form’s primary source.
Tip: You can learn more about views here.
Submit Rules are a type of form rule. They determine where the user is taken upon successful form submission, such as display a message or redirect a user to another page.
Tip: You can learn more about submit rules here.
Display Rules are a type of form rule. Display rules control how a form is displayed. For example, form inputs can be shown or hidden and input labels can be updated based on other form and record values.
Tip: You can learn more about display rules here.
Record rules are a type of form and grid rule. These rules allow you to perform specific actions behind the scenes when a form is submitted in the live app.
These rules can update the record the form is using, update connected records, and insert new connected records.
Tip: You can learn more about record rules here.
Conditional rules are used to set the value of a field based on defined conditions.
Tip: You can learn more about conditional rules here.
Validation rules define which values are or are not allowed to be set in a field via a form, by adding a record manually from the Builder, or by inline editing a field's value.
Tip: You can learn more about validation rules here.
Page rules are actions that can be automatically triggered based on conditions you define as soon as a user enters a page. Page rules can hide views, show a message, redirect to the parent page, redirect to an existing page or redirect to another website URL.
Tip: You can learn more about page rules here.
Tasks are automated actions that can be applied to your app records on a scheduled basis (daily/weekly/monthly). These actions can drive your app’s workflow in powerful ways, such as sending automatic reminders when a deadline is coming up or automatically adding your to-do records periodically.
Tip: You can learn more about tasks here.
Users & Logins
A user is anyone that has an email and password to login and access your live app. Each user is stored as a record in the Account table in your database.
The Account user table stores all user records regardless of assigned user roles.
Users roles are a specific type of user, common examples are Admins and Employee.
Logins require a user email and password to access pages in the app. This can be used to restrict or allow access to different pages and views in the app, based on the user type, or user role.
Tip: You can read more about users & logins here.
The account owner is the primary owner of the Knack account. This person has access to all apps and settings on the account.
A Shared Builder is an additional user, which has access to the Knack Builder for an individual app. These Shared Builders are added to individual apps, rather than an entire Knack account.
These users will be able to fully edit the app shared with them, including adding, editing, and deleting elements from both the Data, Records, and Pages section of the Knack Builder.
Tip: You can learn more about sharing apps with shared builders here.