Custom Object Records

Knack lets a business define its own objects, such as customers, orders, or projects, each with custom fields inside a hosted app. A Beam agent reads records from a chosen object whenever a trigger fires elsewhere in the stack, such as a new order or an updated status. Where the connector and account permissions allow it, the agent writes the matching field back into Knack so the app reflects the change without someone opening it manually. Updates that touch a field marked sensitive, or that would overwrite data entered by a person, are routed to a human before anything is saved.

Connected Field Views

Knack apps often link one object to another, so an order record can show connected customer or product details inside a single view. A Beam agent reads across these connections when it needs context beyond a single record, such as checking a customer's history before updating an order. Where the connector allows it, the agent follows the same connections a person would use in the app and applies its update to the correct linked record. Cases where a connection is missing, points to more than one match, or looks inconsistent are routed to a human to resolve before any record changes.

App User Roles

Knack apps are built with user roles that decide who can see or edit which records, from staff logins to customer portals. A Beam agent checks the role tied to a request before it reads or writes anything, so it only touches records that role is permitted to reach. Where the connector and account permissions allow it, the agent completes the update within those limits and leaves a note on the record for the app's owner. Any request that would need a role change, or that falls outside the permissions already granted, is routed to a human to approve.