Apr 14, 2024 03:36 PM
Solved! Go to Solution.
Apr 14, 2024 05:00 PM
Create a table of People and add fields for all their information including 'Domain'. The primary field in this table could be their email or first name. In the table in question, make a linked field to this People table, plus a lookup field for the 'Domain'. Then proceed to automations. The trigger for this one should be When a record is created in the table in question, update the new record with the name or email (whichever is the primary field in the People table) of the name or email of the 'user who took action'
Feel free to schedule a free call with me if you need more help! - Brian
Apr 14, 2024 05:00 PM
Create a table of People and add fields for all their information including 'Domain'. The primary field in this table could be their email or first name. In the table in question, make a linked field to this People table, plus a lookup field for the 'Domain'. Then proceed to automations. The trigger for this one should be When a record is created in the table in question, update the new record with the name or email (whichever is the primary field in the People table) of the name or email of the 'user who took action'
Feel free to schedule a free call with me if you need more help! - Brian
Apr 15, 2024 01:08 PM
Thanks Brian, this solution does work but the only problem with this is that if users want to update the Domain manually then they won't be able to do so. As it's a lookup field based on the linked field on the People.
Apr 15, 2024 02:02 PM
If you want to have it so they are able to update their domain, you can give them access to the People table. If you want a user login situation where they have control over their details and no one else's, this would not be possible using just Airtable. You'll have to use an application like Softr or Fillout which uses Airtable as a backend.