Client-Login
Permalink
I'm trying to figure out the best way to use what Concrete5 has built into it to create a client login for a client.
They want clients to be able to log-in and download their own contacts and forms.
I set up the member directory and figured out how to edit the member profile pages .. but then realized after customizing one member profile and adding that particular customers contracts and forms.. that they showed up on all of members specific profile pages..
So plan b was to simply create users and then create specific user pages and then password protect those pages to the individual users.. but then realized that my client would have to create a new page for each client and then a new user group for each client so that they could then password protect those pages to just those users.. but that seemed like way too much work.
Is there no easier way to do a simple client login using what concrete5 already has built in?
If not.. Please let me know if this is something you can build.
They want clients to be able to log-in and download their own contacts and forms.
I set up the member directory and figured out how to edit the member profile pages .. but then realized after customizing one member profile and adding that particular customers contracts and forms.. that they showed up on all of members specific profile pages..
So plan b was to simply create users and then create specific user pages and then password protect those pages to the individual users.. but then realized that my client would have to create a new page for each client and then a new user group for each client so that they could then password protect those pages to just those users.. but that seemed like way too much work.
Is there no easier way to do a simple client login using what concrete5 already has built in?
If not.. Please let me know if this is something you can build.
The file manager permissions has a specific group called "File Uploader". Andrew did a "How'd we do that" on a recent "Totally Random" video explaining how to do it.
http://www.youtube.com/watch?v=6ETVOcWJkQ0&feature=share&li...
Couldn't you just build a page for each member and grant 'view' permissions just to this member and then use the 'file uploader' permission to restrict them to only seeing their own files?
http://www.youtube.com/watch?v=6ETVOcWJkQ0&feature=share&li...
Couldn't you just build a page for each member and grant 'view' permissions just to this member and then use the 'file uploader' permission to restrict them to only seeing their own files?
I've tried to train the client on adding a group and a page for each client and it's kind of a ridiculous method for maintaining a client log-in..
I need a quote on customizing the member login that comes standard with concrete5 so that you can add a block to each member that only that member can see. This should be pretty straight forward.
Let me know.
Joel
I need a quote on customizing the member login that comes standard with concrete5 so that you can add a block to each member that only that member can see. This should be pretty straight forward.
Let me know.
Joel
What's your end-goal? C5 has several ways of doing this "out of the box" (though, as you've seen, they're not necessarily client-friendly).
WIthout more details, I'd suggest advanced permissions (where you can choose to hide blocks from users not in an associated group, or an add-on that redirects users on login). Though neither are super-automated and might get complex with a lot of groups.
James
WIthout more details, I'd suggest advanced permissions (where you can choose to hide blocks from users not in an associated group, or an add-on that redirects users on login). Though neither are super-automated and might get complex with a lot of groups.
James
I've tried to rig this to work and it's just making us look like we don't know what we're doing to the client..
What I would like is to simply be able to add blocks that only the client associated with the page you're working on would see.
The client is a benefits administrator and wants to be able to upload forms and data for each client.
Joel Lucibello
Agenity Corporation
http://www.agenity.com
joel@agenity.com
704.728.1110
"We make websites smarter!"
What I would like is to simply be able to add blocks that only the client associated with the page you're working on would see.
The client is a benefits administrator and wants to be able to upload forms and data for each client.
Joel Lucibello
Agenity Corporation
http://www.agenity.com
joel@agenity.com
704.728.1110
"We make websites smarter!"
Blocks that are created on a page that only the member can access are automatically 'exclusive' to that member but the content they upload goes into the general File Manager. If I'm not mistaken, you can set permissions on the File Manager to 'File Uploader' so that a member can access only those items they uploaded themselves. Is this the concept you're after?
Technically, your "new pages" way is the easiest route. You wouldn't have to create a new group for each user -- you should be able to give individual users access to their page. But, clearly, that's still not a very good solution.
The next easiest (from the perspective of fitting into the c5 paradigm and no/little development), I think, is to have a file display block on the profile page (or anywhere else). It'd show the files in a set that the user has permissions to view. (You need to enable advanced permissions.) The problem, though, is that management will be difficult. It's not immediately clear who has access to the file(s), and you have to set permissions on each individual upload. A lot of the difficulty depends on how many users and files you have. I'm not positive that the "files in set" block respects permissions, but it should.
Probably the easiest from a maintenance perspective (but far less C5-y) is to use the "files in filesystem" block, and tweak it so that the directory it looks in is tied to the user (but with some obfuscation so other users can't guess the URLs). Then your client can just upload with FTP.
#1 and #2 are pretty easy and you might be able to handle with no coding. I can help with all 3.
James