Hello, what happens if I use a static custom code? How do I put the prebuilt functionality features into practice? Using the forgotten password feature as an example? Many thanks
I have 2 kinds of users: Employees and external contract workers. In Airtable, external workers have a table and employees have separate table. In the following video, we configured users to be connected to a specific table (for example, in my case, the contract workers). What if I want to connect the employees to also view the same page? The current configuration forces me to have the 2 types of users on the same table on Airtable, which seems to be a bit problematic from a backend design perspective. In that case, do I need to create a separate app? If yes, then it means I have to redesign the same pages twice
Hi! it is typically best practice to have one users table. Then you can create a single select field within that table that indicates if they are an Employee or External Contract worker. You can also create separate views within that table to only show Employees and Contract workers, for instance. If you have further questions, our support team is standing by! www.softr.io/
ok, but what about membership users? I need to build a membership site and as I understand it, in order to get more than 5 membership users I would need to on the $65/month tier?
Great walkthrough thank you so much
Hello, what happens if I use a static custom code? How do I put the prebuilt functionality features into practice? Using the forgotten password feature as an example? Many thanks
I have 2 kinds of users:
Employees and external contract workers. In Airtable, external workers have a table and employees have separate table. In the following video, we configured users to be connected to a specific table (for example, in my case, the contract workers).
What if I want to connect the employees to also view the same page?
The current configuration forces me to have the 2 types of users on the same table on Airtable, which seems to be a bit problematic from a backend design perspective.
In that case, do I need to create a separate app? If yes, then it means I have to redesign the same pages twice
Hi! it is typically best practice to have one users table. Then you can create a single select field within that table that indicates if they are an Employee or External Contract worker. You can also create separate views within that table to only show Employees and Contract workers, for instance. If you have further questions, our support team is standing by! www.softr.io/
ok, but what about membership users? I need to build a membership site and as I understand it, in order to get more than 5 membership users I would need to on the $65/month tier?
Hi Hugh, that is correct. If you want more members (users), then the professional plan is for you.