Log in to different homepage
closed
L
Linda Cahoon
Our Home page is for public use and it would be great if the home owner could log in and be directed to a different page i.e what we have labelled now "Registered Users home page". It seems redundant for them to use the public page and be directed to the public page after logging in. Thanks for listening.
Log In
Tony Goodrow
Here's an approach that allows those users who agree with your design principles to have what they want and those who don't agree to have what they want. Add an option to redirect post login to any URL in the site. If nothing is filled in on the option, the default is the home page.
I hope this can be reconsidered.
Meredith Owens
Merged in a post:
Add a private Home Page
L
Lhv Website
Would like to see a Public Home Page AND a Private Home Page. In other words, when a member logs in, they land on a Home Page that only members can see. As an example, when our pool finally opened, we want to put a fun notice on the body of the home page to catch their attention but we don't want the public to see it.
Meredith Owens
Meredith Owens
Merged in a post:
Different home page when logged in
Ronald Crans
The home page is nice to have as a public-facing introduction to the community but, for residents, it's a mostly ignorable page. It would be GREAT to create a home page with alternate content for logged in users. It would allow displaying timely bits of important information to the community.
Meredith Owens
Meredith Owens
Merged in a post:
Have two homepages
Kim Wilcox
The HOME screen on what I call the Public side of our site tells about the community, etc. After a member logs in, they get the Same Home Screen except for an expanded menu. They still see the paragraph about how great the community is. This space could be used for other information.
Meredith Owens
closed
The public homepage is designed to provide an overview of information about the community that is applicable to all visitors to the website. Creating two separate homepages for both registered members and non-registered visitors would create unnecessary complexity, which doesn't follow our design philosophy of creating clean, easy-to-use websites.
For any information you'd like to have viewed by only registered and approved members, we recommend splitting this up into restricted pages on the website.
You mention that the login process is redirecting them back to the homepage. The way the login process works, it actually just brings the user back to the page they were previously viewing.
Since your community website in particular has hidden restricted pages in the menu, the homepage is the only page people will see before logging in. Therefore, after logging in they'll always see the homepage again.
If, instead, you unhid restricted pages, visitors could click on their desired page in the menu, log in, and then see that page immediately after.
Ronald Crans
Meredith Owens: I've been involved with web app development for more than fifteen years. There is nothing that could be deemed as unnecessary complexity about a few lines of code and few database fields ... a fairly simple task to achieve. So if there is some other reason that this can't be implemented, please inform us about the actual reason(s).
Wes Cossick
Ronald Crans: The complexity is not in regards to the development of the feature, but rather, the user experience. Having two distinct sets of content for the homepage (one for visitors and one for logged-in users) would not follow the design patterns already established for page content, and would add unnecessary difficulty and potentially confusion for both residents and administrators.
For more information about our design philosophy and how we keep our software easy-to-use, check out this help article: https://help.hoa-express.com/en/articles/2347346-how-feedback-change-requests-and-suggestions-are-handled