Forum OpenACS Q&A: Re: schedule proc memory

Collapse
5: Re: schedule proc memory (response to 1)
Posted by Dave Bauer on 05/11/06 01:45 PM
Right, setup a queue of who needs to get added to what communities then clear it out once a day, or whenever is appropriate.

Although, I can't help but imagine the real solution is to NOT add those 300 communities to the user's portal. There HAS to be an easier way.

Collapse
6: Re: Re: schedule proc memory (response to 5)
Posted by Malte Sussdorff on 05/12/06 09:17 AM
The setup is as follows:

Each customer has it's own community in .LRN so we have a customer portal (the community page).

Each employee needs to be able to work on all customers. Therefore the employee needs to be added to all customers to have the permission to see each task and the projects running with the customer.

If a new customer is added, all employees need to be added to the customer's community

If a new employee is added he needs to be added to all customers.

I would love to find a way for lazy adding (add the employee only when he actually has to work on the customer, but I am not sure how this could be achieved.

Collapse
7: Re: Re: Re: schedule proc memory (response to 6)
Posted by Caroline Meeks on 06/19/06 01:07 AM
Malte,

I think we discussed in AIM creating an employee group and granting that permissions (membership) in all the customer communities.

This might not work with all the user portlets, but for your application you probably don't want an employee to see aggregated items from all the customer communities anyway.

Did you try this? did it work?

Collapse
8: Re: Re: Re: Re: schedule proc memory (response to 7)
Posted by Malte Sussdorff on 06/19/06 06:36 AM
Oh, didn't I mention that. Yes, it did work. Just give permission, make sure the f***ed inheritance of dotlrn-fs is configured correctly and so far no problem with the portlets we are using.