The only way that you can do this is to completely restructure the entire database as a "many-to-many relationship", which is a more complicated type of relationship that requires 3 tables (instead of 2 tables) for your record linking.

You can read more about many-to-many relationships in Airtable's support document here.

Also, If your company has a budget for this project and you’d like to hire an expert Airtable consultant to help you set all of this up for you, please feel free to contact me through my website:

Airtable consulting — ScottWorld

Thank you; this article is helpful but I'm struggling to imagine what my three tables are. New hires, onboarding tasks and ??

You can call it whatever you want: “junction table” or “individual tasks” or “new hires x onboarding tasks” or whatever you want!

You could try using an automation with repeating groups if you'd like.  Make an automation that'll trigger when a new employee record gets created, look for all your template tasks, and create them all and link them to the new employee:

Link to base

Record templates are the newer & easier way to automatically create linked records, but @brianna_eagen will still need to have a 3rd junction table in her base.

Thanks - I'm not stuck on the naming, more what the actual content of that table would be. Just to track the additional field of complete? In this scenario, is there one row per employee per task?

Employee name, task name, complete y/n

Employee name, task 2 name, complete y/n

Each record would link to one employee and one task. So you will have 2 linked record fields: one linked record field for employee and one linked record field for task.