Thread

Hey all,

I’m new to EE and to back-end coding in general. Most of my time is spent doing IA and front end development but have recently decided to roll up my sleeves and get involved in doing some back-end stuff as well. I’ve searched the forums and haven’t seen anything that’s exactly what I’m looking to do so I thought I’d ask.

Developing a site for a company where the company would like to be able to create accounts for its clients that grant the client access to a specific page.

So the process would be:
- Company creates user account with custom fields (I would imagine this would be done via the CP)
- After user account is created, user receives an email with the login details
- When user logs in, user sees a page that only displays information pertaining to their project with the company
- Only the company has the ability to edit content on the page. The user is logging in to just check on the status of the project

I hope that’s clear. Any guidance is greatly appreciated and if there is anything I can add to clarify, please feel more than free to ask.

Thank you in advance,
—jj

The first two steps are native EE, so that can be easily achieved using the back-end and some configuration (of settings in the CP). The third step requires a login form with a redirect to their profile page. The link to the profile page is based on their screen name for instance—> site.com/profile/screen_name). This profile page shows a certain custom field that is only editable by your customer (in CP). (you can find custom fields for user accounts: Admin ›  Members and Groups ›  Custom Profile Fields )

I’d probably shy away from using member profile fields for content.

What I’d investigate instead is:

- creating a weblog to hold all client-specific content.
- Assigning a client as author of the entry holding their content
- Using conditionals to get the ID of the logged in user and use that as a parameter on the weblog:entries tag to only show entries where the currently logged in user is author.

This way you’re in the standard Publish/Edit area for content maintenance, and if you ever get to the point of wanting to allow clients to edit their own content you are nicely positioned to do so.

I’d probably shy away from using member profile fields for content.

What I’d investigate instead is:

- creating a weblog to hold all client-specific content.
- Assigning a client as author of the entry holding their content
- Using conditionals to get the ID of the logged in user and use that as a parameter on the weblog:entries tag to only show entries where the currently logged in user is author.

This way you’re in the standard Publish/Edit area for content maintenance, and if you ever get to the point of wanting to allow clients to edit their own content you are nicely positioned to do so.

I am in the same boat. I am trying to setup a conditional redirect a client specific page. I’d like each client to be redirected to their own set of pages when they login. how can I do that? especially, how to use conditionals to get the ID of the logged in user and use that as a parameter on the weblog:entries tag to only show entries where the currently logged in user is author