Portal user provisioning

Softr builds portals and apps on top of Airtable data with logged-in users. When a new user should have access, a Beam agent reads the request and the Airtable record behind it, applies your approved rule, and grants the right portal role or membership where account permissions allow. The user record notes the access granted. When a request names someone not in the source data, asks for an admin role, or would expose a restricted view, the agent holds it and routes the decision to an administrator instead of granting access on its own.

Airtable-backed content refresh

Softr pages render live from Airtable, so the app reflects whatever the base holds. A Beam agent reads changes in the connected records and, following your rule, updates the fields that drive published blocks, lists, and detail pages so content stays current without manual edits. Routine updates flow straight through. When a change would remove a published item, alter pricing, or touch a field your rule marks sensitive, the agent stages it and notifies an editor to approve before the portal shows it to users.

Form submission handling

Softr forms write submissions back into Airtable. A Beam agent reads each new submission, applies your rule to check required fields and categorise the entry, and updates the underlying record or creates a follow-up task for the right owner. A confirmation can be noted on the submitter's record. When a submission is missing required detail, looks like spam, or asks for something outside the rule set, the agent sets it aside and notifies a person rather than writing incomplete or suspect data into the base your app depends on.