Multiple member-specific pages
complete
Naitik Mehta
1) The problem → As a Memberstack customer, I'd like to set different 'sets' of member-specific pages. Example: I have freelancers, and clients, but both their member-specific pages have a different 'root' URL.
2) Why is this important → This enables me to create a separate workflow and dashboard for the multiple types of members I'm serving.
3) What's your plan B → Not sure.
4) Possible solutions we could build for you → Not sure.
Duncan Hamra
complete
This feature is now live in Memberstack 2.0 🎉
Here are the docs to get started → https://docs.memberstack.com/hc/en-us/articles/7385311945499-Setting-a-Member-specific-Login-Redirect
Duncan Hamra
in progress
This feature is finished in Memberstack 2.0 🎉 Will update the status again when 2.0 is live.
Duncan Hamra
planned
We have a solution which simplifies member-specific pages AND enables site admin to create as many different types of member-specific pages as they want. Expected to launch with Memberstack 2.0.
Naitik Mehta
Merged in a post:
Multiple Member-Specific Pages for Multiple CMS collections and pages
Chukwudi Onyekwere
1) The problem → We are using Memberstack + Webflow + Zapier to build a client admin app. The app requires multiple pages with multiple pieces of client-specific content.
It seems the Member-specific pages power-up is limited to only a single CMS collection which doesn't solve our problem as we have multiple CMS collections and pages (with collection lists) that will need to display data unique to each client.
2) Why is this important → We need to display data unique to each client on multiple CMS collections and pages.
3) What's your plan B → Not sure.
4) Possible solutions we could build for you → Make Member-specific pages power-up to work for multiple CMS collections and not limited to only a single CMS collection.
Naitik Mehta
under review
M
Maybaum Film
1) The problem → I can not set multiple member specific pages to a member. I have 2 kinds of members (clients / employees).
2) Why is this important → I have created member-specific pages (dashboards) for clients and I would like to give our employees access to several client dashboards (member-specific pages).
3) What's your plan B → Find another tool.
4) Possible solutions we could build for you → Not sure.
Duncan Hamra
I'm most familiar with this problem in Webflow. Webflow's CMS makes it super easy to create pages using structured data, but each CMS collection has its own distinct folder (file path). Memberstack requires all member-specific pages to be in the same folder (same file path) which means your stuck with a single Webflow CMS collection... which is not ideal for a decent number of use cases. Like the example provided above.
Karthik Sridharan
Duncan Hamra: That's right Duncan. At the moment, the solution is to do the following:
- Keep the URL as complex as possible
- Add a no-index tag to these pages.
- Of course, add each of the respective CMS collection paths to member blocked content. So, it can't be accessed by a non-member. Of course, still one member can access content of another - that's where I am hoping point 1 will help.
But is there any timeline to solve for multiple member-specific pages?