Fillout + Airtable + Softr Setup for Client Portal

I am building a client portal for my friend marketing brand

The journey starts on Fillout where the clients will answer questions based on the service they want

All the answers will be saved on an Airtable base

From the airtable base there will be different tables, including “Project”, and “Tasks” tables.

I want to connect those Project and Tasks tables to Softr so my friend can see all the Projects and also the client can see only the tasks for the specific service they selected in the initial Fillout Questionnaire.

What I am struggling with is how do I make sure that the relevant tasks for a specific service are shown to be completed in each client’s portal?

Any guidance would be helpful

I have attached a Loom video explaining a little bit more

Hey!

What you’re asking for is one of Softr’s strengths, largely due to its user-friendly interface.

Almost every block includes a ‘filter’ feature. When setting the data source and mapping fields, you’ll find an option to add filters.

This feature allows you to show tasks that should be visible only to specific users. When setting up tasks in the ‘tasks’ table, you likely have a ‘user email’ field.

In Softr, you can add a filter to your mapped tasks table. Set it so that the logged-in user can only see records where the ‘email’ field matches their own email.

Let me know if you already understood this and were looking for more advanced guidance.

Hi @acjnas ,

Thanks for your reply.

Currently I do not have an email field within tasks table, however I will have a “Service” field.

Does the same logic apply in this case?

Would I be able to set a filter on tasks set to a specific Service?

Hope I am making sense

Oh yeah, filters are very versatile and can be set based on almost any condition from any field type.

You just need a way to identify tasks in reference to the user. For example, if you add a condition to show “service” = “design,” all records with that condition will show to any user. What you want is to hide records that do not belong to the user’s session.

The recommendation is to associate a property from your ‘users’ table with your tasks table. The usual choice is the email address, but it can be anything that uniquely identifies the user.