Community Forums › Forums › Archived Forums › General Discussion › Help with creating a Client Portal
Tagged: client portal
- This topic has 5 replies, 3 voices, and was last updated 6 years, 3 months ago by RavenManiac.
-
AuthorPosts
-
January 7, 2018 at 4:41 pm #215187RavenManiacParticipant
I'm thinking about creating a client portal for my website design business, but I don't know where to start. Currently, my clients view the website I have in the works for them by going to clientname.mycompanydomain.com
What I would prefer is a login page where my clients can enter a username and password that takes them to a secure area on my development server so they can view the work in progress. This would be for both WordPress and non-WordPress websites.
Can somebody point me in the right direction?
Thanks!
http://N/AJanuary 8, 2018 at 8:26 am #215197Victor FontModeratorSince you mentioned both WordPress and non-WordPress sites, you probably need to setup passwords at the Apache level. See this: http://www.yolinux.com/TUTORIALS/LinuxTutorialApacheAddingLoginSiteProtection.html
Regards,
Victor
https://victorfont.com/
Call us toll free: 844-VIC-FONT (842-3668)
Have you requested your free website audit yet?January 9, 2018 at 1:15 pm #215233Mark CorpuzParticipantOne simple approach would be to utilize a membership system for your wordpress / genesis site. I created one myself and I'll be more than happy to share my thoughts on the matter.
My goal is to create a convenient place where clients can only see 1 page. I'll then use this page to redirect them towards the right place. I'm also using this single page to embed any relevant information that they might find important.
Simplicity is key! Too much information and your client wouldn't bother to login. So it has to be more functional than it is wordy.
Here's my formula:
- Membership Plugin (currently Membership2 but there are other better options)
- Genesis Framework on WP
- Beaver Builder for the convenience on writing contentOther helpful strategies
- Dropbox Paper to allow clients to open up links that would need a lot of detailFeel free to reach out if you have any questions. I'm interested in seeing this from a developer (or client's point of view).
Mark Corpuz
626-590-6190
https://SmarterWebPackages.comJanuary 10, 2018 at 9:47 am #215268RavenManiacParticipantThanks guys. I really appreciate your help. I do have a few problems I could use your advice on.
Problem 1
With my current structure I'm using subdomains (i.e. client1.mydomain.com, client2.mydomain.com, etc.) for each website development project. While this works well, in order to put an SSL on my development server I would need to purchase a wildcard SSL, which is really expensive.Is there anything wrong with simply changing my structure to mydomain/client1, mydomain/client2, etc.?
Problem 2
I'm currently hosting my client's websites on a GoDaddy shared server, using my account and domain name, even though that is hidden. Because of this I think I need to have a totally different domain name for my development server. Would you agree?Mark, I totally agree with your statement, "Simplicity is key! Too much information and your client wouldn't bother to login. So it has to be more functional than it is wordy." Do you have an example of your client portal?
January 10, 2018 at 5:22 pm #215289Mark CorpuzParticipantI might have misunderstood your question earlier. But I'm going to point out my own experience with regard to "Client Portal" anyways.
1. My experience on a client portal is to simply create a single location where the clients can login to and get a central information from by way of a password protected unique page where the user gets redirected towards. This is simply referring to the "portal", kinda like a centralized customer support center.
For example:
https://client.YOURDOMAIN.com (LOGIN)
redirects to
https://client.YOURDOMAIN.com/CLIENTONE-PAGE
https://client.YOURDOMAIN.com/CLIENTTWO-PAGE2. As for the actual development site, that's entirely up to you. In my experience, I prefer to use a subdomain for this purpose but I technically also use different a different domain name altogether.
In the end, the main takeaway from this is that a client portal should be simple in the sense that it's the central location where you tell the client where to go after they see the information when they login. How you manage this however is a different story altogether and will depend on the plugins you use.
I can't really share my example to you but if you email me, I'll send you some screenshots of what I've done with my approach.
Mark Corpuz
626-590-6190
https://SmarterWebPackages.comJanuary 11, 2018 at 9:44 am #215298RavenManiacParticipantThanks Mark.
In my case:
http://client.YOURDOMAIN.comCurrently redirects to:
http://YOURDOMAIN.com/CLIENTONE-PAGE
http://YOURDOMAIN.com/CLIENTTWO-PAGEI wouldn't mind continuing to use subdomains, but doing so requires a wildcard SSL, which is expensive. https://www.godaddy.com/web-security/ssl-certificate
That's the only reason I'm considering changing how I have my development server setup.
-
AuthorPosts
- The forum ‘General Discussion’ is closed to new topics and replies.