How to create secure user dashboards with multiple sections in Webflow for a marketplace?
If i want members to have their unique and secure page in webflow, is it best to have a cms page or use attributes on static pages? or any other way around this matter, thanks in advance 🙂
I want it to be kind of advanced, like a dashbord where the user have full control over their information, data, etc. I'm trying to build a marketplace, but find it a bit difficult to make the dashbord so the users can move to e.g. inbox, earnings, settings, current jobs/projects, etc. Is that even possible, because if I give the users their unique cms page, its only one page, and then i have to use tabs to select out these different pages....
Comments
1 comment
Hey Aleksander Kjølberg,
If you want you can also show or hide items from users based on code, like how its done in this free CRM template where deals are shown for relevant users via a static page, you can do so. If the data you are populating on the page comes from a CMS and is not sensitive in nature, you could go for such approach, but if its sensitive in nature, you might want to have unique pages for each member where only relevant information is populated (without you having to hide or show it after the page loads via custom code).
You could explore templates like Premium Job Board and Advanced Job Board to get some idea as to how the dashboard is handled and how other parts of the project are linked to it from a user perspective. Hope this gives you some idea. Explore and research for your project and feel free to reach out, if you face any blocker during implementation.
If its just basic textual data like name, email, any custom fields data stored in Memberstack, you can have a static page like 'dashboard' and you can make use of attributes to show unique data as per the logged in user.
If you plan to show more data (in future) which you are not storing in Memberstack or if you want each user to have a unique URL for some reason, or if you are storing some data for each member in Webflow CMS (or any other database), its better to have CMS page setup and have a workflow create a new CMS item for new member sign ups on Memberstack. In CMS pages, you can use attributes as well, but you also have the option to filter data as per the current user (without using custom code) if you want to show other collections from Webflow CMS which are linked to Members collection in Webflow CMS. This approach is recommended if you want to customize and show data that you are not storing in Memberstack for each member.
So the best choice depends on the project use-case and what you want to setup for users in long run. Hope this gives you some idea.
Please sign in to leave a comment.