Let Portal Users Create, Edit and Delete Records

Read-only portals answer questions. Two-way portals remove work.

If a contractor can update their own compliance documents, nobody on your team is copying them out of an email. If a client can file a request, nobody is re-typing it into the base.

What it does

With the right permissions, portal users work with records directly:

• Create: a form built from the fields you allowed, writing a new record into Airtable
• Edit: change existing records, field by field, with your rules about what is editable
• Delete: remove a record, behind a confirmation step

Every write goes straight into your base. There is no queue, no staging table, and nothing for someone on your side to approve into place.

Why it matters

This is where a portal stops being a nicer way to look at data and starts saving time. The person who knows the answer types it in once, into the system of record, instead of sending it to someone who types it in for them.

It also improves the data. A form built from your Airtable fields collects the right shape: dates as dates, selects as options, required fields filled in. That is a different thing from an email with the information somewhere in the third paragraph.

Controlled by the same permissions

Nothing here is all-or-nothing. What a user can write is decided by the layers they already sit under:

• Table permissions decide whether the role can create, edit or delete in this table at all
• Field permissions decide which fields appear on the create form and the edit form, and which are required
• Record ownership and filtering decide which records they can reach in the first place

So a client portal can allow a client to add a request and update their own contact details, while every internal field on the same table stays untouchable.

How it works

Turn the table switches on, decide the fields, and check the forms by opening the portal as a real user. The guides cover each step: creating records, editing records, and deleting records.

Who it is for

Any workflow where the information starts outside your team: internal request portals, contractor compliance, issue tracking, and event crew scheduling where people confirm their own shifts.