CustomerRole matched ✓
After login
/my-account/After logout
/shop/MemberRole matched ✓
After login
/members/After logout
/Jamie is a customer. Select Log in to follow the customer’s journey.
← All features
Login & logout redirects
Send each person to the right next page.
Choose login and logout destinations by role, with a default for everyone else.
Available in the current release.
See it in action
Same login. A different destination.
A customer goes to their account. A member goes to their member area. Watch where each person lands after logging in and out.
Welcome back
Sign in to your WordPress site.
Username or emailjamie@example.com
Password••••••••
Finding your destination
Your account is verified. Checking its role.
Customer/my-account/
Your site✓ Signed in
Customer areaMy account
Welcome back, Jamie.
OrdersView your purchases →
AddressesManage delivery details →
Account detailsUpdate your profile →
Your site✓ Signed in
Member areaMember home
Welcome back, Alex.
Your coursesContinue learning →
Member resourcesExplore the library →
Your membershipManage your plan →
Your siteSigned out
The shopFind your next favourite.
You’re logged out and back at the shop.
Your siteSigned out
Welcome homeA place to learn and grow.
You’re logged out and back on the homepage.
Your configured destinations
Why it matters
A successful login should lead somewhere useful.
A student needs a course area. An editor needs a workspace. Sending everyone to the same default screen adds another detour and can make a member feel lost.
How it helps your site
Choose the destination, keep permissions separate.
FluentAuth selects destinations using your redirect rules. Users still need the appropriate permissions at the destination. A redirect improves the journey; it does not prevent someone from visiting another URL directly.
What you gain
Help each role get to work sooner, with a sensible fallback for everyone else.
Get FluentAuth →Inside FluentAuth
See the controls behind the experience.
Available in the current release.
Follow the setup guide →
How redirect rules work
- Add a destination for a role or supported condition.
- Put more specific rules before broader ones.
- Set a fallback destination for users who do not match an earlier rule.
Review the order when someone has more than one role. A sensible default keeps new or unexpected roles from reaching an unsuitable page.
Useful for courses and client portals
Send students to their course area, clients to their account and staff to their workspace. Test with representative accounts, including the logout journey, rather than checking only with an administrator.
Do redirects control permission to view a page?
A redirect chooses a destination. The destination still needs its own access controls. Membership rules and WordPress capabilities remain responsible for deciding what a user may see or change.
Custom forms can also provide a redirect destination. Check that choice alongside your global rules when debugging a route.
Works well with
Build on this feature.
Give every role a useful next step.
Set login and logout destinations, then test with the roles your site actually uses.