Welcome to the community!
You wouldn’t be able to combine all of that together with the built-in features of Airtable.
Built into Airtable: you can create different filtered views for each one of your clients, and then share with them a read-only link to that specific view. So that would enable you to give each client read-only access to their items.
However, there is no built-in ability for them to update fields in their existing record. A quick & easy tool that was created for this task is Single Record Editor for Airtable, which gives you a unique URL for each one of your records — and then that unique URL will take your client into a form to update record. You can choose which fields will show up on that form — but all the fields will be editable, not just the one “Client Comments” field.
To combine both of these features together, you might want to check out Stacker, which creates a new web interface to your Airtable database that lets you choose which records each client can see, and which fields each user can edit. It’s pretty cool.
There are lots of other paths you could go down as well, such as creating a custom form using Integromat & Formstack.
Welcome to the community!
You wouldn’t be able to combine all of that together with the built-in features of Airtable.
Built into Airtable: you can create different filtered views for each one of your clients, and then share with them a read-only link to that specific view. So that would enable you to give each client read-only access to their items.
However, there is no built-in ability for them to update fields in their existing record. A quick & easy tool that was created for this task is Single Record Editor for Airtable, which gives you a unique URL for each one of your records — and then that unique URL will take your client into a form to update record. You can choose which fields will show up on that form — but all the fields will be editable, not just the one “Client Comments” field.
To combine both of these features together, you might want to check out Stacker, which creates a new web interface to your Airtable database that lets you choose which records each client can see, and which fields each user can edit. It’s pretty cool.
There are lots of other paths you could go down as well, such as creating a custom form using Integromat & Formstack.
Thanks Scott! but I just would like to point out a workaround for this. If you would like to prevent users from editing specific fields -but you still want those fields to be visible- you can make a read-only copy of them by using formulas. That way they’ll become uneditable.
Thanks Scott! but I just would like to point out a workaround for this. If you would like to prevent users from editing specific fields -but you still want those fields to be visible- you can make a read-only copy of them by using formulas. That way they’ll become uneditable.
Oh, nice! With the built-in Airtable forms, you can’t put formula fields onto your forms at all! So that’s another great feature of your extension! Add that to the features list! :winking_face:
Thanks Scott! but I just would like to point out a workaround for this. If you would like to prevent users from editing specific fields -but you still want those fields to be visible- you can make a read-only copy of them by using formulas. That way they’ll become uneditable.
@Moe, what is the difference between these 2 extensions? It seems like both of them will allow you to edit a single record at a time, based on the URL for that record:
@Moe, what is the difference between these 2 extensions? It seems like both of them will allow you to edit a single record at a time, based on the URL for that record:
The 1st one
Supports all field types
Requires adding a new temporary record (which effects autonumber)
The 2nd one
Field types support is limited
Doesn’t support uploading attachment
Supports showing attachments
Supports showing formulas
These are the main differences, but the most important difference is that one uses Airtable’s nice features and UI and the other one doesn’t. Most people use the first one since it’s crucial to support linked records, single/multiple select…etc.
The 1st one
Supports all field types
Requires adding a new temporary record (which effects autonumber)
The 2nd one
Field types support is limited
Doesn’t support uploading attachment
Supports showing attachments
Supports showing formulas
These are the main differences, but the most important difference is that one uses Airtable’s nice features and UI and the other one doesn’t. Most people use the first one since it’s crucial to support linked records, single/multiple select…etc.
Thanks for the explanation, Moe!