Project progression to portal

[davo]

I've been working on a fairly large project which is a single company that represents events and trips run by partner agencies around the world.

To sum up, every partner agency has it's own page that is maintained by the representation company. There's also plenty of tools around the site all of which link to the partner agencies such as photos and video galleries.

My next stage of the project is to create a number of services that are to be maintained by the partner agencies. These might be hotels or special deals they are offering, or current flight to hotel transfer rates.

Really I'm just after some guidance before I commence this stage as I wish I'd done that prior to starting other areas of the project.

The issue I can see that I need to addresss are:

A log in area for the partner agencies

A way of controlling security for what they can each do; I wouldn't want one partner agency being able to control another's page.. oh no!

I also need some thought around how to actually structure the data.

with regards to the last point, I've had a look at the profields - tables module and on first look it seems to be just the thing.

Thoughts, suggestions and ideas welcome (on the understanding that you'll know I'll come back to you another )

David

[MindFull]

For the login, you would create a login form and based on who they are, direct them to the appropriate landing page.  This can be tricky to update if you're hardcoding all the partner companies into your script (don't do that). Instead, for each company, create a user.  Then, based on the users role, they can access pages that they are allowed to manage. You might find the Page Edit Per User module handy http://modules.processwire.com/modules/page-edit-per-user/ Or the Page Edit Per Role module http://modules.processwire.com/modules/page-edit-field-permission/ . 

I am actually working on a front end admin for users of a company intranet and that's along the lines of how I do it.

[davo]

Thank you. Login page created from Ryan's example used:

https://processwire.com/talk/topic/1716-integrating-a-member-visitor-login-form/

StArted looking at those two modules. Ta

[davo]

For the login, you would create a login form and based on who they are, direct them to the appropriate landing page.  This can be tricky to update if you're hardcoding all the partner companies into your script (don't do that). Instead, for each company, create a user.  Then, based on the users role, they can access pages that they are allowed to manage. You might find the Page Edit Per User module handy http://modules.processwire.com/modules/page-edit-per-user/ Or the Page Edit Per Role module http://modules.processwire.com/modules/page-edit-field-permission/ . 

I am actually working on a front end admin for users of a company intranet and that's along the lines of how I do it.

Brilliant; 3 days later i have full functionallity...

login using ryan's script https://processwire....tor-login-form/

page edit using soma's modal trick https://processwire.com/talk/topic/2382-processwire-setup-and-front-end-editing-made-easy/

access control via  http://modules.proce...-edit-per-user/ module

and some cool table editing via profields table https://processwire.com/api/modules/profields/table/

3 days with just a couple of hours a day..