Wondering if it is possible to have multiple signup / update pages in the new app version yet? I tried before and ended up rolling back because it was no longer possible.
I have multiple user types requiring different information from each user type, thus when each user-type creates an account or updates information they need to access the site through a specific creation or update link.
I see that I can only link all the signup pages to one database. Is that correct?
If i want to create user profiles, do they need to be linked to the same database? Or if i have multiple user types can they each have their own database for user profiles?
Indeed, each Softr App has one Users entity - which can be synced with one database table.
The recommended setup in case you have, as you mentioned, multiple user types is to have fields to differentiate them, for example “Role” as a select field:
Thanks so much! Does the role assignment need to be done manually or how can it be automated during the signup process? Or is this done through the redirect to a new form?
Sorry if this should all be very obvious, I am just not seeing how everything works together.
Sorry more questions about the databases: I see that when I create a database "from scratch” it automatically makes a database with a different colour and Icon. I am not even sure what these colours and Icons mean or if I am supposed to have a certain kind of database.
In your screenshot I see that you have multiple tables (tabs). Is this the way to setup the database / tables correctly? Rather than having one database for each user type? I am not even sure I am explaining myself correctly.
When it comes for the role assignment, as you could see in my screenshots, it is then connected to a Select field (1 value per user group in my case).
And then there are multiple ways to add the right value for the right users.
If you are building an internal tool where you will actually not even have a sign up page because this is not open for more people to create their accounts, you will have in your app maybe an admin role that will be the one adding new users whenever you get a new hire, for example. They would select, in a form when they are creating that account, the role to assign to this user, and they can also use that to modify the role in the future. This would make them proper admins of that Softr app.
If this app is more of a public facing app where you have signup flows, then you can eventually, let’s say you’re building a recruitment portal. You could have one signup page for talents and one for companies and use a hidden field for each of those signup pages to pass the value either talents or company as their role when they sign up.
If it’s up to your users to declare their role, you could also have an onboarding flow, which is also a native feature in Softr, where you give them the options to pick their role, which will set that value for the role field in the users table in your database.
Now, if you like to learn more about the best practices to set up your database before building an app, I highly recommend this tutorial where we go through all the steps of app building. It starts with building the database, indeed one database and then multiple tables, one table per object. For example one table for users, one for projects, one for tasks, one for documents.
