I have both the free level and premium level access in my access groups. Both groups will share the same login page. Here’s what I’d like to achieve:
(i) Free level access user to land on the free level home page after logging in, and…
(ii) Premium level access user to land on premium level home page after logging in
But it seems like there’s only one option on the login page setting “Redirect fallback”. It’s like I can only have one home page for both free level and premium level users.
Is there a way to achieve the two different scenarios above?
I came across your other response where you shared the Sygnal attributes: Advanced Log-In & Sign-Up Flow ❺ | Sygnal Attributes | Designed for Webflow . Would this help with what I’d like to achieve above? If yes, what is the value that I should replace “config.routeAfterFirstLogin” and “config.routeAfterLogin” ?
Implement your JS business rule to decide where the user should be directed to
As a fallback, just in case, I’d put a 5 second timer or something that redirects to a default page just in case something breaks in your access group setup ( changing an AG name, modifying your site structure, a slow network response, etc. )
Is there any alternative to this solution? I’m in a similar predicament, where “Gated content” is actually a page that hosts an embedded iframe dashboard.
Webpage A is a free demo of the dashboard.
Webpage B is an exclusive dashboard that certain users or access groups will only have access to.
So goals are:
Free users, i.e. anyone who signs up can access Webpage A
Only specific users added to our site can access Webpage B. Whenever logging in, they must always land on Webpage B.
If you’re using Webflow user accounts, SA5’s User Accounts lib is the only toolkit for extracting user info, custom fields, and access groups.
When I want something more robust and a project budget allows it, I build a reverse proxy that extends user accounts. It makes all of the user information instantly available, and supports secure server-side gating even for user-specific info.
Memberstack might be another option for you although it’s limited to client side script in its Webflow page gating abilities.
Because I tried applying the steps you mentioned on your earlier reply, but got confused halfway through (totally my fault, as this is my first time working in a non-native tech). I got lost in the technicalities in the docs, specifically on this step 3 of setting up access group detection..
I’ve pasted the codes required in implementing the SA5 user info lib on the site settings custom tag, so I’m clueless where I’m supposed to put the code mentioned in the above step 3 link.
I think I misread the instructions in the docs, since it said to “update” the code and not “add” per se. My bad. Anyway, I did some tinkering again but now when I try to login with the routing/loading page as a fallback, it just leads to a login error. Hope you can provide some more advice, thank you!
It sounds like you may have skipped the initial setup docs, and started with the access groups feature. There’s a lot to read through, because there is a lot of setup needed for SA5 to access the data you want. I’d review by starting with the basic install first, and then review your access groups setup again. If you need some help with that, you can DM me and I can send you my rates, I’d need full project access to go in an implement that for you.
SA5 User Info doesn’t have anything to do with the login itself, so it can’t cause an error there, it just captures info about the login. You may have something else wrong, like incorrect email / password, or too many logins in a short period of time.
You might prefer using a platform where the user-info and access-group access are directly integrated into the platform, in which case check out Memberstack.